| Summary: | Evolution 2.0 crashes when accessing an Exchange Calendar | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | James Ward <james> |
| Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
James Ward
2004-10-12 07:36:16 UTC
This bug seems to have been reported to the Ximian bugzilla also: http://bugs.ximian.com/show_bug.cgi?id=67519 Just as that user points out, it also worked fine in previous versions of Evolution. maybe you could do a better job @ getting a backtrace ? Hmmm. I tried to attach to the evolution-exchange-storage process in gdb, but it hung evolution... Sorry I have never done this before. Any hints on getting a bt? I reset it for a reason ok ? Sorry, I didn't realize that you reset it. I thought I had initially set it incorrectly. Today I realized something very strange... I got a meeting notification, but still can't get the calendar to come up. So evolution-alarm-notify can talk to the calendar correctly, but evolution can't. Very weird. I think I fixed it... I noticed I had a few older packages laying around, so I removed them: mail-client/evolution-1.4.6 net-mail/evolution-data-server-0.0.91 mail-client/ximian-connector-1.4.7.2 Now my exchange calendar works in Evolution!!! I take that back. It worked once, but now it doesn't work again. I figured out how to get some information on the problem. I did: jamesw@taco ~ $ export E2K_DEBUG=5 jamesw@taco ~ $ /usr/libexec/evolution/2.0/evolution-exchange-storage And I get: Evolution Exchange Storage up and running (evolution-exchange-storage:9236): libedata-cal-WARNING **: e-data-cal-view.c:249: Starting new query (evolution-exchange-storage:9236): libedata-cal-WARNING **: e-data-cal-view.c:249: Starting new query (evolution-exchange-storage:9236): libedata-cal-WARNING **: e-data-cal-view.c:249: Starting new query (evolution-exchange-storage:9236): libecal-CRITICAL **: file e-cal-component.c: line 4656 (e_cal_component_has_alarms): assertion `priv->icalcomp != NULL' failed (evolution-exchange-storage:9236): libedata-cal-WARNING **: e-data-cal-view.c:249: Starting new query (evolution-exchange-storage:9236): libecal-CRITICAL **: file e-cal-component.c: line 2321 (e_cal_component_get_dtstart): assertion `priv->icalcomp != NULL' failed (evolution-exchange-storage:9236): libecal-CRITICAL **: file e-cal-component.c: line 2205 (e_cal_component_get_dtend): assertion `priv->icalcomp != NULL' failed (evolution-exchange-storage:9236): libecal-CRITICAL **: file e-cal-component.c: line 3396 (e_cal_component_has_rdates): assertion `priv->icalcomp != NULL' failed (evolution-exchange-storage:9236): libecal-CRITICAL **: file e-cal-component.c: line 3489 (e_cal_component_has_rrules): assertion `priv->icalcomp != NULL' failed (evolution-exchange-storage:9236): libecal-CRITICAL **: file e-cal-component.c: line 2677 (e_cal_component_has_exdates): assertion `priv->icalcomp != NULL' failed (evolution-exchange-storage:9236): libecal-CRITICAL **: file e-cal-component.c: line 2838 (e_cal_component_has_exrules): assertion `priv->icalcomp != NULL' failed *** glibc detected *** free(): invalid pointer: 0xb6c79b84 *** I believe that the user posting that bug is also a Gentoo user. And since I can't find anyone else who has encountered this issue, I am assuming this is probably a Gentoo specific bug. not exactly, the first report was from fedora core 2 This is upstream, and is reportedly fixed in evolution 2.2. Any chance you could unmask evo 2.2 (it's in p.mask at the moment) and try it out? Thanks. No reply, try evo-2.2 as suggested in my last comment. |
