What were you doing when the application crashed?
am trying to get codec for player


Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.3104.fc7 #1 SMP Sat Apr 21 22:20:43 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 111632384 vsize: 111632384 resident: 43950080 share: 16969728 rss: 43950080 rss_rlim: 4294967295
CPU usage: start_time: 1182530659 rtime: 1090 utime: 990 stime: 100 cutime:2 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208497920 (LWP 3817)]
[New Thread -1245717616 (LWP 3836)]
[New Thread -1219806320 (LWP 3822)]
[New Thread -1234076784 (LWP 3821)]
(no debugging symbols found)
0x00f56402 in __kernel_vsyscall ()

+ Trace 142807

----------- .xsession-errors ---------------------
    for repo in self.repos.listGroupsEnabled():
  File "/usr/lib/python2.5/site-packages/yumerror getting update info:  Cannot find a valid baseurl for repo: development
error getting update info:  Cannot find a valid baseurl for repo: development
error getting update info:  Cannot find a valid baseurl for repo: development
compiz: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager.
compiz: No manageable screens found on display :0.0
gtk-window-decorator: Could not acquire decoration manager selection on screen 0 display ":0.0"
compiz: pixmap 0x3a0157d can't be bound to texture
(rhythmbox:3817): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:3817): 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...
--------------------------------------------------