Version: 2.18.0

What were you doing when the application crashed?
i'm changing the way my system log on and the displayed text 



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: 36823040 vsize: 36823040 resident: 13209600 share: 9310208 rss: 13209600 rss_rlim: 4294967295
CPU usage: start_time: 1152995410 rtime: 50 utime: 44 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/sbin/gnome-system-log'

(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 -1208477984 (LWP 3157)]
(no debugging symbols found)
0x005a1402 in __kernel_vsyscall ()

+ Trace 148312

----------- .xsession-errors (415 sec old) ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/dyn-24-194.nur.local:/tmp/.ICE-unix/2909
** (gnome-session:2909): WARNING **: Host name lookup failure on localhost.
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
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.
--------------------------------------------------