ubuntu-x-swat team mailing list archive
-
ubuntu-x-swat team
-
Mailing list archive
-
Message #21918
[Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0
** Description changed:
I believe that glxgears crashed because I don't have glx running at the
moment:
Xlib: extension "GLX" missing on display ":0.0".
However, if this is the case it'd make much more sense if apport, in the
form of a per package hook, did not allow these crash reports to be
reported.
ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/glxgears
Package: mesa-utils 7.3-1ubuntu1
ProcCmdline: glxgears
ProcEnviron:
PATH=(custom, user)
SHELL=/bin/zsh
LANG=en_US.UTF-8
Signal: 11
SourcePackage: mesa
StacktraceTop:
?? () from /usr/lib/libGL.so.1
?? () from /usr/lib/libGL.so.1
?? ()
?? () from /usr/lib/libGL.so.1
?? ()
Title: glxgears crashed with SIGSEGV
Uname: Linux 2.6.27-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip family floppy fuse lpadmin plugdev pulse pulse-access pulse-rt sambashare scanner video
+ SegvAnalysis:
+ Segfault happened at: 0x7ffacbdf4d0a: mov (%rax),%esi
+ PC (0x7ffacbdf4d0a) ok
+ source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
+ destination "%esi" ok
+ SegvReason: reading NULL VMA
--
glxgears crashed with SIGSEGV due to no GLX on display :0
https://bugs.launchpad.net/bugs/327673
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.