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

[Ersin Akyüz]

Binary package hint: gnome-screensaver

when screensaver starts then crashed

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-screensaver 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelModules: fglrx wl
Architecture: i386
Date: Tue Apr 6 22:44:42 2010
ExecutablePath: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100405)
ProcCmdline: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
ProcEnviron:
 PATH=(custom, no user)
 LANG=tr_TR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xe9ded6 <XF86DRIQueryExtension+142>: movzbl 0x4(%esi),%edx
 PC (0x00e9ded6) 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/fglrx/libGL.so.1
 ?? ()
 ?? ()
 ?? ()
Title: gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryExtension()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: metacity

[Apport retracing service (apport)]

Stacktrace:
 #0 0x00e9ded6 in XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 No symbol table info available.
 #1 0x0000000d in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 XF86DRIQueryExtension () from /usr/lib/fglrx/libGL.so.1
 ?? ()

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.