GNOME Bugzilla – Bug 436996
crash in Rhythmbox Music Player: openning another program...
Last modified: 2007-05-08 21:53:25 UTC
What were you doing when the application crashed? openning another programe (sound juicer) 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.2948.fc6 #1 SMP Fri Apr 27 18:53:15 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 145289216 vsize: 0 resident: 145289216 share: 0 rss: 46735360 rss_rlim: 0 CPU usage: start_time: 1178656811 rtime: 0 utime: 1861 stime: 0 cutime:1726 cstime: 0 timeout: 135 it_real_value: 0 frequency: 15 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 -1208477232 (LWP 27055)] [New Thread -1264141424 (LWP 4856)] [New Thread -1253651568 (LWP 13245)] [New Thread -1274631280 (LWP 28070)] (no debugging symbols found) 0x00c9b402 in __kernel_vsyscall ()
+ Trace 133144
Thread 2 (Thread -1264141424 (LWP 4856))
----------- .xsession-errors (6 sec old) --------------------- ** (nautilus:3016): WARNING **: destroyed file has call_when_ready pending inotify_add_watch: Permission denied ** (sound-juicer:3480): WARNING **: Error getting media type (rhythmbox:27055): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:27055): 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:4859): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 434003 ***