GNOME Bugzilla – Bug 450920
crash in Rhythmbox Music Player:
Last modified: 2007-06-25 22:29:33 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 577773568 vsize: 577773568 resident: 69595136 share: 29900800 rss: 69595136 rss_rlim: 18446744073709551615 CPU usage: start_time: 1182782300 rtime: 566 utime: 515 stime: 51 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496503360 (LWP 6118)] [New Thread 1105209680 (LWP 6146)] [New Thread 1084229968 (LWP 6135)] [New Thread 1094719824 (LWP 6132)] (no debugging symbols found) 0x00000034ee00c728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
+ Trace 143585
Thread 2 (Thread 1105209680 (LWP 6146))
----------- .xsession-errors --------------------- (rhythmbox:6118): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:6118): 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... X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x140c518 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x64 --------------------------------------------------
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 ***