GNOME Bugzilla – Bug 444000
crash in Rhythmbox Music Player: closing the application
Last modified: 2007-06-04 22:23:05 UTC
What were you doing when the application crashed? closing the application 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:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 641118208 vsize: 641118208 resident: 88313856 share: 20475904 rss: 88313856 rss_rlim: 18446744073709551615 CPU usage: start_time: 1180972523 rtime: 2355 utime: 2139 stime: 216 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912499067552 (LWP 4003)] [New Thread 1147169104 (LWP 4235)] [New Thread 1157658960 (LWP 4219)] [New Thread 1084229968 (LWP 4176)] [New Thread 1115699536 (LWP 4093)] (no debugging symbols found) 0x0000003197e0c728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
+ Trace 138168
Thread 2 (Thread 1147169104 (LWP 4235))
----------- .xsession-errors --------------------- Checking Screen 0 ... Checking for GLX_SGIX_fbconfig : passed Checking for GLX_EXT_texture_from_pixmap : passed Checking for non power of two texture support : passed Checking maximum texture size : passed (8192x8192) Reloading options (rhythmbox:4003): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:4003): 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 ***