What were you doing when the application crashed?
closing it down.. der i thought big brother would have known..


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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 560664576 vsize: 560664576 resident: 42483712 share: 20889600 rss: 42483712 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186055082 rtime: 302 utime: 276 stime: 26 cutime:1 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912709306560 (LWP 3473)]
[New Thread 1199884624 (LWP 3506)]
[New Thread 1084229968 (LWP 3496)]
[New Thread 1136945488 (LWP 3486)]
[New Thread 1105475920 (LWP 3482)]
[New Thread 1105209680 (LWP 3478)]
(no debugging symbols found)
0x00002aaab187f728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 152299

----------- .xsession-errors ---------------------
localuser:tim being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3237
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Introspect error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the ne
Loading "installonlyn" plugin
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Introspect error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the ne
(rhythmbox:3473): 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...
--------------------------------------------------