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

Bug #469209 reported by rychu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-screensaver

I have executed 'xset dpms force suspend'. After that, i hit some key and then the crash happend.

ProblemType: Crash
Architecture: i386
Date: Sun Nov 1 19:34:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
Package: gnome-screensaver 2.28.0-0ubuntu3
ProcCmdline: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
ProcEnviron:
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x874f48: mov (%eax),%esi
 PC (0x00874f48) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-screensaver
StacktraceTop:
 ?? () from /usr/lib/libGL.so.1
 ?? () from /lib/tls/i686/cmov/libc.so.6
 exit () from /lib/tls/i686/cmov/libc.so.6
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: gnome-screensaver-gl-helper crashed with SIGSEGV in exit()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare scard

Revision history for this message
rychu (rychu) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? () from /usr/lib/libGL.so.1
__run_exit_handlers (status=-1215971328, listp=0x6cf4304,
*__GI_exit (status=0) at exit.c:100
__libc_start_main (main=0x8048cb0 <main>, argc=1,
_start () at ../sysdeps/i386/elf/start.S:119

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gnome-screensaver (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

visibility: private → public
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.