rhythmbox crashed with SIGSEGV

Bug #647494 reported by Guybrush88
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gstreamer0.10 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: libgstreamer0.10-0 0.10.30-1build2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sat Sep 25 14:56:59 2010
Disassembly: => 0xad0b58: Cannot access memory at address 0xad0b58
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: rhythmbox /media/IPOD
ProcEnviron:
 LANG=it_IT.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xad0b58: Cannot access memory at address 0xad0b58
 PC (0x00ad0b58) ok
 SP (0xbfeddc20) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: gstreamer0.10
Stacktrace:
 #0 0x00ad0b58 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfeddc20
StacktraceTop: ?? ()
Title: rhythmbox crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Guybrush88 (guybrush) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00ad0b58 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfeddc5c
StacktraceTop: ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
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.

Changed in gstreamer0.10 (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 gstreamer0.10 (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.