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 442292 - crash in Rhythmbox Music Player: Pluggin ipod
crash in Rhythmbox Music Player: Pluggin ipod
Status: RESOLVED DUPLICATE of bug 352972
Product: rhythmbox
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-30 11:01 UTC by ipoduser
Modified: 2007-06-03 10:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description ipoduser 2007-05-30 11:01:26 UTC
What were you doing when the application crashed?
Pluggin ipod


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 88723456 vsize: 0 resident: 88723456 share: 0 rss: 17010688 rss_rlim: 0
CPU usage: start_time: 1180495553 rtime: 0 utime: 243 stime: 0 cutime:219 cstime: 0 timeout: 24 it_real_value: 0 frequency: 4

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 -1208248608 (LWP 18957)]
[New Thread -1244865648 (LWP 18965)]
(no debugging symbols found)
0x00f95402 in __kernel_vsyscall ()

Thread 1 (Thread -1208248608 (LWP 18957))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strlen
    from /lib/libc.so.6
  • #5 g_strdup
    from /lib/libglib-2.0.so.0
  • #6 itdb_device_list_devices
    from /usr/lib/libgpod.so.0
  • #7 itdb_device_list_devices
    from /usr/lib/libgpod.so.0
  • #8 g_object_newv
    from /lib/libgobject-2.0.so.0
  • #9 g_object_new_valist
    from /lib/libgobject-2.0.so.0
  • #10 g_object_new
    from /lib/libgobject-2.0.so.0
  • #11 itdb_device_new
    from /usr/lib/libgpod.so.0
  • #12 itdb_set_mountpoint
    from /usr/lib/libgpod.so.0
  • #13 itdb_parse
    from /usr/lib/libgpod.so.0
  • #14 rb_ipod_source_register_type
    from /usr/lib/rhythmbox/plugins/libipod.so
  • #15 g_object_newv
    from /lib/libgobject-2.0.so.0
  • #16 g_object_new_valist
    from /lib/libgobject-2.0.so.0
  • #17 g_object_new
    from /lib/libgobject-2.0.so.0
  • #18 rb_ipod_source_new
    from /usr/lib/rhythmbox/plugins/libipod.so
  • #19 register_rb_plugin
    from /usr/lib/rhythmbox/plugins/libipod.so
  • #20 rb_marshal_OBJECT__OBJECT
  • #21 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #22 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #25 rb_removable_media_manager_get_type
  • #26 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #27 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #28 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #31 gnome_vfs_volume_monitor_emit_pre_unmount
    from /usr/lib/libgnomevfs-2.so.0
  • #32 gnome_vfs_volume_monitor_client_shutdown_private
    from /usr/lib/libgnomevfs-2.so.0
  • #33 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #34 dbus_server_setup_with_g_main
    from /usr/lib/libdbus-glib-1.so.2
  • #35 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #36 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #37 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #38 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 main
  • #0 __kernel_vsyscall

Comment 1 Philip Withnall 2007-06-03 10:33:16 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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