hyperspace crashed with SIGSEGV

Bug #448543 reported by Alistair Young
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

Ubuntu 9.10 beta
I selected Hyperspace and got the crash report

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Oct 11 20:33:24 2009
Disassembly: 0xc57898: Cannot access memory at address 0xc57898
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/xscreensaver/hyperspace
Package: rss-glx 0.9.0-2ubuntu3
ProcCmdline: hyperspace -r
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_NZ.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-13.43-generic
Signal: 11
SourcePackage: rss-glx
Stacktrace:
 #0 0x00c57898 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf9cd3dc
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (Thread 13302):
 #0 0x00c57898 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf9cd3dc
Title: hyperspace crashed with SIGSEGV
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0xc57898: Cannot access memory at address 0xc57898
 PC (0x00c57898) ok
 SP (0xbf9cd380) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

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

StacktraceTop:?? ()

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
Kees Cook (kees)
description: updated
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.