[apport] glxgears crashed with SIGSEGV in __ctype_b_loc()

Bug #102988 reported by Arie
18
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

While update the system i tried to start glxgears but this wasn't possible. It crashed almost immediately. No i get this

arie@arie-desktop:~$ glxgears
Segmentation fault
arie@arie-desktop:~$

ProblemType: Crash
Architecture: i386
Date: Wed Apr 4 20:04:27 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/glxgears
Package: mesa-utils 6.5.2-3ubuntu7
PackageArchitecture: i386
ProcCmdline: glxgears
ProcCwd: /home/arie
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=nl_NL.UTF-8
Signal: 11
SourcePackage: mesa
Stacktrace:
 #0 0xb7d580e2 in __ctype_b_loc () from /lib/libc.so.6
 #1 0xbfab5ff8 in ?? ()
 #2 0xb7c88505 in _X11TransConnectDisplay () from /usr/lib/libX11.so.6
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 __ctype_b_loc () from /lib/libc.so.6
 ?? ()
 _X11TransConnectDisplay () from /usr/lib/libX11.so.6
Uname: Linux arie-desktop 2.6.20-13-386 #2 Sun Mar 25 00:18:53 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Arie (arietimmerman) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__ctype_b_loc () from /lib/libc.so.6
_XwcDefaultTextExtents (oc=0x0, text=0x0, length=134530440, overall_ink=0x0, overall_logical=0x0) at ../../../src/xlibi18n/XDefaultOMIF.c:792
XOpenDisplay (display=0x0) at ../../src/OpenDis.c:563
main (argc=1, argv=0xbfab63b4) at glxgears.c:585
__libc_start_main () from /lib/libc.so.6

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in mesa:
importance: Undecided → Medium
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Thanks for your bug report. Does this still happen in Gutsy or Hardy? If so, please attach your Xorg.0.log and xorg.conf.

Changed in mesa:
assignee: nobody → tormodvolden
status: New → Incomplete
Revision history for this message
Tormod Volden (tormodvolden) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in mesa:
assignee: tormodvolden → nobody
status: Incomplete → Invalid
jussir (jussir)
Changed in mesa:
status: Invalid → Confirmed
Timo Aaltonen (tjaalton)
Changed in mesa:
status: Confirmed → Invalid
Revision history for this message
bazzdee (bazz-dee) wrote :

i got this with hardy

Revision history for this message
bazzdee (bazz-dee) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.