What were you doing when the application crashed?
i ve watched many pictures.. i have seen this bug already on bugzilla for fc3-4. it had something to do with gconfd


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 109232128 vsize: 109232128 resident: 56176640 share: 14114816 rss: 56176640 rss_rlim: 4294967295
CPU usage: start_time: 1181261441 rtime: 3335 utime: 3119 stime: 216 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gthumb'

(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 -1209063168 (LWP 6004)]
[New Thread -1228252272 (LWP 6013)]
[New Thread -1227723888 (LWP 6012)]
[New Thread -1227195504 (LWP 6011)]
[New Thread -1226667120 (LWP 6010)]
[New Thread -1226138736 (LWP 6009)]
(no debugging symbols found)
0x00b8d402 in __kernel_vsyscall ()

+ Trace 139145

----------- .xsession-errors ---------------------
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x140fb29
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x4d
Cannot access memory at address 0xc
Cannot access memory at address 0xc
--------------------------------------------------