GNOME Bugzilla – Bug 442790
crash in Rhythmbox Music Player: play mp3 file
Last modified: 2007-06-01 06:30:19 UTC
What were you doing when the application crashed? play mp3 file 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: 136425472 vsize: 136425472 resident: 32137216 share: 18968576 rss: 32137216 rss_rlim: 4294967295 CPU usage: start_time: 1180677213 rtime: 346 utime: 34 stime: 312 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 -1208661456 (LWP 10334)] [New Thread -1247437936 (LWP 10376)] [New Thread -1281365104 (LWP 10369)] [New Thread -1312834672 (LWP 10367)] [New Thread -1270875248 (LWP 10344)] (no debugging symbols found) 0x00f3f402 in __kernel_vsyscall ()
+ Trace 137149
Thread 2 (Thread -1247437936 (LWP 10376))
----------- .xsession-errors (21 sec old) --------------------- --- Hash table keys for warning below: --> file:///home/kevin (nautilus:10274): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --- Hash table keys for warning below: --> file:///home/kevin (nautilus:10294): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) closing (rhythmbox:10334): 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 ***