[evolution-kolab-devel] Tasks: another try



Hello Christian,

On Tue, 2011-08-23 at 10:51 +0200, Christian Hilberg wrote: 
> 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.

Yes I am. Thanks for the hint.

> 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.

A todo list is a very personal thing. Can you treat it confidentially?

> 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.

Speed is definitely an issue. As workaround I edit first offline and
then switch to online-mode in order to synchronize data. Have you 
confederated a data cache? 

Here some more input:

First I imported my task-list via horde3.
Then I defined a remote task list in evolution.

The task-module exits with an error message.
You will find a screen-shot of the pop-up attached
and a log-file.

I comes every time I start evolution and then switch to
the taks view.


Best regards 




Jens




getreu@leon3:~/Bureau$ LANG=C evolution

** (evolution:31307): CRITICAL **: categories_icon_theme_hack: assertion `filename != NULL && *filename != '\0'' failed
(evolution:31307): camel-kolab-DEBUG: camel_kolab_imapx_provider_module_init: done
(evolution:31307): camel-kolab-DEBUG: camel_provider_module_init: kolab2 provider registered
(evolution:31307): camel-kolab-DEBUG: camel_kolab_imapx_store_init: done
(evolution:31307): camel-kolab-DEBUG: kolab_imapx_construct: metadata db initialized
** (evolution:31307): DEBUG: e_plugin_lib_enable(): Kolab plugin enabled
e_cal_view_start: Message did not receive a reply (timeout by message bus)

(evolution:31307): libecal-WARNING **: e-cal-view.c:425: Unable to start view

(evolution:31307): libecal-WARNING **: e_cal_dispose: Failed to close calendar, The name :1.832 was not provided by any .service files


(evolution:31307): libecal-WARNING **: e-cal.c:404: e-d-s proxy died
getreu@leon3:~/Bureau$ 
getreu@leon3:~/Bureau$ 
getreu@leon3:~/Bureau$ 
getreu@leon3:~/Bureau$ LANG=C evolution

** (evolution:31605): CRITICAL **: categories_icon_theme_hack: assertion `filename != NULL && *filename != '\0'' failed
(evolution:31605): camel-kolab-DEBUG: camel_kolab_imapx_provider_module_init: done
(evolution:31605): camel-kolab-DEBUG: camel_provider_module_init: kolab2 provider registered
(evolution:31605): camel-kolab-DEBUG: camel_kolab_imapx_store_init: done
(evolution:31605): camel-kolab-DEBUG: kolab_imapx_construct: metadata db initialized
** (evolution:31605): DEBUG: e_plugin_lib_enable(): Kolab plugin enabled
e_cal_view_start: Message did not receive a reply (timeout by message bus)

(evolution:31605): libecal-WARNING **: e-cal-view.c:425: Unable to start view

(evolution:31605): calendar-gui-WARNING **: e-cal-model.c:2125: Unable to get query, The name :1.838 was not provided by any .service files

(evolution:31605): libecal-WARNING **: e-cal.c:404: e-d-s proxy died

(evolution:31605): libecal-CRITICAL **: file e-cal.c: line 1399: assertion `priv->proxy' failed

(evolution:31605): calendar-modules-WARNING **: file e-cal.c: line 1399: assertion `priv->proxy' failed
** (evolution:31605): DEBUG: set_ui_from_source()[186] called.

(evolution:31605): libecal-WARNING **: e-cal.c:404: e-d-s proxy died

(evolution:31605): libecal-WARNING **: e-cal.c:404: e-d-s proxy died
getreu@leon3:~/Bureau$ LANG=C evolution

Attachment: pngQqniysetl3.png
Description: PNG image



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]