GNOME Bugzilla – Bug 468042
crash in Rhythmbox Music Player: esperando
Last modified: 2007-08-20 08:52:34 UTC
What were you doing when the application crashed? esperando 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: Glossy Icon Theme: gnome Memory status: size: 154714112 vsize: 154714112 resident: 30748672 share: 17694720 rss: 30748672 rss_rlim: 4294967295 CPU usage: start_time: 1187466837 rtime: 593 utime: 527 stime: 66 cutime:4 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 -1209124304 (LWP 3923)] [New Thread -1310037104 (LWP 3956)] [New Thread -1289057392 (LWP 3945)] [New Thread -1299547248 (LWP 3944)] [New Thread -1278301296 (LWP 3941)] [New Thread -1288791152 (LWP 3940)] [New Thread -1256928368 (LWP 3936)] [New Thread -1246102640 (LWP 3931)] (no debugging symbols found) 0x003e9402 in __kernel_vsyscall ()
+ Trace 156215
Thread 2 (Thread -1310037104 (LWP 3956))
----------- .xsession-errors (9 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:3923): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:3923): 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... --------------------------------------------------
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 ***