GNOME Bugzilla – Bug 497952
crash in Rhythmbox Music Player: Apenas fechei o programa...
Last modified: 2007-11-25 11:13:08 UTC
What were you doing when the application crashed? Apenas fechei o programa. 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:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 125673472 vsize: 125673472 resident: 28131328 share: 16183296 rss: 28131328 rss_rlim: 4294967295 CPU usage: start_time: 1195406809 rtime: 437 utime: 95 stime: 342 cutime:1 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 -1208993232 (LWP 2557)] [New Thread -1274532976 (LWP 2574)] [New Thread -1264043120 (LWP 2573)] [New Thread -1241683056 (LWP 2571)] [New Thread -1227199600 (LWP 2568)] [New Thread -1252983920 (LWP 2566)] (no debugging symbols found) 0x00b2b402 in __kernel_vsyscall ()
+ Trace 178548
Thread 3 (Thread -1264043120 (LWP 2573))
----------- .xsession-errors (12 sec old) --------------------- localuser:norton being added to access control list SESSION_MANAGER=local/nsg31:/tmp/.ICE-unix/2320 Loading "installonlyn" plugin (rhythmbox:2557): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Dispositivo ou recurso está ocupado' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' aborting... --------------------------------------------------
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 ***