GNOME Bugzilla – Bug 484900
crash in Rhythmbox Music Player: nada
Last modified: 2007-10-09 11:09:41 UTC
What were you doing when the application crashed? nada 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Gion Memory status: size: 182251520 vsize: 182251520 resident: 78139392 share: 30056448 rss: 78139392 rss_rlim: 4294967295 CPU usage: start_time: 1191874915 rtime: 1003 utime: 970 stime: 33 cutime:2 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 -1208493520 (LWP 3349)] [New Thread -1292297328 (LWP 3361)] [New Thread -1281807472 (LWP 3360)] [New Thread -1270166640 (LWP 3356)] [New Thread -1247151216 (LWP 3355)] [New Thread -1257641072 (LWP 3354)] (no debugging symbols found) 0x00e10402 in __kernel_vsyscall ()
+ Trace 168903
Thread 3 (Thread -1281807472 (LWP 3360))
----------- .xsession-errors --------------------- Input File : '/usr/share/amsn/skins/default/sounds/online.wav' Sample Size : 16-bit (2 bytes) Sample Encoding: signed (2's complement) Channels : 1 Sample Rate : 11025 Time: 00:00.74 [00:01.35] of 00:02.09 ( 35.6%) Output Buffer: 35.52K Time: 00:01.49 [00:00.60] of 00:02.09 ( 71.1%) Output Buffer: 71.19K Time: 00:02.09 [00:00.00] of 00:02.09 ( 100.0%) Output Buff Done. (rhythmbox:3349): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Dispositivo o recurso ocupado' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' aborting... --------------------------------------------------
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 ***