GNOME Bugzilla – Bug 509924
crash in Email:
Last modified: 2008-02-07 08:26:26 UTC
Version: 2.10 What were you doing when the application 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.23.12-52.fc7 #1 SMP Tue Dec 18 20:27:10 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 590442496 vsize: 590442496 resident: 48152576 share: 37871616 rss: 48152576 rss_rlim: 18446744073709551615 CPU usage: start_time: 1200499371 rtime: 125 utime: 112 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 46912506427920 (LWP 4168)] [New Thread 1105209680 (LWP 4176)] [New Thread 1084229968 (LWP 4173)] (no debugging symbols found) 0x00000030cbc0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 185574
Thread 1 (Thread 46912506427920 (LWP 4168))
----------- .xsession-errors (256 sec old) --------------------- Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 431459 ***