drempels crashed with SIGSEGV

Bug #452538 reported by Stuart Johnson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rss-glx (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: rss-glx

Came back to my desktop to find a message that the drempels screen saver had crashed.

ProblemType: Crash
Architecture: i386
Date: Thu Oct 15 16:51:54 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/xscreensaver/drempels
NonfreeKernelModules: nvidia
Package: rss-glx 0.9.0-2ubuntu3
ProcCmdline: drempels -r
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
SegvAnalysis:
 Segfault happened at: 0x1689154: mov %eax,0x44(%edx)
 PC (0x01689154) ok
 source "%eax" ok
 destination "0x44(%edx)" (0x00000044) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: rss-glx
StacktraceTop:
 ?? () from /usr/lib/libGLcore.so.1
 ?? () from /usr/lib/libGL.so.1
 ?? ()
Title: drempels crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Stuart Johnson (jstuart-johnson) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? () from /usr/lib/libGLcore.so.1
?? () from /usr/lib/libGL.so.1
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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.

visibility: private → public
Changed in rss-glx (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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!.

Changed in rss-glx (Ubuntu):
status: Incomplete → Invalid
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.