GNOME Bugzilla – Bug 452248
crash in Rhythmbox Music Player: closing
Last modified: 2007-06-29 23:04:13 UTC
What were you doing when the application crashed? closing 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 112816128 vsize: 112816128 resident: 44392448 share: 17379328 rss: 44392448 rss_rlim: 4294967295 CPU usage: start_time: 1183168120 rtime: 1142 utime: 1097 stime: 45 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 -1208657360 (LWP 3481)] [New Thread -1233359984 (LWP 3516)] [New Thread -1220338800 (LWP 3510)] [New Thread -1255150704 (LWP 3488)] (no debugging symbols found) 0x00700402 in __kernel_vsyscall ()
+ Trace 144604
Thread 2 (Thread -1233359984 (LWP 3516))
----------- .xsession-errors --------------------- (nautilus:3449): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! (rhythmbox:3481): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:3481): 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 ***