gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryExtension()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-screensaver (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-screensaver
1) Ubuntu Natty (developement branch) Release 11.04
2) andrew@SandBox:~$ apt-cache policy unity
unity:
Installed: 3.8.2-0ubuntu1
Candidate: 3.8.2-0ubuntu1
Version table:
*** 3.8.2-0ubuntu1 0
500 http://
100 /var/lib/
3) Up until about 3 days ago I was able to use Unity, but then i got a message "It seems your hardware will not support Unity" or similar - now it goes straight to Gnome and I unable to use Unity. This bug occurs after coming out of the Gnome screensaver.
4) I had this error but processing continued as normal.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-screensaver 2.30.2-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
CrashCounter: 1
Date: Tue Apr 5 10:27:40 2011
ExecutablePath: /usr/lib/
GconfGnomeSession:
idle_delay = 5
/desktop/
windowmanager = gnome-wm
GnomeSessionIdl
GnomeSessionInh
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xa62824 <XF86DRIQueryEx
PC (0x00a62824) ok
source "0x4(%esi)" (0x00000004) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-screensaver
Stacktrace:
#0 0x00a62824 in XF86DRIQueryExt
No symbol table info available.
#1 0x00176aa6 in ?? () from /usr/lib/
No symbol table info available.
StacktraceTop:
XF86DRIQueryEx
?? () from /usr/lib/
Title: gnome-screensav
UpgradeStatus: Upgraded to natty on 2011-04-05 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: gnome-wm
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #750010, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.