GNOME Bugzilla – Bug 532015
crash in Rhythmbox Music Player: Plugged in my iPod to my...
Last modified: 2008-05-09 22:44:53 UTC
Version: 0.11.5 What were you doing when the application crashed? Plugged in my iPod to my system with Rhythmbox already open. Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686-bigmem #1 SMP Sat Apr 19 01:23:53 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: ThinIce Icon Theme: Mist Memory status: size: 86913024 vsize: 86913024 resident: 36786176 share: 18358272 rss: 36786176 rss_rlim: 4294967295 CPU usage: start_time: 1210186796 rtime: 116 utime: 107 stime: 9 cutime:1 cstime: 0 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb660a960 (LWP 9069)] [New Thread 0xb3db9b90 (LWP 9147)] [New Thread 0xb47efb90 (LWP 9077)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197158
Thread 1 (Thread 0xb660a960 (LWP 9069))
----------- .xsession-errors --------------------- ** (update-notifier:4055): WARNING **: no cdrom: disk Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c0001e (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. closing gnome-mount 0.7 (synaptic:8373): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed Window manager warning: last_focus_time (3300823341) is greater than comparison timestamp (3300823268). This most likely represents a buggy client sending inaccurate timestamps in messages such as _N ** (update-notifier:4055): WARNING **: no cdrom: disk (rhythmbox:9069): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed --------------------------------------------------
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 524985 ***