GNOME Bugzilla – Bug 433677
crash in Rhythmbox Music Player:
Last modified: 2007-04-28 09:40:58 UTC
What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.20-1.2944.fc6 #1 SMP Tue Apr 10 17:27:49 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 166076416 vsize: 0 resident: 166076416 share: 0 rss: 50163712 rss_rlim: 0 CPU usage: start_time: 1177614593 rtime: 0 utime: 1579 stime: 0 cutime:1411 cstime: 0 timeout: 168 it_real_value: 0 frequency: 2 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 -1208408352 (LWP 6304)] [New Thread -1317012592 (LWP 6343)] [New Thread -1260635248 (LWP 6331)] [New Thread -1271624816 (LWP 6326)] [New Thread -1247057008 (LWP 6312)] (no debugging symbols found) 0x0098b402 in __kernel_vsyscall ()
+ Trace 130753
Thread 2 (Thread -1317012592 (LWP 6343))
----------- .xsession-errors (9 sec old) --------------------- DCOP: unregister 'anonymous-6297' DCOP: unregister 'kbuildsycoca' kdeinit: PID 6297 terminated. (rhythmbox:6304): Rhythmbox-WARNING **: Couldn't get menu widget for /BrowserSourcePopup ** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3 (rhythmbox:6304): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:6304): 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... ** (bug-buddy:6346): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
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 ***