GNOME Bugzilla – Bug 452500
crash in Rhythmbox Music Player: mp3-at akartam benne lej...
Last modified: 2007-06-30 22:56:20 UTC
What were you doing when the application crashed? mp3-at akartam benne lejatszani 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 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 162672640 vsize: 162672640 resident: 60973056 share: 31420416 rss: 60973056 rss_rlim: 4294967295 CPU usage: start_time: 1183195178 rtime: 1997 utime: 1860 stime: 137 cutime:4 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208227280 (LWP 4301)] [New Thread -1292874864 (LWP 4377)] [New Thread -1253049456 (LWP 4356)] [New Thread -1227977840 (LWP 4326)] [New Thread -1263539312 (LWP 4319)] (no debugging symbols found) 0x00ac8402 in __kernel_vsyscall ()
+ Trace 144808
Thread 2 (Thread -1292874864 (LWP 4377))
----------- .xsession-errors (6 sec old) --------------------- (rhythmbox:4301): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:4301): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Az eszköz vagy erőforrás foglalt' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' aborting... X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1408ee6 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 ***