GNOME Bugzilla – Bug 462998
crash in Rhythmbox Music Player:
Last modified: 2007-08-07 12:45:35 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: Clearlooks Icon Theme: Fedora Memory status: size: 108355584 vsize: 108355584 resident: 28659712 share: 16510976 rss: 28659712 rss_rlim: 4294967295 CPU usage: start_time: 1186080164 rtime: 352 utime: 320 stime: 32 cutime:2 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 -1208702416 (LWP 3050)] [New Thread -1276224624 (LWP 3135)] [New Thread -1220433008 (LWP 3132)] [New Thread -1255244912 (LWP 3130)] [New Thread -1244755056 (LWP 3058)] (no debugging symbols found) 0x007f4402 in __kernel_vsyscall ()
+ Trace 152469
Thread 4 (Thread -1255244912 (LWP 3130))
----------- .xsession-errors (18 sec old) --------------------- CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! --- Hash table keys for warning below: --> file:///root (nautilus:3101): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (rhythmbox:3050): 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 ***