GNOME Bugzilla – Bug 466265
crash in Rhythmbox Music Player:
Last modified: 2007-08-23 10:42:30 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 96071680 vsize: 96071680 resident: 33501184 share: 22257664 rss: 33501184 rss_rlim: 4294967295 CPU usage: start_time: 1187016400 rtime: 363 utime: 132 stime: 231 cutime:0 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 -1208784336 (LWP 13062)] [New Thread -1244066928 (LWP 13088)] [New Thread -1220473968 (LWP 13086)] [New Thread -1232426096 (LWP 13074)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 154885
Thread 2 (Thread -1244066928 (LWP 13088))
----------- .xsession-errors --------------------- ** (nautilus:2494): WARNING **: No description found for mime type "x-special/socket" (file is "log"), please tell the gnome-vfs mailing list. ConsoleKit console-kit-daemon (pid 1917) is running... ConsoleKit console-kit-daemon (pid 1917) is running... ConsoleKit console-kit-daemon (pid 1917) is running... (gecko:12696): Gtk-CRITICAL **: gtk_main_quit: assertion `main_loops != NULL' failed (rhythmbox:13062): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' aborting... --------------------------------------------------
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 434003 ***