[apport] balazar crashed with TypeError in _soya.render()

[Mark Keller]

Binary package hint: balazar

* Balazar * Balazar lives in /usr/share/games
* Balazar * (Psyco not found ; if you are using an x86 processor, installing psyco can speed up Balazar a little)
* Soya * Using 8 bits stencil buffer

* Soya * version 0.12
* Using OpenGL 1.3 Mesa 6.5.2
* - renderer : Mesa DRI R300 20060815 AGP 1x x86/MMX+/3DNow!+/SSE TCL
* - vendor : Tungsten Graphics, Inc.
* - maximum number of lights : 8
* - maximum number of clip planes : 6
* - maximum number of texture units : 8
* - maximum texture size : 2048 pixels
* Using OpenAL 1.1
* - renderer : Software
* - vendor : OpenAL Community

*********************************WARN_ONCE*********************************
File r300_render.c function r300Fallback line 430
Software fallback:ctx->Point.SmoothFlag
***************************************************************************
Try R300_SPAN_DISABLE_LOCKING env var if this hangs.
Unknown GL_ERROR
Traceback (most recent call last):
  File "/usr/games/balazar", line 138, in <module>
    balazar.game_interface.init()
  File "/usr/share/games/balazar/game_interface.py", line 39, in init
    soya.render()
  File "renderer.pyx", line 424, in _soya.render
  File "renderer.pyx", line 404, in _soya.check_gl_error
TypeError: exceptions must be strings, classes, or instances, not GLError
* Soya3D * Quit...

ProblemType: Crash
Architecture: i386
Date: Tue May 15 16:21:53 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/games/balazar
InterpreterPath: /usr/bin/python2.5
Package: balazar 0.3.3.ds1-1
PackageArchitecture: all
ProcCmdline: /usr/bin/python -O /usr/games/balazar
ProcCwd: /home/mark
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/games/balazar']
SourcePackage: balazar
Uname: Linux kellerboys 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thank you for your bug report. This bug has already been reported by other users.