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
Sorry, New to Ubuntu as well as "gnome-screensaver" package. I don't know what caused the bug report, but will pay close attention in future. I am currently running the video output of my Ubunty pc into a plasma monitor, which automatically powers-down after input (from pc or other source) is absent for N minutes. Hope I have not muddied the waters - I'll do better, if possible, next time. Much thanks to Ubuntu community for all your efforts toward a better OS.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-screensaver 2.30.2-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Tue Apr 19 12:57:05 2011
ExecutablePath: /usr/lib/
GconfGnomeSession:
idle_delay = 5
/desktop/
windowmanager = gnome-wm
GnomeSessionIdl
GnomeSessionInh
InstallationMedia: Ubuntu-Studio 10.10 "Maverick Meerkat" - Release i386 (20101008)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x562824 <XF86DRIQueryEx
PC (0x00562824) 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 0x00562824 in XF86DRIQueryExt
No symbol table info available.
#1 0x00b5dae6 in ?? () from /usr/lib/
No symbol table info available.
StacktraceTop:
XF86DRIQueryEx
?? () from /usr/lib/
Title: gnome-screensav
UpgradeStatus: Upgraded to natty on 2011-04-19 (0 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
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.