GNOME Bugzilla – Bug 351466
crash on Evolution
Last modified: 2008-09-02 07:04:38 UTC
What were you doing when the application crashed? Launched evo-2.8, which then appeared, displayed my calendar, and crashed before I did anything with it at all. Distribution: Fedora Core release 3 (Heidelberg) Gnome Release: 2.15.91 2006-08-11 (GARNOME) BugBuddy Version: 2.15.90 Memory status: size: 202932224 vsize: 202932224 resident: 30404608 share: 180215808 rss: 30404608 rss_rlim: -1 CPU usage: start_time: 1155652209 rtime: 133 utime: 118 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/ita/gar65/bin/evolution-2.8' Using host libthread_db library "/lib64/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 183018491936 (LWP 8903)] [New Thread 1076099424 (LWP 8909)] [Thread debugging using libthread_db enabled] [New Thread 183018491936 (LWP 8903)] [New Thread 1076099424 (LWP 8909)] [Thread debugging using libthread_db enabled] [New Thread 183018491936 (LWP 8903)] [New Thread 1076099424 (LWP 8909)] 0x0000002a99c62f7a in waitpid () from /lib64/tls/libpthread.so.0
+ Trace 70490
Thread 1 (Thread 183018491936 (LWP 8903))
first evolution function in the stacktrace is e_cal_finalize from evolution-data-server/calendar/libecal/e-cal.c
*** Bug 349680 has been marked as a duplicate of this bug. ***
*** Bug 354838 has been marked as a duplicate of this bug. ***
*** Bug 356129 has been marked as a duplicate of this bug. ***
*** Bug 359022 has been marked as a duplicate of this bug. ***
Detailed stack trace and some duplicates. Confirming.
Not sure if it helps at all, but im having the same issue running against our Exchange server. First, i get errors saying that the "The Evolutions Tasks have quit unexpectedly" and "the Evolution Calendar has quit unexpectedly" then if i try to click on the exchange calendar Evolution crashes about half the time; it just immediately disappears, no more errors. let me know how i can help
Bumping version to a stable release.
can anyone please try in current stable 2.22.3, thanks in advance.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME 2.22.3.1, thanks.