What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 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: 460374016 vsize: 460374016 resident: 41533440 share: 23805952 rss: 41533440 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189274008 rtime: 372 utime: 334 stime: 38 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 46912505731856 (LWP 3169)]
[New Thread 1105209680 (LWP 3182)]
[New Thread 1084229968 (LWP 3181)]
[New Thread 1094719824 (LWP 3174)]
(no debugging symbols found)
0x0000003a5b00c808 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 161378

----------- .xsession-errors (1851 sec old) ---------------------
                 System error: Device or resource busy
scsi_read error: sector=2898 length=1 retry=6
                 Sense key: 2 ASC: 3a ASCQ: 0
                 Transport error: Device busy
                 System error: Device or resource busy
scsi_read error: sector=2898 length=1 retry=7
                 Sense key: 2 ASC: 3a ASCQ: 0
                 Transport error: Device busy
                 System error: Device or resource busy
scsi_read error: sector=2898 length=1 retry=8
                 Sense key: 2 ASC: 3a ASCQ: 0
                 Transport error: Device busy
                 System error: Device or resource busy
...Too much output, ignoring rest...
--------------------------------------------------