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
another crash for natty
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-screensaver 2.30.2-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelMo
Architecture: i386
CrashCounter: 1
Date: Tue Apr 19 16:55:51 2011
ExecutablePath: /usr/lib/
GconfGnomeSession:
idle_delay = 30
/desktop/
windowmanager = gnome-wm
GnomeSessionIdl
GnomeSessionInh
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xea2824 <XF86DRIQueryEx
PC (0x00ea2824) 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 0x00ea2824 in XF86DRIQueryExt
No symbol table info available.
#1 0x008f6ae6 in ?? () from /usr/lib/
No symbol table info available.
StacktraceTop:
XF86DRIQueryEx
?? () from /usr/lib/
Title: gnome-screensav
UpgradeStatus: Upgraded to natty on 2011-04-17 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: gnome-wm
XsessionErrors:
(smd-applet:1592): GLib-WARNING **: /build/
(smd-applet:1592): GLib-WARNING **: /build/
(nautilus:1585): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(firefox-
(<unknown>:5120): Bonobo-WARNING **: Bonobo must be initialized before use
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.