GNOME Bugzilla – Bug 462670
crash in Rhythmbox Music Player: cant play *.wma files
Last modified: 2007-08-02 11:25:51 UTC
What were you doing when the application crashed? cant play *.wma files 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: 123445248 vsize: 123445248 resident: 44466176 share: 17399808 rss: 44466176 rss_rlim: 4294967295 CPU usage: start_time: 1186082161 rtime: 1144 utime: 1081 stime: 63 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 -1208886736 (LWP 4775)] [New Thread -1246159984 (LWP 4840)] [New Thread -1256649840 (LWP 4806)] [New Thread -1234859120 (LWP 4780)] (no debugging symbols found) 0x00f27402 in __kernel_vsyscall ()
+ Trace 152228
Thread 2 (Thread -1246159984 (LWP 4840))
----------- .xsession-errors --------------------- (yelp:3524): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed --- Hash table keys for warning below: --> file:///home/Viewcom (nautilus:4632): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (rhythmbox:4775): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:4775): 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 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 ***