GNOME Bugzilla – Bug 470163
crash in Rhythmbox Music Player: Importing MP3s from a NT...
Last modified: 2007-08-27 12:36:44 UTC
What were you doing when the application crashed? Importing MP3s from a NTFS drive 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: 112979968 vsize: 112979968 resident: 30986240 share: 17649664 rss: 30986240 rss_rlim: 4294967295 CPU usage: start_time: 1188038093 rtime: 1149 utime: 1020 stime: 129 cutime:3 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 -1208788432 (LWP 3882)] [New Thread -1255855216 (LWP 3988)] [New Thread -1220478064 (LWP 3891)] [New Thread -1244800112 (LWP 3890)] (no debugging symbols found) 0x00439402 in __kernel_vsyscall ()
+ Trace 157799
Thread 2 (Thread -1255855216 (LWP 3988))
----------- .xsession-errors --------------------- 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:3882): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:3882): 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... (gnome-help:3896): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed --------------------------------------------------
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 ***