GNOME Bugzilla – Bug 578333
crash in Evolution Mail and Calendar: Ok, I tried to run evolu...
Last modified: 2009-04-08 05:42:22 UTC
What were you doing when the application crashed? Ok, I tried to run evolution again after it crashed. I'll try blowing renaming my configuration and starting over... Distribution: Ubuntu 9.04 (jaunty) Gnome Release: 2.26.0 2009-03-19 (Ubuntu) BugBuddy Version: 2.26.0 System: Linux 2.6.28-dasARCH #1 SMP PREEMPT Mon Apr 6 00:09:21 CDT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 613216256 vsize: 613216256 resident: 38432768 share: 22765568 rss: 38432768 rss_rlim: 18446744073709551615 CPU usage: start_time: 1239168109 rtime: 65 utime: 57 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7fd28eaaa7f0 (LWP 26612)] [New Thread 0x7fd27188f950 (LWP 26625)] 0x00007fd288e98bbf in waitpid () from /lib/libpthread.so.0
+ Trace 214280
Thread 1 (Thread 0x7fd28eaaa7f0 (LWP 26612))
----------- .xsession-errors (1089 sec old) --------------------- Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Root Privileges granted. Uid is: 1000 Root privileges retired. Database Update Performed DB Update Finished --------------------------------------------------
This crash is the followup to Bug 578331 so I'm marking it as a duplicate and resolving it. *** This bug has been marked as a duplicate of 578331 ***