GNOME Bugzilla – Bug 485131
crash in Rhythmbox Music Player: Tentando abrir arquivo m...
Last modified: 2007-10-11 16:53:55 UTC
What were you doing when the application crashed? Tentando abrir arquivo mp3 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: 126603264 vsize: 126603264 resident: 36114432 share: 20262912 rss: 36114432 rss_rlim: 4294967295 CPU usage: start_time: 1191950797 rtime: 1105 utime: 207 stime: 898 cutime:0 cstime: 4 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 -1208145360 (LWP 2944)] [New Thread -1288717424 (LWP 3066)] [New Thread -1362146416 (LWP 3056)] [New Thread -1257583728 (LWP 3014)] [New Thread -1220355184 (LWP 3005)] [New Thread -1246758000 (LWP 2952)] (no debugging symbols found) 0x003e4402 in __kernel_vsyscall ()
+ Trace 169072
Thread 2 (Thread -1288717424 (LWP 3066))
----------- .xsession-errors (19 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:2944): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:2944): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Dispositivo ou recurso está ocupado' 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 ***