GNOME Bugzilla – Bug 307486
Crash when displaying calendars
Last modified: 2006-01-20 20:31:57 UTC
Distribution: Debian testing/unstable Package: Evolution Severity: normal Version: GNOME2.10.1 unspecified Gnome-Distributor: Debian Synopsis: Crash when displaying calendars Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: For some reason my calendars show up not-displayed - no checkmarks. When I try to check them so they get displayed, I get a warning that the calendar backend has crashed, then a few moments later, evolution crashes. Steps to reproduce the crash: 1. Start evolution 2. Try to enable calendars 3. Expected Results: Calendars show up How often does this happen? Always Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.2' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1229389696 (LWP 13563)] [New Thread -1344275536 (LWP 13639)] [New Thread -1255146576 (LWP 13611)] [New Thread -1263535184 (LWP 13610)] [New Thread -1297343568 (LWP 13582)] [New Thread -1288954960 (LWP 13581)] [New Thread -1272054864 (LWP 13579)] [New Thread -1245140048 (LWP 13576)] [New Thread -1236751440 (LWP 13575)] 0xb6fda561 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 60934
Thread 1 (Thread -1229389696 (LWP 13563))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-13 11:14 UTC -------
Matt: This happens with personal calendar or web calendar or groupwise calendar ? Whats the evolution version you are using ?
This was with both the CVS version and 2.2.2. I think it has to do with a corrupted file somewhere - after a crash is when it started happening, and by deleting the calendar and task folders under ~/.evolution, it seems to have stopped crashing (of course I lost all my info). I haven't filled the now empty calendars back up yet, but it seems to be more stable now. Maybe the calendar or task files got corrupted, and the calendar backend couldn't take it? I did notice that in 2.2.2, I got a message saying that the calendar backend had crashed before evolution crashed, with no such message under the CVS version.
BTW, these were personal calendars, sorry. Evolution was the only program that read/wrote to them.
reopening
Could you please use evolution-2.4.x which is the latest stable version ? There is no active development going on in evolution-2.2.
Please reopen the bug if you find it happening.