Bugzilla – Bug 113154
Evolution fails to load calendar when configured to go against a groupwise server (when using Gnome)
Last modified: 2008-05-22 18:19:04 UTC
I configured evolution to go against a groupwise server and it crashed when trying to download the email. This is in beta 3 of suse linux 10.0
Back trace?
Created attachment 47670 [details] back trace
Its crashing because of a calendar item. is it possible to get the console messages? * Run evolution from console using the command 'evolution-2.4' * get the console messages and put them here.
Created attachment 48025 [details] running from a terminal done
sorry, ignore that last attachement. I don't know what happened.
Created attachment 48029 [details] running from a terminal
I just put on beta 4 and I found that it no longer crashes, but the calendar won't load. The interesting thing is that the calendar will load if I use evolution in KDE. If I use evolution in GNOME, then I seem to have the problem.
Changing the summary to reflect the problem, re-assigning it to chenthill.
I have tested this in beta4 and the calendar gets loaded properly in GNOME. Please attach the soap traces from evolution-data-server by setting GROUPWISE_DEBUG=1. This can be done by starting evolution-data-server ina seperate terminal as follows $export GROUPWISE_DEBUG=1 $/opt/gnome/libexec/evolution-data-server-1.4 and run evolution in another terminal. Thanks.
This might take me a couple of days until it fails again. I also found out that it is happening in KDE as well. You mentioned that it was a calendar item, but I don't think it is. I think that it is certain emails that I receive. It appears to happen when it get stuck on certain email messages. Hoever, the next time it happens I will get a soap trace and a stack trace (now that I have the debugino packages).
Please understand that this is not a blocker. Reducing severity to `critical'.
(In reply to comment #11) > Please understand that this is not a blocker. > Reducing severity to `critical'. I marked it as a blocker because at the time it was crashing. I didn't have the debuginfo files at the time so I couldn't get a stack trace.
Created attachment 49058 [details] E2K_DEBUG=4 log
This working on RC1 for Nat earlier today.
I have not been able to reproduce this in RC4