After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 636447 - crash in Rhythmbox: Just connected Creative ...
crash in Rhythmbox: Just connected Creative ...
Status: RESOLVED DUPLICATE of bug 613526
Product: rhythmbox
Classification: Other
Component: general
0.12.x
Other All
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-12-04 12:59 UTC by haruo31
Modified: 2010-12-04 23:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Description haruo31 2010-12-04 12:59:37 UTC 
Version: 0.12.8

What were you doing when the application crashed?
Just connected Creative Zen


Distribution: Debian squeeze/sid
Gnome Release: 2.30.2 2010-11-12 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.36 #1 SMP Thu Nov 11 02:37:59 JST 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaEalm
Icon Theme: Nuvola
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 762687488 vsize: 762687488 resident: 64724992 share: 32874496 rss: 64724992 rss_rlim: 18446744073709551615
CPU usage: start_time: 1291467518 rtime: 197 utime: 160 stime: 37 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 0x7fb5090d7710 (LWP 30449)]
[New Thread 0x7fb50048d710 (LWP 30420)]
[New Thread 0x7fb500c8e710 (LWP 30419)]
[New Thread 0x7fb50b3c8710 (LWP 30408)]
[New Thread 0x7fb51713f710 (LWP 30407)]
0x00007fb5263b2b4d in waitpid () from /lib/libpthread.so.0

+ Trace 224977

Thread 1 (Thread 0x7fb52a6957e0 (LWP 30395))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_assertion_message
    from /lib/libglib-2.0.so.0
  • #8 g_assertion_message_expr
    from /lib/libglib-2.0.so.0
  • #9 rb_sourcelist_remove
    from /usr/lib/librhythmbox-core.so.0
  • #10 ??
    from /usr/lib/librhythmbox-core.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/rhythmbox/plugins/mtpdevice/libmtpdevice.so
  • #16 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main 
A debugging session is active.

	Inferior 1 [process 30395] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
Device 0 (VID=041e and PID=4162) is a Creative ZEN X-Fi.
**
Rhythmbox:ERROR:rb-sourcelist.c:1320:rb_sourcelist_remove: assertion failed: (rb_sourcelist_source_to_iter (sourcelist, source, &iter))
LIBMTP PANIC: Unable to read device information on device 28 on bus 2, trying to continueignoring usb_claim_interface = -16ignoring usb_claim_interface = -22PTP_ERROR_IO: Trying again after re-initial
inep: usb_get_endpoint_status(): デバイスもしくはリソースがビジー状態です
outep: usb_get_endpoint_status(): デバイスもしくはリソースがビジー状態です
usb_clear_halt() on IN endpoint: デバイスもしくはリソースがビジー状態です
usb_clear_halt() on OUT endpoint: デバイスもしくはリソースがビジー状態です
usb_clear_halt() on INTERRUPT endpoint: デバイスもしくはリソースがビジー状態です
LIBMTP PANIC: Unable to read device information on device 28 on bus 2, trying to continueignoring usb_claim_interface = -16ignoring usb_claim_interface = -22PTP_ERROR_IO: Trying again after re-initial
inep: usb_get_endpoint_status(): デバイスもしくはリソースがビジー状態です
outep: usb_get_endpoint_status(): デバイスもしくはリソースがビジー状態です
usb_clear_halt() on IN endpoint: デバイスもしくはリソースがビジー状態です
usb_clear_halt() on OUT endpoint: デバイスもしくはリソースがビジー状態です
usb_clear_halt() on INTERRUPT endpoint: デバイスもしくはリソースがビジー状態です
LIBMTP PANIC: Unable to read device information on device 28 on bus 2, trying to continue
--------------------------------------------------
Comment 1 Jonathan Matthew 2010-12-04 23:07:38 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 613526 ***