gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryExtension()

Bug #553952 reported by Ilya
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-screensaver

i don't know why this bug came to me

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-screensaver 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic-pae
Uname: Linux 2.6.31-19-generic-pae i686
NonfreeKernelModules: fglrx
Architecture: i386
CrashCounter: 1
Date: Fri Apr 2 15:24:15 2010
ExecutablePath: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6cd755a <XF86DRIQueryExtension+142>: movzbl 0x4(%esi),%edx
 PC (0xb6cd755a) 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
StacktraceTop:
 XF86DRIQueryExtension () from /usr/lib/libGL.so.1
 ?? ()
 ?? ()
 ?? ()
Title: gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryExtension()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
WindowManager: compiz

Revision history for this message
Ilya (ppp0-at) wrote :
Ilya (ppp0-at)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb6cd755a in ?? ()
 No symbol table info available.
 #1 0x091daeb8 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-screensaver (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

python2.6: installed version 2.6.5-1ubuntu3, latest version: 2.6.5-1ubuntu4
libplymouth2: installed version 0.8.1-3, latest version: 0.8.1-4
upstart: installed version 0.6.5-5, latest version: 0.6.5-6
python2.6-minimal: installed version 2.6.5-1ubuntu3, latest version: 2.6.5-1ubuntu4
plymouth: installed version 0.8.1-3, latest version: 0.8.1-4

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
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.