GNOME Bugzilla – Bug 473207
crash in Rhythmbox Music Player: open a MP3 file
Last modified: 2007-09-05 17:10:51 UTC
What were you doing when the application crashed? open a 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 135753728 vsize: 135753728 resident: 35180544 share: 20189184 rss: 35180544 rss_rlim: 4294967295 CPU usage: start_time: 1188832367 rtime: 346 utime: 160 stime: 186 cutime:2 cstime: 1 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 -1208772048 (LWP 7930)] [New Thread -1252590704 (LWP 7980)] [New Thread -1242100848 (LWP 7957)] [New Thread -1266312304 (LWP 7939)] (no debugging symbols found) 0x0045a402 in __kernel_vsyscall ()
+ Trace 160108
Thread 2 (Thread -1252590704 (LWP 7980))
----------- .xsession-errors (15 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:7930): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:7930): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error '设备或资源忙' 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 ***