GNOME Bugzilla – Bug 548396
Evolution-data-server crashed : at start up
Last modified: 2009-04-06 16:25:01 UTC
Evolution 2.23.90 (Exchange backend) I changed system date and started evolution. Gdb traces of eds process ** libecal:ERROR:e-cal-util.c:317:compute_alarm_range: assertion failed: (*alarm_start <= *alarm_end) Program received signal SIGABRT, Aborted. [Switching to Thread 0xb6f178f0 (LWP 32519)] 0xffffe430 in __kernel_vsyscall () (gdb) t a a bt
+ Trace 205335
Evolution also crashed just after that. Gdb traces of evo process Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb64616e0 (LWP 32748)] connection_listen_cb (object=0x808f728, user_data=0x84dd5a0) at e-component-listener.c:48 48 switch (ORBit_small_get_connection_status (cl->priv->component)) { (gdb) t a a bt
+ Trace 205336
Thread 1 (Thread 0xb64616e0 (LWP 32748))
the crash is similar to bug #404626
*** Bug 554610 has been marked as a duplicate of this bug. ***
Yeah, evo doesn't play well with link_connection_emit_broken, it has been emitted because of the crash of eds. One question, was eds/alarm notification running before you changed the time? Maybe it doesn't matter, I'm just curious. none the less, I see you reported the crash in eds already, in bug #491755.
*** Bug 575692 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 491755 ***