What were you doing when the application crashed?
Toggling screens, one where Add/Remove programs was opening


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

Memory status: size: 566136832 vsize: 566136832 resident: 35430400 share: 18305024 rss: 35430400 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193418971 rtime: 417 utime: 366 stime: 51 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 2934)]
[New Thread 1115699536 (LWP 2972)]
[New Thread 1084229968 (LWP 2970)]
[New Thread 1094719824 (LWP 2941)]
(no debugging symbols found)
0x00002aaab187f728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 173089

----------- .xsession-errors (20 sec old) ---------------------
localuser:probs being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2730
Loading "installonlyn" plugin
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
(rhythmbox:2934): 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...
--------------------------------------------------