GNOME Bugzilla – Bug 542449
crash in Rhythmbox Music Player: Plugged IPod into doc, a...
Last modified: 2008-07-10 23:16:08 UTC
Version: 0.11.5 What were you doing when the application crashed? Plugged IPod into doc, and this happened Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Amaranth Icon Theme: Amaranth Memory status: size: 499666944 vsize: 499666944 resident: 45768704 share: 20488192 rss: 45768704 rss_rlim: 18446744073709551615 CPU usage: start_time: 1215727452 rtime: 50 utime: 44 stime: 6 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x2b617726fda0 (LWP 3807)] 0x00002b6169160edf in waitpid () from /lib/libpthread.so.0
+ Trace 202514
Thread 1 (Thread 0x2b617726fda0 (LWP 3807))
----------- .xsession-errors --------------------- ** (gnome-settings-daemon:3612): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory Window manager warning: Failed to read saved session file /home/john/.metacity/sessions/default0.ms: Failed to open file '/home/john/.metacity/sessions/default0.ms': No such file or directory seahorse nautilus module initialized 11 Initializing gnome-mount extension (rhythmbox:3719): Rhythmbox-WARNING **: Could not open device /dev/radio0 closing gnome-mount 0.7 ** (update-notifier:3654): WARNING **: no cdrom: disk Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400024 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
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 524985 ***