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 376460 - crash in Rhythmbox Music Player: Inserted iPod Shuffle af...
crash in Rhythmbox Music Player: Inserted iPod Shuffle af...
Status: RESOLVED DUPLICATE of bug 358855
Product: rhythmbox
Classification: Other
Component: general
0.9.6
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-17 21:06 UTC by austin
Modified: 2006-11-17 23:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description austin 2006-11-17 21:06:16 UTC 
What were you doing when the application crashed?
Inserted iPod Shuffle after program was started. Starting program with iPod Shuffle already inserted also leads to a crash.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 187019264 vsize: 187019264 resident: 23707648 share: 14385152 rss: 23707648 rss_rlim: -1
CPU usage: start_time: 1163797470 rtime: 126 utime: 120 stime: 6 cutime:6 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47147961058272 (LWP 7663)]
[New Thread 1107310928 (LWP 7677)]
(no debugging symbols found)
0x00002ae1789b7eef in waitpid () from /lib/libpthread.so.0

+ Trace 87318

Thread 1 (Thread 47147961058272 (LWP 7663))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 rb_ipod_source_register_type
    from /usr/lib/rhythmbox/plugins/ipod/libipod.so
  • #4 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #5 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #6 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #7 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #8 g_object_class_override_property
    from /usr/lib64/libgobject-2.0.so.0
  • #9 g_object_newv
    from /usr/lib64/libgobject-2.0.so.0
  • #10 g_object_new_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #11 g_object_new
    from /usr/lib64/libgobject-2.0.so.0
  • #12 rb_ipod_source_new
    from /usr/lib/rhythmbox/plugins/ipod/libipod.so
  • #13 register_rb_plugin
    from /usr/lib/rhythmbox/plugins/ipod/libipod.so
  • #14 rb_marshal_OBJECT__OBJECT
  • #15 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #16 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #19 rb_removable_media_manager_queue_transfer
  • #20 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #21 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #24 gnome_vfs_volume_monitor_client_get_type
    from /usr/lib64/libgnomevfs-2.so.0
  • #25 dbus_connection_dispatch
    from /usr/lib64/libdbus-1.so.3
  • #26 dbus_server_setup_with_g_main
    from /usr/lib64/libdbus-glib-1.so.2
  • #27 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #28 g_main_context_check
    from /usr/lib64/libglib-2.0.so.0
  • #29 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #30 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #31 main
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Alex Lancaster





          2006-11-17 22:59:19 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

There are several possible duplicates, bug #358855, bug #352972, a debug stacktrace may help narrow it down.







Comment 2


Jonathan Matthew





          2006-11-17 23:34:59 UTC
        



Looks exactly like bug 358855.

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.  A stack trace with debug symbols would still be very helpful there.


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