What were you doing when the application crashed?
I was looking at jamendo and opened there web page and at that point the page locked up.  I can send you my system hardwear if you need it.


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:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 96931840 vsize: 96931840 resident: 28106752 share: 16715776 rss: 28106752 rss_rlim: 4294967295
CPU usage: start_time: 1180602194 rtime: 385 utime: 344 stime: 41 cutime:4 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 -1208202704 (LWP 3066)]
[New Thread -1219613808 (LWP 3080)]
[New Thread -1245709424 (LWP 3077)]
[New Thread -1256199280 (LWP 3075)]
(no debugging symbols found)
0x00d86402 in __kernel_vsyscall ()

+ Trace 137085

----------- .xsession-errors (97 sec old) ---------------------
** (nm-applet:2965): CRITICAL **: network_device_is_wired: assertion `dev != NULL' failed
** (nm-applet:2965): CRITICAL **: network_device_is_wireless: assertion `dev != NULL' failed
** (nm-applet:2965): CRITICAL **: nma_get_connected_icon: assertion `dev != NULL' failed
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory
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
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200021 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------