GNOME Bugzilla – Bug 444461
crash in Rhythmbox Music Player: Jamendo & gnome-vfs related
Last modified: 2007-06-05 22:10:15 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.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 197279744 vsize: 197279744 resident: 67772416 share: 36438016 rss: 67772416 rss_rlim: 4294967295 CPU usage: start_time: 1181070260 rtime: 2121 utime: 2016 stime: 105 cutime:5 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208882640 (LWP 13347)] [New Thread -1312466032 (LWP 13404)] [New Thread -1354818672 (LWP 13388)] [New Thread -1289479280 (LWP 13373)] [New Thread -1277260912 (LWP 13353)] 0x00eea402 in __kernel_vsyscall ()
+ Trace 138536
Thread 2 (Thread -1312466032 (LWP 13404))
----------- .xsession-errors --------------------- (rhythmbox:13347): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:13347): 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... warning: the debug information found in "/usr/lib/debug//lib/libpthread-2.6.so.debug" does not match "/lib/libpthread.so.0" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib/libc-2.6.so.debug" does not match "/lib/libc.so.6" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib/ld-2.6.so.debug" does not match "/lib/ld-linux.so.2" (CRC mismatch). --------------------------------------------------
Oops. Sorry about the messy report. Lets try this again: Started Rhythmbox (for the first time since upgrade to F7), noted the new Jamendo implementation, clicked on that, RB starts loading catalog, wait some time, get bored, quit RB --> *crash* $ gdb rhythmbox GNU gdb Red Hat Linux (6.6-8.fc7rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/rhythmbox [Thread debugging using libthread_db enabled] [New Thread -1208776144 (LWP 14123)] [New Thread -1277154416 (LWP 14127)] [New Thread -1287644272 (LWP 14128)] [Thread -1277154416 (LWP 14127) exited] [Thread -1287644272 (LWP 14128) exited] [New Thread -1287644272 (LWP 14129)] [New Thread -1277154416 (LWP 14130)] [Thread -1277154416 (LWP 14130) exited] [Thread -1287644272 (LWP 14129) exited] [New Thread -1287644272 (LWP 14131)] [New Thread -1277154416 (LWP 14132)] [New Thread -1300673648 (LWP 14133)] [Thread -1287644272 (LWP 14131) exited] [Thread -1277154416 (LWP 14132) exited] [New Thread -1277154416 (LWP 14134)] [New Thread -1287644272 (LWP 14135)] [Thread -1287644272 (LWP 14135) exited] [New Thread -1287644272 (LWP 14138)] (rhythmbox:14123): 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... Program received signal SIGABRT, Aborted. [Switching to Thread -1287644272 (LWP 14138)] 0x00b98402 in __kernel_vsyscall () (gdb) thread apply all bt
+ Trace 138541
Thread 1 (Thread -1208776144 (LWP 14123))
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 is fixed in 0.10.1. *** This bug has been marked as a duplicate of 434003 ***