Starting bouncy: python2.5 crashed with SIGSEGV in vfprintf() [Hardy]

[Jan Ischebeck]

Binary package hint: bouncy

When starting bouncy it directly segfaults.

jan@PUNDIT:~$ bouncy
*** stack smashing detected ***: python terminated
Segmentation fault (core dumped)

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Dec 8 10:02:15 2007
Dependencies:
 libgcc1 1:4.2.2-3ubuntu4
 gcc-4.2-base 4.2.2-3ubuntu4
 zlib1g 1:1.2.3.3.dfsg-7ubuntu1
 libc6 2.7-3ubuntu1
Disassembly: 0x40de8800:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/python2.5
NonfreeKernelModules: vmnet vmmon nvidia
Package: python2.5-minimal 2.5.1-5ubuntu5
PackageArchitecture: i386
ProcCmdline: python game.py
ProcCwd: /usr/share/games/bouncy
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 PATH=/home/jan/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: python2.5
StacktraceTop:
 ?? ()
 ?? () from /lib/libc.so.6
 vfprintf () from /lib/libc.so.6
 fprintf () from /lib/libc.so.6
 Py_FatalError ()
Title: python2.5 crashed with SIGSEGV in vfprintf()
Uname: Linux PUNDIT 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy kvm lpadmin plugdev scanner video

[Apport retracing service (apport)]

StacktraceTop:?? ()
printf_unknown () from /lib/libc.so.6
__vstrfmon_l () from /lib/libc.so.6
_i18n_number_rewrite () from /lib/libc.so.6
Py_FatalError (

[Daniel Hahler (blueyed)]

JFI: Cannot confirm it here, using also Hardy/i386 and the non-free nvidia drivers: the game starts and is playable.

Unfortunately the apport-retrace failed and a manual retrace is not possible, given that ddebs.ubuntu.com seems to be a bit behind.

You might want to create debug-enabled packages yourself using the method described at https://wiki.ubuntu.com/DebuggingProgramCrash#head-6d5ad9ce155fc4f032725a49ba93dcf6fd2e977c

[Matthias Klose (doko)]

closing the python2.5 task, unreproducible

[Daniel Hahler (blueyed)]

Jan, can you still reproduce this?

[Jan Ischebeck (siesel)]

Hi Daniel,

no I can't reproduce the same bug, but...
when I start bouncy under the same circumstances (compiz active ->? OpenGL blocked? ).

 I get the following stack-trace.

jan@PUNDIT:~$ bouncy
Traceback (most recent call last):
  File "game.py", line 8, in <module>
    from OpenGL.GL import *
  File "/usr/lib/python2.5/site-packages/OpenGL/GL/__init__.py", line 2, in <module>
    from OpenGL.raw.GL import *
  File "/usr/lib/python2.5/site-packages/OpenGL/raw/GL/__init__.py", line 6, in <module>
    from OpenGL.raw.GL.constants import *
  File "/usr/lib/python2.5/site-packages/OpenGL/raw/GL/constants.py", line 7, in <module>
    from OpenGL import platform, arrays
  File "/usr/lib/python2.5/site-packages/OpenGL/platform/__init__.py", line 57, in <module>
    _load()
  File "/usr/lib/python2.5/site-packages/OpenGL/platform/__init__.py", line 53, in _load
    sys.platform, os.name,
RuntimeError: Unable to find an implementation for the 'linux2' ('posix') platform

[Daniel Hahler (blueyed)]

Jan, thanks for reporting back. I can confirm this.
This is filed already at bug 195270 (a problem with pyopengl apparently).
So we need to get this fixed, before we can look at this bug here again.

[Daniel Hahler (blueyed)]

Jan, pyopengl is fixed now. Can you please try again, if bouncy now works for you?
Thank you.

[Jan Ischebeck (siesel)]

Daniel, everything works now. :)

[Daniel Hahler (blueyed)]

Great! :)
Thank you for reporting back, I'm marking it "Fix Released".