abrt version: 1.1.17 architecture: i686 Attached file: backtrace, 31313 bytes cmdline: rhythmbox component: rhythmbox Attached file: coredump, 70373376 bytes crash_function: rb_sync_settings_sync_category executable: /usr/bin/rhythmbox kernel: 2.6.35.11-83.fc14.i686.PAE package: rhythmbox-0.13.3-1.fc14 rating: 4 reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1298457740 uid: 500 How to reproduce ----- 1.Open Uncknown Device 2. 3.
Created attachment 480413 [details] File: backtrace
Package: rhythmbox-0.13.3-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Connect Cowon D-2 to usb port 2. Wait till mounted 3. Start RhythmBox 4. Note that device shows up as "Unknown Device" - the device doesn't seem to be connected. No songs show up on clicking on it. 5. Right click on the device and click on Properties 6. Crash! Comment ----- I recently installed python-pymtp to play with some code to manipulate playlists. Since that time, Rhythmbox fails to connect to the device properly. Before installing python-pymtp, Rhythm Box could load tracks, album info etc. from the device reliably (i.e. on every connect). I've also installed mtp-tools to check libmtp directly and it seems to have the same problem - it detects the Vendor and Device ids and then simply seems to hang.
After installation python-pymtp, crash is not reproduced. "Unknown Device" has been changed on "Sansa Express".
(In reply to comment #3) _BEFORE_ installation python-pymtp, crash is not reproduced. "Unknown Device" has been changed on "Sansa Express".
Package: rhythmbox-0.13.3-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. unplugging my mp3 player (creative zen) 2. 3.
Backtrace analysis found this bug to be similar to bug #701746, closing as duplicate. Bugs which were found to be similar to this bug: bug #655198, bug #662252, bug #673245, bug #701746 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 701746 ***