GNOME Bugzilla – Bug 448893
crash in Rhythmbox Music Player: I was just erasing the e...
Last modified: 2007-06-18 21:52:26 UTC
What were you doing when the application crashed? I was just erasing the error message in Rhytmbox that told me that mp3 plugin were not found Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 109182976 vsize: 109182976 resident: 42070016 share: 23752704 rss: 42070016 rss_rlim: 4294967295 CPU usage: start_time: 1182196741 rtime: 918 utime: 860 stime: 58 cutime:6 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 -1208681936 (LWP 7959)] [New Thread -1239233648 (LWP 8038)] [New Thread -1225094256 (LWP 8033)] [New Thread -1249723504 (LWP 7968)] (no debugging symbols found) 0x0031e402 in __kernel_vsyscall ()
+ Trace 141965
Thread 2 (Thread -1239233648 (LWP 8038))
----------- .xsession-errors (7 sec old) --------------------- (process:8022): 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:7959): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:7959): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Périphérique ou ressource occupé' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' aborting... --------------------------------------------------
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 434003 ***