GNOME Bugzilla – Bug 477485
crash in Tasks:
Last modified: 2007-09-24 17:40:50 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 130834432 vsize: 130834432 resident: 38981632 share: 32477184 rss: 38981632 rss_rlim: 4294967295 CPU usage: start_time: 1189951908 rtime: 79 utime: 72 stime: 7 cutime:2 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208703264 (LWP 14408)] [New Thread -1270887536 (LWP 14433)] [New Thread -1249907824 (LWP 14430)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 163323
Thread 1 (Thread -1208703264 (LWP 14408))
----------- .xsession-errors (27092 sec old) --------------------- 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". 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". 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 364700 ***