Balazar crashes with soya3d error: invalid GL_ENUM

[msanzullo]

Binary package hint: balazar

Game version: 0.3.4ds1-2.
Ubuntu gutsy powerpc.
After the settings screens, if you start play you go back to start screen with the warning:
 Error: <class '_soya.GLError'>(GL_INVALID_ENUM)

ProblemType: Crash
Architecture: powerpc
Date: Wed Aug 15 11:21:15 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/games/balazar
InterpreterPath: /usr/bin/python2.5
Package: balazar 0.3.4.ds1-2
PackageArchitecture: all
ProcCmdline: /usr/bin/python -O /usr/games/balazar
ProcCwd: /home/mario
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/games/balazar']
SourcePackage: balazar
Title: balazar crashed with GLError in _soya.render()
Uname: Linux ubuntu 2.6.22-mario5 #1 PREEMPT Mon Aug 6 23:14:31 CEST 2007 ppc GNU/Linux

[misiu_mp (misiu-mp)]

I confirm this bug on ubuntu 8.10 ( on i386 ) and package version 0.3.4.ds1-3ubuntu2.
This is actually on eeebuntu 2, but I would not think this affects it.

[rusivi2 (rusivi2-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

In Maverick, I was unable to reproduce this problem, the game played fine.

As well, the version of Ubuntu your reporting this issue on is in End of Life status. You can learn more about this at https://wiki.ubuntu.com/Releases Please update via www.ubuntu.com provide a detailed error report, and update the bug status. Thanks!

lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10

apt-cache policy balazar
balazar:
  Installed: 0.3.4.ds1-6.1
  Candidate: 0.3.4.ds1-6.1
  Version table:
 *** 0.3.4.ds1-6.1 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/universe i386 Packages
        100 /var/lib/dpkg/status

[Charlie Kravetz (cjkgeek)]

@rusivi1: Please check the duplicate bugs listed in this report. This has been reported as happening in Maverick Meerkat also, and is still valid for that release. bug 632949 was reported on 2010-09-08 and marked as a duplicate of this bug. The EOL does not apply to this issue.