What were you doing when the application crashed?
closing app


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 133713920 vsize: 133713920 resident: 33234944 share: 19177472 rss: 33234944 rss_rlim: 4294967295
CPU usage: start_time: 1194317338 rtime: 564 utime: 47 stime: 517 cutime:0 cstime: 5 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 -1208444368 (LWP 2593)]
[New Thread -1266435184 (LWP 2617)]
[New Thread -1287414896 (LWP 2610)]
[New Thread -1266168944 (LWP 2606)]
[New Thread -1233966192 (LWP 2601)]
[New Thread -1244456048 (LWP 2600)]
(no debugging symbols found)
0x0017d402 in __kernel_vsyscall ()

+ Trace 175607

----------- .xsession-errors (6 sec old) ---------------------
Loading "installonlyn" plugin
wbs
name
start
finish
work
duration
slack
cost
assigned_to
(rhythmbox:2593): 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...
--------------------------------------------------