GNOME Bugzilla – Bug 458417
crash in Rhythmbox Music Player: trying to play mp3 file
Last modified: 2007-07-20 11:34:14 UTC
What were you doing when the application crashed? trying to play mp3 file 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: 96808960 vsize: 96808960 resident: 27705344 share: 16441344 rss: 27705344 rss_rlim: 4294967295 CPU usage: start_time: 1184877920 rtime: 125 utime: 113 stime: 12 cutime:2 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 -1208092112 (LWP 4067)] [New Thread -1245451376 (LWP 4076)] [New Thread -1219605616 (LWP 4073)] [New Thread -1233810544 (LWP 4071)] (no debugging symbols found) 0x00a17402 in __kernel_vsyscall ()
+ Trace 149184
Thread 2 (Thread -1245451376 (LWP 4076))
----------- .xsession-errors --------------------- --- Hash table keys for warning below: --> file:///root (nautilus:3999): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --- Hash table keys for warning below: --> file:///root (nautilus:4059): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (rhythmbox:4067): 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 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 ***