GNOME Bugzilla – Bug 509505
crash in Rhythmbox Music Player: !!
Last modified: 2008-01-15 07:23:31 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: 137113600 vsize: 137113600 resident: 37122048 share: 20549632 rss: 37122048 rss_rlim: 4294967295 CPU usage: start_time: 1200351242 rtime: 884 utime: 812 stime: 72 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 -1208362448 (LWP 3693)] [New Thread -1319236720 (LWP 3831)] [New Thread -1244566640 (LWP 3749)] [New Thread -1287292016 (LWP 3732)] [New Thread -1231221872 (LWP 3722)] [New Thread -1220732016 (LWP 3698)] (no debugging symbols found) 0x00907402 in __kernel_vsyscall ()
+ Trace 185358
Thread 2 (Thread -1319236720 (LWP 3831))
----------- .xsession-errors --------------------- most likely the X server was shut down or you killed/destroyed the application. --- Hash table keys for warning below: --> file:///home/xbit (nautilus:3795): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Loading "installonlyn" plugin (rhythmbox:3693): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:3693): 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 ***