rhythmbox crashed when pluged in and removed mp3-player w/o having codec installed

Bug #197902 reported by Patrik Schönfeldt
10
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

(Gusty, Rhythmbox 0.11.4-0ubuntu6)
I plugged in my Digital Audio Player (Samsung YP-U2R) with mainly OGG Vorbis (~1GB), some MP3-Tracks (~300MB) and a few other binary files (7z compressed Files, <10MB) on it. Rhythmbox started and put tracks into library. After a while the codec installer started and I added the two codecs shown in the list (Gstreamer extra plugins and Gstreamer ffmpeg video plugin). After installation Rhythmbox was frozen and it crached when I unmounted the device.

ProblemType: Crash
Architecture: i386
Date: Mon Mar 3 08:34:20 2008
Disassembly: 0x0:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: cdrom
Package: rhythmbox 0.11.4-0ubuntu6
PackageArchitecture: i386
ProcCmdline: rhythmbox /media/disk
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? ()
 rb_source_delete_thyself ()
 ?? ()
 ?? ()
 ?? ()
Title: rhythmbox crashed with SIGSEGV in rb_source_delete_thyself()
Uname: Linux 2.6.24-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev video

Revision history for this message
Patrik Schönfeldt (bauer87) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
rb_source_delete_thyself (source=0x8dbb9a0) at rb-source.c:1041
impl_delete_thyself (source=0x8bd4038) at rb-generic-player-source.c:665
rb_source_delete_thyself (source=0x8bd4038) at rb-source.c:1041
IA__g_list_foreach (list=0x89b7520, func=0xb7f249e0 <rb_source_delete_thyself>, user_data=0x0)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, trace is similar to http://bugzilla.gnome.org/show_bug.cgi?id=442486, can you still reproduce this ? may you tell us a few steps in order to reproduce the crash? thanks in advance.

Changed in rhythmbox:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Patrik Schönfeldt (bauer87) wrote :

I just tried and I can still reproduce the crash. What I do:

1. Not have proprietary codecs installed.
2. Plug in removable device (MP3 Player).
3. (Rhythmbox opens and asks if you want to search for suitable codecs.)
4. Confirm. (Codecs are beings searched.)
5. Unmount removable device.
6. Close "Add/Remove Programs" after successful installation of codecs (do not want to add more software).
7. Wait some seconds. (Rhythmbox is frozen, you cannot resize the window, klick buttons or anything.)
7. Rhythmbox crashes.

(If you wonder why anybody unmounts the device while codecs are being installed: The first time I removed the device because I realized that I have the music available in my local network.)

Revision history for this message
Caroline Ford (secretlondon) wrote :

This *only* happens when you are searching for codecs? The usptream bug is unconnected to codecs.

Revision history for this message
Patrik Schönfeldt (bauer87) wrote :

I cannot reproduce the bug anymore. When I reported this bug rhythmbox started automatically when I plugged in my music player and started importing media. Now it does neither start nor import media. Instead nautilus opens to shows the content. Opening rhythmbox manually has no effect either. It seems that it is not detected as a music device but as an external hard disk: The icon looks like the one of a hdd.

I remember that it says that the device is currently in use when you try to unmount it without the installation codecs (or at least without this dialog popping up).

Revision history for this message
Sebastien Bacher (seb128) wrote :

closing since the way rhythmbox is called on those devices changed and the submitter doesn't get the bug in hardy now, feel free to reopen if you get the issue again though

Changed in rhythmbox:
status: Incomplete → Fix Released
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.