GNOME Bugzilla – Bug 375065
crash in Evolution: Nothing. I switched fro...
Last modified: 2007-01-17 17:04:34 UTC
What were you doing when the application crashed? Nothing. I switched from 1 workspace (which was empty) to the one Evolution was on. Not sure I can reproduce. If it matters, Evolution was running on my second monitor (DISPLAY=:0.1), which isn't running xinerama. Simple Dup Finder reports no duplicates on the stacktrace. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 338673664 vsize: 0 resident: 338673664 share: 0 rss: 76058624 rss_rlim: 0 CPU usage: start_time: 1163366716 rtime: 0 utime: 36284 stime: 0 cutime:32473 cstime: 0 timeout: 3811 it_real_value: 0 frequency: 588 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233307984 (LWP 5232)] [New Thread -1427154016 (LWP 12636)] [New Thread -1368392800 (LWP 5882)] [New Thread -1354052704 (LWP 5255)] [New Thread -1353786464 (LWP 5253)] [New Thread -1344996448 (LWP 5250)] [New Thread -1296278624 (LWP 5246)] [New Thread -1287373920 (LWP 5245)] [New Thread -1278944352 (LWP 5242)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 86330
Thread 8 (Thread -1287373920 (LWP 5245))
A little more information. Upon trying to restart Evolution again, I received another crash (with the same stacktrace). Starting Evo again after that it launched okay, but repeatedly showed "Summary Folder Mismatch, Even after sync" warning dailogs. Shutting it down and starting it again and the warning disappeared. Evo seems to be running okay now.
I think we've got a bunch of reports of problems with summary folder mismatches. Shall we keep this report open even though the crash is probably just fallout from a different problem?
*** Bug 397226 has been marked as a duplicate of this bug. ***
*** Bug 397291 has been marked as a duplicate of this bug. ***
*** Bug 397287 has been marked as a duplicate of this bug. ***
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 348149 ***