What were you doing when the application crashed?



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.20-2925.9.fc7xen #1 SMP Tue May 22 09:29:36 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 623796224 vsize: 623796224 resident: 74301440 share: 18653184 rss: 74301440 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181223867 rtime: 3011 utime: 2460 stime: 551 cutime:0 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 46912496376384 (LWP 29174)]
[New Thread 1136679248 (LWP 29288)]
[New Thread 1105209680 (LWP 29283)]
[New Thread 1094719824 (LWP 29186)]
[New Thread 1084229968 (LWP 29179)]
(no debugging symbols found)
0x00000037bea0c728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 139066

----------- .xsession-errors ---------------------
** Message: don't know how to handle audio/x-mod
** Message: don't know how to handle audio/x-mod
** Message: don't know how to handle audio/x-mod
** Message: don't know how to handle audio/x-mod
** Message: don't know how to handle audio/x-mod
** Message: don't know how to handle audio/x-mod
** Message: don't know how to handle audio/x-mod
** Message: don't know how to handle audio/x-mod
** Message: don't know how to handle audio/x-mod
** Message: don't know how to handle audio/x-mod
** Message: don't know how to handle audio/x-mod
** Message: don't know how to handle audio/x-mod
** Message: don't know how to handle audio/x-mod
...Too much output, ignoring rest...
--------------------------------------------------