GNOME Bugzilla – Bug 490401
crash in Rhythmbox Music Player: nothing complicated, onl...
Last modified: 2007-10-27 04:03:37 UTC
What were you doing when the application crashed? nothing complicated, only click the close button. 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 536682496 vsize: 536682496 resident: 33329152 share: 16392192 rss: 33329152 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193362341 rtime: 352 utime: 234 stime: 118 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496331328 (LWP 4838)] [New Thread 1115699536 (LWP 4854)] [New Thread 1105209680 (LWP 4850)] [New Thread 1094719824 (LWP 4845)] (no debugging symbols found) 0x000000336360c728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
+ Trace 172953
Thread 2 (Thread 1115699536 (LWP 4854))
----------- .xsession-errors (14 sec old) --------------------- as very first thing in its main() function. Please file a bug against this application. compiz: No GLXFBConfig for default depth, this isn't going to work. compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 gtk-window-decorator: Could not acquire decoration manager selection on screen 0 display ":0.0" compiz: No GLXFBConfig for default depth, this isn't going to work. compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 Loading "installonlyn" plugin (rhythmbox:4838): 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 ***