GNOME Bugzilla – Bug 543980
crash in Rhythmbox Music Player:
Last modified: 2008-07-21 22:04:32 UTC
Version: 0.11.5 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-07-10 (Parsix) BugBuddy Version: 2.22.0 System: Linux 2.6.24-parsix64-23 #1 SMP PREEMPT Fri Jun 13 08:56:10 CEST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Aurora-Midnight Icon Theme: OxygenRefit2-green-version Memory status: size: 622477312 vsize: 622477312 resident: 40849408 share: 21024768 rss: 40849408 rss_rlim: 18446744073709551615 CPU usage: start_time: 1216643105 rtime: 72 utime: 61 stime: 11 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2accd1b56e60 (LWP 4321)] (no debugging symbols found) 0x00002accc3e96edf in waitpid () from /lib/libpthread.so.0
+ Trace 203391
Thread 1 (Thread 0x2accd1b56e60 (LWP 4321))
----------- .xsession-errors --------------------- (rhythmbox:4300): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running (rhythmbox:4300): Rhythmbox-WARNING **: Could not open device /dev/radio0 Rhythmbox: could not connect to socket Rhythmbox: No such file or directory (rhythmbox:4300): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed (rhythmbox:4321): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running (rhythmbox:4321): Rhythmbox-WARNING **: Could not open device /dev/radio0 Rhythmbox: could not connect to socket Rhythmbox: No such file or directory (rhythmbox:4321): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed --------------------------------------------------
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 ***