GNOME Bugzilla – Bug 443327
crash in Rhythmbox Music Player: Trying to play mp3 files...
Last modified: 2007-06-02 22:56:43 UTC
What were you doing when the application crashed? Trying to play mp3 files from my Iriver, i right clicked the file, opened with and rhythmbox music player. 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 542654464 vsize: 542654464 resident: 38182912 share: 18812928 rss: 38182912 rss_rlim: 18446744073709551615 CPU usage: start_time: 1180817982 rtime: 667 utime: 588 stime: 79 cutime:2 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 46912527319872 (LWP 3018)] [New Thread 1126189392 (LWP 3090)] [New Thread 1147169104 (LWP 3087)] [New Thread 1115699536 (LWP 3079)] [New Thread 1094719824 (LWP 3037)] (no debugging symbols found) 0x00000035f040c728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
+ Trace 137606
Thread 2 (Thread 1126189392 (LWP 3090))
----------- .xsession-errors --------------------- GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' aborting... X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x64 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1402c5b X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x1402c5b --------------------------------------------------
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 ***