GNOME Bugzilla – Bug 479412
crash in Rhythmbox Music Player:
Last modified: 2007-09-24 16:48:40 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.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 614977536 vsize: 614977536 resident: 48316416 share: 26406912 rss: 48316416 rss_rlim: 18446744073709551615 CPU usage: start_time: 1190514596 rtime: 339 utime: 301 stime: 38 cutime:1 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496355280 (LWP 5298)] [New Thread 1147435344 (LWP 5343)] [New Thread 1126455632 (LWP 5312)] [New Thread 1115699536 (LWP 5308)] [New Thread 1094719824 (LWP 5304)] (no debugging symbols found) 0x000000394900c808 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
+ Trace 164759
Thread 2 (Thread 1147435344 (LWP 5343))
----------- .xsession-errors --------------------- return self.NameToInfo[name] KeyError: 'opt/magnatune/info/song_info.xml' (rhythmbox:5298): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:5298): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Dispositivo o recurso ocupado' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' aborting... (pidgin:2970): GStreamer-CRITICAL **: Trying to dispose element fakesink, but it is not in the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. --------------------------------------------------
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 ***