GNOME Bugzilla – Bug 330279
Exchange account crashes when calendar is viewed
Last modified: 2006-02-13 18:11:42 UTC
From: John Russell <jjrussell@gmai.com> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.12.1 Subject: Exchange account crashes after about 1 minute Distribution: Gentoo Base System version 1.12.0_pre15 Package: Evolution Severity: major Version: GNOME2.12.2 2.4.x Gnome-Distributor: Gentoo Synopsis: Exchange account crashes after about 1 minute Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: There is something in my exchange account now that causes evolution to crash. I've been using evo 2.4.2 since it came out and others before that and It didn't used to do this. I'm not sure what about the account has changed. Steps to reproduce the crash: 1. Turn on evolution with the exchange account active 2. wait one minute or so 3. Evolution crashes with dialog to submit a bug Expected Results: It should not crash How often does this happen? It now happens every time I open evolution, but like I said, it used to work ok. It would crash on certain meeting acceptances but now it crashes every time it opens. Additional Information: Debugging Information: 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233717056 (LWP 23971)] [New Thread -1337992272 (LWP 24226)] [New Thread -1321206864 (LWP 24172)] [New Thread -1276060752 (LWP 24171)] [New Thread -1301238864 (LWP 24170)] [New Thread -1292846160 (LWP 23998)] [New Thread -1258882128 (LWP 23997)] [New Thread -1258615888 (LWP 23985)] [New Thread -1249760336 (LWP 23984)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 65985
Thread 1 (Thread -1233717056 (LWP 23971))
------- Bug created by bug-buddy at 2006-02-07 14:47 -------
hi john, thanks for reporting. make sure you're using the latest versions (evolution 2.4.2.1, evolution-data-server 1.4.2.1, evolution exchange 2.4.2). unique stacktrace according to simple-dup-finder.
I am using all the latest versions you mentioned. I recompiled evolution at all without stripping to get a more useful stack trace. I'll put it in an attachment so the comments aren't so long.
Created attachment 59081 [details] new stack trace without stripping No strip stack trace
the second stacktrace seems to be a bit similar to bug 313111 comment 2 which leads to bug 261154. however, it seems that it is a different bug then the original one here. :-/ reassigning to connector (=exchange module).
(uhm. dealing suddenly with two bugs in one report is bad. perhaps the first one isn't a connector issue and i should not have reassigned this. anyway. :-/ )
Created attachment 59094 [details] Stack trace after deleting all config and starting again Just to get started fresh, I killed all evo related processes deleted ~/.evolution ~/.gconf/apps/evolution and restarted gconfd-2 and recreated my exchange evolution account from scratch. Mail works just fine, but as soon as I switch to the calendar it crashes. I got another stack trace from that, which looks similar to the first but has some new stuff in it.
Created attachment 59095 [details] shell output during calendar crash Here is the shell output for the calendar crash after deleting all config and starting again. This corresponds to the second stack trace attachment.
committed the fix to cvs HEAD. *** This bug has been marked as a duplicate of 329866 ***
Thanks for getting to this. Will this fix be in the next point release or will this have to wait for the next major version? Thanks again.
hi john, yes, this will be included in the upcoming evolution 2.6.0 (scheduled for march 15th, 2006).