What were you doing when the application crashed?
when the connect mp3 files to USB flash disk, music player wasn't play and it's 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.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: 643457024 vsize: 643457024 resident: 65400832 share: 21127168 rss: 65400832 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181465751 rtime: 1151 utime: 1059 stime: 92 cutime:2 cstime: 2 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 46912709368000 (LWP 3321)]
[New Thread 1147435344 (LWP 3367)]
[New Thread 1084229968 (LWP 3360)]
[New Thread 1126455632 (LWP 3335)]
[New Thread 1105209680 (LWP 3330)]
[New Thread 1094719824 (LWP 3326)]
(no debugging symbols found)
0x00002aaab1b63956 in poll () from /lib64/libc.so.6

+ Trace 139737

----------- .xsession-errors ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3006
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
closing
closing
closing
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x1000577 (muzik); these messages lack timestamps and therefore suck.
(rhythmbox:3321): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:3321): 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...
Xlib: unexpected async reply (sequence 0x21aa4)!
--------------------------------------------------