GNOME Bugzilla – Bug 613526
Crash in rb_sourcelist_remove at rb-sourcelist.c line 1330
Last modified: 2010-12-10 02:13:45 UTC
Version: 0.12.7 What were you doing when the application crashed? connected samsung YP-R0 player Distribution: Debian squeeze/sid Gnome Release: 2.28.2 2009-12-18 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.32-3-686 #1 SMP Thu Feb 25 06:14:20 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10705000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 106278912 vsize: 106278912 resident: 35147776 share: 19795968 rss: 35147776 rss_rlim: 18446744073709551615 CPU usage: start_time: 1269205261 rtime: 295 utime: 261 stime: 34 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0xb282db70 (LWP 16405)] [New Thread 0xb397bb70 (LWP 16381)] 0xb788d424 in __kernel_vsyscall ()
+ Trace 221030
Thread 1 (Thread 0xb634e970 (LWP 16377))
Inferior 1 [process 16377] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (7 sec old) --------------------- Device 0 (VID=04e8 and PID=5125) is a Samsung YP-R0. Device 0 (VID=04e8 and PID=5125) is a Samsung YP-R0. Device 0 (VID=04e8 and PID=5125) is a Samsung YP-R0. ignoring usb_claim_interface = -2ignoring usb_claim_interface = -22PTP_ERROR_IO: Trying again after re-initializing USB interface inep: usb_get_endpoint_status(): Kein passender Prozess gefunden outep: usb_get_endpoint_status(): Kein passender Prozess gefunden usb_clear_halt() on IN endpoint: Kein passender Prozess gefunden usb_clear_halt() on OUT endpoint: Kein passender Prozess gefunden usb_clear_halt() on INTERRUPT endpoint: Kein passender Prozess gefunden ignoring usb_claim_interface = -2ignoring usb_claim_interface = -22LIBMTP PANIC: Could not open session! (Return code 767) Try to reset the device. Device 0 (VID=04e8 and PID=5125) is a Samsung YP-R0. ignoring usb_claim_interface = -110LIBMTP PANIC: Unable to read device information on device 22 on bus 1, trying to continueDevice 0 (VID=04e8 and PID=5125) is a Samsung YP-R0. ignoring usb_claim_interface = -110LIBMTP PANIC: Unable to read device information on device 23 on bus 1, trying to continue** Rhythmbox:ERROR:rb-sourcelist.c:1330:rb_sourcelist_remove: assertion failed: (rb_sourcelist_source_to_iter (sourcelist, source, &iter)) --------------------------------------------------
I can't reproduce this. If you can, output from 'rhythmbox -D mtp' would probably help.
that would require me to reproduce the exact same sequence of events which I do not know how to do. It is not that rb crashes each time I connect the player. There is probably more than one factor involved, and I have no idea what they are....
Judging by the error messages from libmtp, it's probably caused by the device being accessed by some other process, or being busy in some other way.
we got a similar bug report here: https://bugs.edge.launchpad.net/ubuntu/+source/rhythmbox/+bug/569380 ; the output of the rhythmbox -D is here: http://launchpadlibrarian.net/45568551/output1
OK, now it makes sense - the source is being deleted twice. Once when the device is removed (it appears as device 13, disappears, then reappears as device 5), and again when the device open fails (because the device is no longer there).
Fixed in commit b6fa443, hopefully.
*** Bug 621255 has been marked as a duplicate of this bug. ***
*** Bug 636447 has been marked as a duplicate of this bug. ***
*** Bug 636922 has been marked as a duplicate of this bug. ***