GNOME Bugzilla – Bug 473956
crash in Rhythmbox Music Player: closing it
Last modified: 2007-09-05 17:10:51 UTC
What were you doing when the application crashed? closing it Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve-BerriesAndCream Icon Theme: Human Memory status: size: 126070784 vsize: 126070784 resident: 40693760 share: 25538560 rss: 40693760 rss_rlim: 4294967295 CPU usage: start_time: 1189008141 rtime: 516 utime: 472 stime: 44 cutime:5 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 -1208358352 (LWP 3737)] [New Thread -1257399408 (LWP 3779)] [New Thread -1221801072 (LWP 3744)] [New Thread -1234822256 (LWP 3743)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 160673
Thread 2 (Thread -1257399408 (LWP 3779))
----------- .xsession-errors (122 sec old) --------------------- File "/usr/lib/python2.5/zipfile.py", line 462, in getinfo return self.NameToInfo[name] KeyError: 'opt/magnatune/info/song_info.xml' --- Hash table keys for warning below: --> file:///home/jsur (nautilus:3754): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (rhythmbox:3737): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:3737): 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 ***