Hi Jens,
Am Dienstag 23 August 2011, um 03:09:14 schrieb Jens Getreu:
> Hi Christian,
>
> thanks for the link towards the manual.
>
> I found my configuration mistake:
>
> It should be "INBOX/Kalender" instead of "Kalender"
> ...
That's right. Normally, all PIM folders will reside under INBOX, but technically,
this is not a strict requirement. You could have a (e.g. shared) PIM folder at
IMAP toplevel, so we cannot automatically prepend INBOX/ to the IMAP path. Hopefully,
in future, we will be able to provide autodetection of folders (in fact, the backend
already does, but in Evolution 2.30, we cannot make sensible use of this capability for
the plugin configuration).
> First I copied my 400 adresses to a kolab folder.
> evolution-kolab crashed 2 times. I have the impression the crashes have
> to do with duplicate detection.
>
> The todo plugin crashes predicable:
> 1. create a todo entry in horde.
> 2. select this entry in evolution.
> (see screen shot and error log).
It is hard to tell from the Evolution logs whether the plugin really crashed or just
timed out. I would assume that, instead of a crash, the Evolution Data Server (EDS)
took too much time because of the 400 address entries. All but the configuration and Email
of evolution-kolab is handled in the EDS. Evolution connects to EDS and asks for data.
If the request times out, Evolution assumes that the EDS process must have died. In order
to see what is actually happening, we will need to capture the EDS output. The procedure
for that is described in [1]. It's in German, so if you're a German speaker, you might
find that wiki page helpful. There's no english version of that page as yet.
Is it possible for you to export the TODO in question from Horde and send it to this list?
We could then check whether evolution-kolab chokes on that data (-->bug) or whether you're
suffering from EDS timeouts.
We are currently working on improving the overall speed of evolution-kolab, especially
when it comes to scanning the contents of PIM mail folders. The next release will do
better in this area, but evolution-kolab still has a long march ahead of it. In the meantime,
you might want to try with less entries (say, 100), to check whether the plugin generally
works for you. Speedup is on it's way.
Best regards,
Christian
[1] https://sourceforge.net/apps/trac/evolution-kolab/wiki/HowtoFehlersucheUndProblembehebung
PS.: You might want to consider setting the 'LANG=C' environment variable when taking
screenshots or logging debug output (the latter should be in english anyways) so
the messages will be in English. Will increase the usefulness for non-natives.
PPS.: @Jens: Sorry if you receive this as a double-post. My MUA tricked me. Again. :-/
--
kernel concepts GbR Tel: +49-271-771091-14
Sieghuetter Hauptweg 48
D-57072 Siegen
http://www.kernelconcepts.de/
Attachment:
signature.asc
Description: This is a digitally signed message part.