GNOME Bugzilla – Bug 497025
crash in Rhythmbox Music Player:
Last modified: 2007-11-18 14:49:48 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: 97738752 vsize: 97738752 resident: 27848704 share: 16318464 rss: 27848704 rss_rlim: 4294967295 CPU usage: start_time: 1195127630 rtime: 472 utime: 407 stime: 65 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 -1208452560 (LWP 2936)] [New Thread -1256199280 (LWP 2965)] [New Thread -1277178992 (LWP 2961)] [New Thread -1245709424 (LWP 2943)] (no debugging symbols found) 0x003a7402 in __kernel_vsyscall ()
+ Trace 177855
Thread 2 (Thread -1256199280 (LWP 2965))
----------- .xsession-errors (7 sec old) --------------------- Traceback (most recent call last): File "/usr/lib/rhythmbox/plugins/magnatune/MagnatuneSource.py", line 312, in __download_update_cb out.write(catalog.read("opt/magnatune/info/song_info.xml")) File "/usr/lib/python2.5/zipfile.py", line 471, in read zinfo = self.getinfo(name) File "/usr/lib/python2.5/zipfile.py", line 462, in getinfo return self.NameToInfo[name] KeyError: 'opt/magnatune/info/song_info.xml' (rhythmbox:2936): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:2936): 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 ***