GNOME Bugzilla – Bug 491396
crash in Rhythmbox Music Player:
Last modified: 2007-10-30 12:42:26 UTC
What were you doing when the application crashed? 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: HighContrastInverse Icon Theme: HighContrastInverse Memory status: size: 154025984 vsize: 154025984 resident: 39723008 share: 20983808 rss: 39723008 rss_rlim: 4294967295 CPU usage: start_time: 1193668554 rtime: 572 utime: 520 stime: 52 cutime:1 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 -1208268240 (LWP 29363)] [New Thread -1321288816 (LWP 29451)] [New Thread -1300309104 (LWP 29410)] [New Thread -1244427376 (LWP 29404)] [New Thread -1289819248 (LWP 29400)] [New Thread -1257677936 (LWP 29369)] (no debugging symbols found) 0x00b03402 in __kernel_vsyscall ()
+ Trace 173685
Thread 2 (Thread -1321288816 (LWP 29451))
----------- .xsession-errors --------------------- ** (gnome-help:29436): WARNING **: failure: no device event controller found. ** (gnome-help:29436): WARNING **: failure: no device event controller found. (gnome-help:29436): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed (rhythmbox:29363): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:29363): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error '设备或资源忙' 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 ***