Rhythmbox

rhythmbox crashed on unplugging phone

Bug #204113 reported by ndescript on 2008-03-20

Affects		Status	Importance	Assigned to	Milestone
	Rhythmbox	Expired	Critical	gnome-bugs #523089
	rhythmbox (Ubuntu)	Invalid	Medium	Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

While playing music I had my phone plugged into USB (Sony Ericsson W810i) which ubuntu recognizes perfectly. Although as PMP but nonetheless.
After I unplugged my phone RB immediately stopped playing and then crashed.

Running Ubuntu Hardy with latest updates (2.6.24-12-generic.) Rhythmbox 0.11.4.90-0ubuntu1.

When plugging in phone music playback gets choppy for a brief second, same for unplugging which seems to alternate between that or just crashing.

Might just be OSS though, I blame it for most of my problems. Grrr Creative.

ProblemType: Crash
Architecture: i386
Date: Thu Mar 20 03:21:27 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.11.4.90-0ubuntu1
PackageArchitecture: i386
ProcCmdline: rhythmbox
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? () from /usr/lib/librhythmbox-core.so.0
Title: rhythmbox crashed with SIGSEGV
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video
SegvAnalysis:
Segfault happened at: 0xb4ddae8c: mov (%esi),%eax
PC (0xb4ddae8c) ok
source "(%esi)" (0xc9fdaa36) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA

See original description

Tags:

Revision history for this message

ndescript (th3dge) wrote on 2008-03-20:

Dependencies.txt Edit (6.2 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (581 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (37.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (673 bytes, text/plain; charset="utf-8")
Registers.txt Edit (470 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (501 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.5 KiB, text/plain; charset="utf-8")

ndescript (th3dge) on 2008-03-20

description:

updated

Revision history for this message

Apport retracing service (apport) wrote on 2008-03-20: Symbolic stack trace

Stacktrace.txt (retraced) Edit (17.6 KiB, text/plain)

StacktraceTop:impl_delete_thyself (source=0x893f008)
rb_source_delete_thyself (source=0x893f008)
rb_removable_media_manager_unmount_volume (
IA__g_cclosure_marshal_VOID__OBJECT (closure=0x84b4b58,
IA__g_closure_invoke (closure=0x84b4b58, return_value=0x0,

Revision history for this message

Apport retracing service (apport) wrote on 2008-03-20: Symbolic threaded stack trace

ThreadStacktrace.txt (retraced) Edit (46.6 KiB, text/plain)

Changed in rhythmbox:
importance:	Undecided → Medium

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-03-20:

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=523598

Changed in rhythmbox:
assignee:	nobody → desktop-bugs
status:	New → Triaged

Bug Watch Updater (bug-watch-updater) on 2008-03-21

Changed in rhythmbox:
status:	Unknown → Invalid

Bug Watch Updater (bug-watch-updater) on 2008-03-22

Changed in rhythmbox:
status:	Invalid → New

Kees Cook (kees) on 2009-09-16

description:

updated

Bug Watch Updater (bug-watch-updater) on 2010-09-16

Changed in rhythmbox:
importance:	Unknown → Critical

Revision history for this message

Chris Wilson (notgary-deactivatedaccount) wrote on 2012-03-26:

Thanks a lot for reporting this bug, but I do not believe this issue still exists in Ubuntu. The original report was filed against a much older version of the software, and since it has been a long time since there was any activity on this report or any duplicates filed, either here or upstream, it is likely that the issue has been designed out. As such, I'm closing this bug.