[apport] amoeba crashed with SIGILL in __glXInitialize()

Bug #92104 reported by compucoder
0
Affects Status Importance Assigned to Milestone
amoeba (Ubuntu)
Invalid
Medium
MOTU

Bug Description

Binary package hint: amoeba

Just ran it and it crashed. I do get this though... I actually get this same message for any GL applications.
libGL warning: 3D driver claims to not support visual 0x5b

ProblemType: Crash
Architecture: i386
Date: Tue Mar 13 20:54:03 2007
Disassembly: 0xb754a210:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/amoeba
Package: amoeba 1.1-17
PackageArchitecture: i386
ProcCmdline: amoeba
ProcCwd: /home/ron
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
Signal: 4
SourcePackage: amoeba
StacktraceTop:
 ?? ()
 __glXInitialize () from /usr/lib/libGL.so.1
 __glXSetupForCommand () from /usr/lib/libGL.so.1
 ?? () from /usr/lib/libGL.so.1
 ?? ()
Uname: Linux ron-laptop 2.6.20-10-generic #2 SMP Mon Mar 12 00:02:49 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
compucoder (roncr) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report.

Changed in amoeba:
assignee: nobody → motu
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
__glXInitialize () from /usr/lib/libGL.so.1
__glXSetupForCommand () from /usr/lib/libGL.so.1
?? () from /usr/lib/libGL.so.1
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Daniel T Chen (crimsun) wrote :

I can't confirm this symptom in 9.04. Please set the status to:
1) New if reproducible in a supported or development Ubuntu version, or
2) Invalid if you cannot reproduce it in a supported or development Ubuntu version.

Changed in amoeba:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) 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 amoeba:
status: Incomplete → Invalid
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.