GNOME Bugzilla – Bug 443416
crash in Rhythmbox Music Player:
Last modified: 2007-06-03 10:47:12 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 97017856 vsize: 97017856 resident: 27828224 share: 16490496 rss: 27828224 rss_rlim: 4294967295 CPU usage: start_time: 1180839564 rtime: 215 utime: 188 stime: 27 cutime:3 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208894928 (LWP 3426)] [New Thread -1231074416 (LWP 3438)] [New Thread -1220584560 (LWP 3435)] [New Thread -1244906608 (LWP 3434)] (no debugging symbols found) 0x00300402 in __kernel_vsyscall ()
+ Trace 137683
Thread 2 (Thread -1231074416 (LWP 3438))
----------- .xsession-errors (7 sec old) --------------------- as very first thing in its main() function. Please file a bug against this application. (process:3368): GStreamer-WARNING **: The GStreamer function gst_init_get_option_group() was called, but the GLib threading system has not been initialised yet, something that must happen before any other GLib function is called. The application needs to be fixed so that it calls if (!g_thread_supported ()) g_thread_init(NULL); as very first thing in its main() function. Please file a bug against this application. (rhythmbox:3426): 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 ***