GNOME Bugzilla – Bug 451236
crash in Rhythmbox Music Player:
Last modified: 2007-06-26 22:51:25 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: 130904064 vsize: 130904064 resident: 39415808 share: 19283968 rss: 39415808 rss_rlim: 4294967295 CPU usage: start_time: 1182862527 rtime: 2009 utime: 1802 stime: 207 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 -1208665552 (LWP 10763)] [New Thread -1319171184 (LWP 26495)] [New Thread -1308681328 (LWP 16715)] [New Thread -1266721904 (LWP 13174)] [New Thread -1234441328 (LWP 10821)] (no debugging symbols found) 0x003fe402 in __kernel_vsyscall ()
+ Trace 143839
Thread 2 (Thread -1319171184 (LWP 26495))
----------- .xsession-errors (7 sec old) --------------------- --- Hash table keys for warning below: --> file:///home/Seremi/Desktop --> file:///home/Seremi (nautilus:19826): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 2 elements at quit time (keys above) Loading "installonlyn" plugin Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e00003 specified for 0x3e0007c (acroread). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e00003 specified for 0x3e001ed (Adobe Read). (rhythmbox:10763): 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... Xlib: unexpected async reply (sequence 0xf9a97)! --------------------------------------------------
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 ***