You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(28) |
Sep
(3) |
Oct
|
Nov
(1) |
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Christian H. <hi...@ke...> - 2012-05-04 12:36:07
|
Hi everyone! This mailing list has been closed for new postings. Development for evolution-kolab takes place directly at GNOME.org since 2011-11-11. The GNOME wiki contains the new primary website [0]. The primary Git repository [1], bugtracker [2] and the mailing list [3] have also moved there. Source releases are now hosted at GNOME.org as well [4]. For development tasks (code, bug reports and mailing list), please refer to this new site exclusively. The infrastructure at SourceForge will be kept in place for documentation and supplemental files for evolution-kolab targeting Evolution 2.30 and for Maemo 5 devices (Nokia N900) accessing Kolab servers. evolution-kolab versions for Evolution 3.x and above are hosted solely at GNOME.org, and releases will be made there only. Subscribers to this mailing list should have received a subscription invitation for the new list quite a while ago. It is safe now for subscribers to unsubscribe from the evo...@li..., since there will be no further postings. We invite everyone interested in evolution-kolab to join us at GNOME.org! Kind regards, Christian [0] http://live.gnome.org/Evolution/Kolab [1] http://git.gnome.org/browse/evolution-kolab [2] http://bugzilla.gnome.org/browse.cgi?product=evolution-kolab [3] http://mail.gnome.org/archives/evolution-kolab-devel-list/ [4] http://ftp.gnome.org/pub/GNOME/sources/evolution-kolab/ -- kernel concepts GmbH Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ |
From: Christian H. <hi...@ke...> - 2012-05-04 10:30:55
|
Hi everyone. The evolution-kolab team gladly announces the availability of version 0.30.1 of the evolution-kolab plugin for the Evolution PIM suite. This version is the first and final bugfix release for the 0.30.x series of evolution-kolab. The major improvements over our previous release (Version 0.30.0) are internal ones mostly and include: * further speedup fixes to bulk synchronization operations * documentation fixes * rework of the autotools build system * much code cleanup for ANSI C (C99) conformance No new functionality has been added in this bugfix release. Please note that evolution-kolab has moved to GNOME.org (please see [0]) since quite a while now and active development takes place there for the GNOME 3.4 series and above. With the release of version 0.30.1, development for the GNOME 2.30 series has officially ended and only GNOME 3.4 and above will be actively maintained. Thank you very much for your interest in evolution-kolab! Kind regards, Christian Hilberg [0] https://live.gnome.org/Evolution/Kolab -- kernel concepts GmbH Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ |
From: Christian H. <hi...@ke...> - 2011-09-02 13:53:21
|
Hi Christoph, Am Mittwoch 17 August 2011, um 11:35:49 schrieb Christian Hilberg: > [...] > Debugging is possible by starting EDS (it consists of two factory processes, > one for contacts, one for calendar) in a terminal with some environment > variables set and checking the output. I'm about to create a wiki page for > that (will be cut-and-paste from developer emails mostly, in German, > translators welcome). I'll let you know once it is done. Sorry, my MUA tricked me and the following information did not go to the list (though I've posted the link as a follow-up to other mails already): The new wiki page is now accessible via [1]. No english translation is available as yet. HTH, Christian [1] https://sourceforge.net/apps/trac/evolution-kolab/wiki/HowtoFehlersucheUndProblembehebung -- kernel concepts GbR Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ |
From: Christian H. <hi...@ke...> - 2011-09-01 13:30:17
|
Hi Jens, Am Donnerstag 01 September 2011, um 15:01:25 schrieb Jens Getreu: > Hello Christian, > > (I answer you in English to leave a trace for other guys using > evolution-kolab). :-) > I compiled you sources, everything went well without problems. > > You will find the result as (unofficial) Debian packages here: > > http://getreu.net/public/downloads/software/evolution-kolab/evolution-kolab > -20110831-branch-dev_kc_speed/ > > evolution-kolab-dev_0.2.1_amd64.deb > evolution-kolab_0.2.1_amd64.deb Okay, since not everyone will be able to follow my PS. in German, here's for the rest of them: I've sent an unofficial distribution tarball to Jens, who was kind enough to compile it into a package for Debian/Squeeze. This tarball was generated from the dev_kc_speed git branch and contains some speedup fixes (still much work left to be done in that area) as well as a fix for a Horde data parsing issue. Since I cannot currently increment the patchlevel, the tarball contains the 0.2.1 version information, but differs from the already-released one with the same version. It will be a while (presumably end of September) before I can release the next official version. Maybe I will do a tarball-only release (no packaging) before that. > I also had a first try. The todo list issue seems to be solved for me > too and indeed things are a little faster. As my internet link is > _very_ slow from here, it is better to use evolution in offline-mode > and then switch back to online-mode for synchronisation. > Especially browsing the calendar is much too slow. To make up a little for evolution-kolab's intrinsic sluggishness(*), at least your network connection to your Kolab server should be quick. :-) But yes, using offline mode should be a suitable workaround for now. > The whole seems to be quite stable. I will migrate my data on > the kolab server and work with it! Please be sure to make proper backups! While Kolab itself is much robust and stable, evolution-kolab is still very young. Though we did not encounter a case of data corruption or evolution-kolab otherwise eating our PIM information yet, proper precaution should be taken when using evolution-kolab. > Thanks a lot for your help! Welcome. > Kind regards > Jens (Bye)^2, Christian (*) We're working on that > Le jeudi 01 septembre 2011 à 09:57 +0200, Christian Hilberg a écrit : > > Hallo Jens, > > > > Am Mittwoch 31 August 2011, um 23:18:58 schrieb Jens Getreu: > > > Hallo Christian, > > > > > > ja bitte... > > > > Okay, hier kommt die Kiste. > > > > > 1 MB shouldn't be too much. > > > > Gut. > > > > > Thanks in advance. > > > > > > Tervitades > > > > > > Jens > > > > Viele Grüße, > > > > Christian > > > > PS.: Der Tarball trägt zwar noch die Versionsnummer 0.2.1, unterscheidet > > sich aber von dem veröffentlichten. Der Bugfix ist drin, und auch > > schon einige Geschwindigkeitsverbesserungen. Allerdings kann ich > > momentan die Versionsnummer noch nicht hochsetzen, das kommt erst > > kurz vor dem tatsächlichen Release der nächsten Version. Du hast > > jetzt einen Git-Abzug vom Branch dev_kc_speed vom 31.08.2011 > > (commit 39a87c4193bda87a7f284394870d16307cb35759) bzw. einen daraus > > erstellten Distribution-Tarball. -- kernel concepts GbR Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ |
From: Jens G. <jen...@gm...> - 2011-09-01 13:03:11
|
Hello Christian, (I answer you in English to leave a trace for other guys using evolution-kolab). I compiled you sources, everything went well without problems. You will find the result as (unofficial) Debian packages here: http://getreu.net/public/downloads/software/evolution-kolab/evolution-kolab-20110831-branch-dev_kc_speed/ evolution-kolab-dev_0.2.1_amd64.deb evolution-kolab_0.2.1_amd64.deb I also had a first try. The todo list issue seems to be solved for me too and indeed things are a little faster. As my internet link is _very_ slow from here, it is better to use evolution in offline-mode and then switch back to online-mode for synchronisation. Especially browsing the calendar is much too slow. The whole seems to be quite stable. I will migrate my data on the kolab server and work with it! Thanks a lot for your help! Kind regards Jens Le jeudi 01 septembre 2011 à 09:57 +0200, Christian Hilberg a écrit : > Hallo Jens, > > Am Mittwoch 31 August 2011, um 23:18:58 schrieb Jens Getreu: > > Hallo Christian, > > > > ja bitte... > > Okay, hier kommt die Kiste. > > > 1 MB shouldn't be too much. > > Gut. > > > Thanks in advance. > > > > Tervitades > > > > Jens > > Viele Grüße, > > Christian > > PS.: Der Tarball trägt zwar noch die Versionsnummer 0.2.1, unterscheidet > sich aber von dem veröffentlichten. Der Bugfix ist drin, und auch > schon einige Geschwindigkeitsverbesserungen. Allerdings kann ich > momentan die Versionsnummer noch nicht hochsetzen, das kommt erst > kurz vor dem tatsächlichen Release der nächsten Version. Du hast > jetzt einen Git-Abzug vom Branch dev_kc_speed vom 31.08.2011 > (commit 39a87c4193bda87a7f284394870d16307cb35759) bzw. einen daraus > erstellten Distribution-Tarball. > |
From: Jens G. <jen...@gm...> - 2011-08-31 15:34:20
|
#LANG=C ./debian/rules binary .... make[2]: Entering directory `/home/getreu/Bureau/tmp/evolution-kolab/po' INTLTOOL_EXTRACT=/usr/bin/intltool-extract srcdir=. /usr/bin/intltool-update --gettext-package evolution_kolab --pot rm -f missing notexist srcdir=. /usr/bin/intltool-update -m mismatched quotes at line 155 in ../src/libekolab/kolab-mail-info-db.c mismatched quotes at line 157 in ../src/libekolab/kolab-mail-info-db.c mismatched quotes at line 169 in ../src/libekolab/kolab-mail-info-db.c mismatched quotes at line 177 in ../src/libekolab/kolab-mail-info-db.c mismatched quotes at line 313 in ../src/libekolab/kolab-mail-info-db.c mismatched quotes at line 320 in ../src/libekolab/kolab-mail-info-db.c mismatched quotes at line 113 in ../src/libekolab/kolab-mail-side-cache.c mismatched quotes at line 115 in ../src/libekolab/kolab-mail-side-cache.c The following files contain translations and are currently not in use. Please consider adding these to the POTFILES.in file, located in the po/ directory. src/camel/camel-kolab-provider.c If some of these files are left out on purpose then please add them to POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list of left out files has been written in the current directory. Please report to if [ -r missing -o -r notexist ]; then \ exit 1; \ fi make[2]: *** [check] Error 1 make[2]: Leaving directory `/home/getreu/Bureau/tmp/evolution-kolab/po' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/getreu/Bureau/tmp/evolution-kolab' dh_auto_test: make -j1 check returned exit code 2 make: *** [binary] Error 29 root@...:/home/getreu/Bureau/tmp/evolution-kolab# Any idea? Head õhtut (schönen Abend) Jens Le mercredi 31 août 2011 à 17:15 +0200, Christian Hilberg a écrit : > > [...] > > For a quick fix, you could try building the sources as outlined in INSTALL- > > notes, but omitting the "make install" step. Instead, call debian/rules > > now, it should then be able to build the evolution-dev package. Be sure to > ^^^^^^^^^^^^^ > > This should read evolution-kolab-dev, of course. > > ------------------------------------------------------------------------------ > Special Offer -- Download ArcSight Logger for FREE! > Finally, a world-class log management solution at an even better > price-free! And you'll get a free "Love Thy Logs" t-shirt when you > download Logger. Secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsisghtdev2dev > _______________________________________________ Evolution-kolab-devel mailing list Evo...@li... https://lists.sourceforge.net/lists/listinfo/evolution-kolab-devel |
From: Christian H. <hi...@ke...> - 2011-08-31 15:16:06
|
> [...] > For a quick fix, you could try building the sources as outlined in INSTALL- > notes, but omitting the "make install" step. Instead, call debian/rules > now, it should then be able to build the evolution-dev package. Be sure to ^^^^^^^^^^^^^ This should read evolution-kolab-dev, of course. -- kernel concepts GbR Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ |
From: Christian H. <hi...@ke...> - 2011-08-31 14:59:45
|
Hi Jens, Am Mittwoch 31 August 2011, um 16:08:30 schrieb Jens Getreu: > Le mercredi 31 août 2011 à 10:50 +0200, Christian Hilberg a écrit : > > Hi Jens, > [...] > > Hendrik prepared a fix which solved the problem for me. The fix is now in > > git master. If you like, clone the git repo, checkout master branch and > [...] > > this was a fast bug-fix! Thanks to Hendrik. > Is this the right master checkout command? > #git clone > git://evolution-kolab.git.sourceforge.net/gitroot/evolution-kolab/evolution > -kolab Looks good. > I had a fast try, copied my debian folder into the tree and launched > #./debian/rules binary > but, it did not work. > > ########### > root@...:/home/getreu/Bureau/tmp/evolution-kolab# ./debian/rules binary > dh binary > dh_install > dh_install: evolution-kolab-dev missing files > (usr/share/gtk-doc/html/*), aborting > make: *** [binary] Erreur 2 > ########### > > I suppose my checkout is not correct or some files are missing. Welcome to the wonders of package generation. :-) Packaging is not a trivial task and it needs some infrastructure to get it right (if you like text adventures, try and find your way through the Debian packaging guides, they're quite extensive). Your checkout is okay, but, unlike the distribution tarball, the git checkout does not contain the HTML API doc files. These are generated when the distributrion tarball is built (from which, ideally, the package is created), and they are needed to build the evolution-kolab-dev package. For a quick fix, you could try building the sources as outlined in INSTALL- notes, but omitting the "make install" step. Instead, call debian/rules now, it should then be able to build the evolution-dev package. Be sure to initially pass to autogen.sh the same flags that would be set by debian/rules. (Bye)^2, Christian PS.: You could also just disable evolution-kolab-dev package generation by commenting out the relevant parts in debian/* -- kernel concepts GbR Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ |
From: Jens G. <jen...@gm...> - 2011-08-31 14:08:05
|
Le mercredi 31 août 2011 à 10:50 +0200, Christian Hilberg a écrit : > Hi Jens, > > Am Dienstag 30 August 2011, um 12:15:42 schrieb Jens Getreu: > > Christian, > > > > I thought, if it were only this special task then I just have > > to delete it and can use the kolab server, but unfortunately > > my other tasks provoke crashes too. I will have to wait for your > > bug-fix. > > Attached you will find another test-case you can forward to your > > colleague. > > > > Kind regards > > > > Jens > > > > Le mardi 30 août 2011 à 10:09 +0200, Christian Hilberg a écrit : > > > Hi Jens, > > > > > > first of all, thank you very much for your persistence. I think we > > > *finally* caught it. The Task you sent causes a segfault. > > > Congratulations! :-) Now we can send the bug squad. The segfault is > > > triggered within the Evolution<->Kolab data conversion library of > > > evolution-kolab. > > [...] > > Hendrik prepared a fix which solved the problem for me. The fix is now in git > master. If you like, clone the git repo, checkout master branch and build from > there. You should now be able to access your folders without the recent > crashes. Note, however, that though the backend does no longer crash on the > sample data you provided, there are still some extra bytes left in the Horde > data which do not display nicely (we will not try to 'correct' that in > evolution-kolab, but leave the data as-is). > It will be a while before the next release of evolution-kolab, so you might > want to give git master a try. > > Kind regards, > > Christian > Christian, this was a fast bug-fix! Is this the right master checkout command? #git clone git://evolution-kolab.git.sourceforge.net/gitroot/evolution-kolab/evolution-kolab I had a fast try, copied my debian folder into the tree and launched #./debian/rules binary but, it did not work. ########### root@...:/home/getreu/Bureau/tmp/evolution-kolab# ./debian/rules binary dh binary dh_install dh_install: evolution-kolab-dev missing files (usr/share/gtk-doc/html/*), aborting make: *** [binary] Erreur 2 ########### I suppose my checkout is not correct or some files are missing. Kind regards Jens |
From: Christian H. <hi...@ke...> - 2011-08-31 08:50:26
|
Hi Jens, Am Dienstag 30 August 2011, um 12:15:42 schrieb Jens Getreu: > Christian, > > I thought, if it were only this special task then I just have > to delete it and can use the kolab server, but unfortunately > my other tasks provoke crashes too. I will have to wait for your > bug-fix. > Attached you will find another test-case you can forward to your > colleague. > > Kind regards > > Jens > > Le mardi 30 août 2011 à 10:09 +0200, Christian Hilberg a écrit : > > Hi Jens, > > > > first of all, thank you very much for your persistence. I think we > > *finally* caught it. The Task you sent causes a segfault. > > Congratulations! :-) Now we can send the bug squad. The segfault is > > triggered within the Evolution<->Kolab data conversion library of > > evolution-kolab. > [...] Hendrik prepared a fix which solved the problem for me. The fix is now in git master. If you like, clone the git repo, checkout master branch and build from there. You should now be able to access your folders without the recent crashes. Note, however, that though the backend does no longer crash on the sample data you provided, there are still some extra bytes left in the Horde data which do not display nicely (we will not try to 'correct' that in evolution-kolab, but leave the data as-is). It will be a while before the next release of evolution-kolab, so you might want to give git master a try. Kind regards, Christian -- kernel concepts GbR Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ |
From: Christian H. <hi...@ke...> - 2011-08-29 08:11:19
|
Hi Jens, Am Sonntag 28 August 2011, um 20:29:29 schrieb Jens Getreu: > Hello, > > Le vendredi 26 août 2011 à 15:23 +0200, Christian Hilberg a écrit : > > Sorry, still no luck. You should monitor the EDS output to see what > > is actually happening when accessing the Kolab PIM folders. Without that, > > I'm afraid, there's no chance to find out why evolutoin-kolab chokes for > > you. > > How can I dump the EDS output? Please refer to [1] and [2], it explains how to manually start the EDS processes to capture their output. The output of an EDS factory process can easily be redirected to a file (make sure to redirect stderr as well as stdout). Under GNOME, special care may be needed to make sure there are no EDS factory processes left running before starting them (again) from a terminal. Kind regards, Christian [1] http://evolution-kolab.git.sourceforge.net/git/gitweb.cgi?p=evolution-kolab/evolution-kolab;a=blob;f=docs/manuals/INSTALL-notes [2] http://sourceforge.net/apps/trac/evolution-kolab/wiki/HowtoFehlersucheUndProblembehebung -- kernel concepts GbR Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ |
From: Christian H. <hi...@ke...> - 2011-08-26 13:24:10
|
Hi Jens, Am Freitag 26 August 2011, um 12:44:44 schrieb Jens Getreu: > Hello Christian, > > On Tue, 2011-08-23 at 10:51 +0200, Christian Hilberg wrote: > > 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. > > Attached you will find sample user data from my imap server folder. The > horde generated xml look quite different from the evolution ones. Maybe > the horde xml crashes the evolution-kolab plugin? Horde is known to generate Kolab XML which, under certain circumstances, can be pretty much off-spec (Kolab XML format specification, that is). However, with the Horde PIM mail at hand, I had no trouble. We have a bunch of testcases with Horde generated XML to test the data conversion part. So, I've copied the email as-is into a notes Kolab IMAP folder using a different IMAP client, expecting some sort of trouble triggered by this Horde XML file. But instead of any problems, I was able to read it with evolution-kolab just fine by down-syncing it from the server, no crashes, neither while syncing nor while displaying in Evolution. The Horde mail payload data (the kolab.xml part) is base64-encoded, hence the funny look. Maybe Horde does this by default. evolution-kolab does base64 encoding only if the payload data cannot be encoded in pure ascii. base64 is just fine, even if it was not strictly necessary to use this encoding. Sorry, still no luck. You should monitor the EDS output to see what is actually happening when accessing the Kolab PIM folders. Without that, I'm afraid, there's no chance to find out why evolutoin-kolab chokes for you. Kind regards, Christian -- kernel concepts GbR Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ |
From: Jens G. <jen...@gm...> - 2011-08-26 10:44:11
|
Hello Christian, On Tue, 2011-08-23 at 10:51 +0200, Christian Hilberg wrote: > 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. Attached you will find sample user data from my imap server folder. The horde generated xml look quite different from the evolution ones. Maybe the horde xml crashes the evolution-kolab plugin? Best regards Jens |
From: Jens G. <jen...@gm...> - 2011-08-24 08:42:02
|
On Wed, 2011-08-24 at 10:08 +0200, Christian Hilberg wrote: > Did you try switching off that accessibility stuff? Did that change anything? Actually I did, the effect was apparently not immediate because I did not see any change. Today I think it had an effect, because after reinstalling my evolution-kollab package the error messages did not come back! So one part of the problem is (hopefully) solved (see logfile). > And which GNOME/GTK-Theme are you using? Mint-X. I changed to the default theme clearlooks: no change. > Maybe I can reproduce the issue. http://getreu.net/public/downloads/software/evolution-kolab/evolution-kolab-0.2.1/evolution-kolab-0.2.1-bin/evolution-kolab-dev_0.2.1_amd64.deb Freundliche Grüße Jens |
From: Jens G. <jen...@gm...> - 2011-08-24 07:04:31
|
Guten Morgen Christian, On Tue, 2011-08-23 at 15:53 +0200, Christian Hilberg wrote: > The log file shows serious trouble with your Evolution frontend > ("Gtk-CRITICAL **", "calendar-gui-CRITICAL **", ...). These errors > are almost certainly not triggered by evolution-kolab, since this > plugin lives inside EDS, not Evolution (this is why it makes no sense > to capture Evolution output when trying to troubleshoot evolution-kolab). I uninstalled evolution-kolab and the messages disappeared (see log). This means the errors _are_ triggered by evolution-kolab. Probably my build is not right. I mainly changed only paths. Except the following line which could be critical (see patchfile): dh_auto_configure -- --disable-largefile --enable-maintainer-mode 'CFLAGS=-g -O0 -fPIC' Is this ok? Freundliche Grüße Jens |
From: Christian H. <hi...@ke...> - 2011-08-23 13:53:30
|
Hi Jens, Am Dienstag 23 August 2011, um 15:28:57 schrieb Jens Getreu: > Hello Christian, > > I do not think the problem is related to the data itself: Seems so. > First I created a new task-list with one task in horde3. > Then I defined a remote task list in evolution. > > The task-module exits with an error message when > I click the completed check-box. > You will find a screen-shot of the pop-up attached > and a log-file. The log file shows serious trouble with your Evolution frontend ("Gtk-CRITICAL **", "calendar-gui-CRITICAL **", ...). These errors are almost certainly not triggered by evolution-kolab, since this plugin lives inside EDS, not Evolution (this is why it makes no sense to capture Evolution output when trying to troubleshoot evolution-kolab). Seems your Evolution/GTK/...-Installation is pretty much hosed. The whole frontend is in an undefined state after these critical warnings. Evolution is not supposed to show any of them. > I give up... Try disabling the "assistive technologies" as per [1]: ---- FYI for future people. To disable accessibility, got to System->Preferences->Assistive Technologies Uncheck the "enable assistive technologies" box. ---- HTH, Christian [1] https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/270271 -- kernel concepts GbR Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ |
From: Jens G. <jen...@gm...> - 2011-08-23 13:28:33
|
Hello Christian, I do not think the problem is related to the data itself: First I created a new task-list with one task in horde3. Then I defined a remote task list in evolution. The task-module exits with an error message when I click the completed check-box. You will find a screen-shot of the pop-up attached and a log-file. I give up... Best regards Jens |
From: Jens G. <jen...@gm...> - 2011-08-23 12:15:28
|
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 |
From: Jens G. <jen...@gm...> - 2011-08-23 10:57:03
|
Hello Christian, thanks for your answer. I come back to it later. Here another issue (that I do not forget): *** evolution deletes cyrus.cache cyrus.header cyrus.index files on server *** How it happens: 1. Go into evolutions Junk-folder of the kolab account 2. select all (ctrl-A) 3. delete It first deleted parts of the messages, then stopped. Then no other action in mailboxes were possible. Steps to repair the mailbox 1. login as root at kolab server 2. #sudo -u cyrus cyrreconstruct -r -v user/ma...@ko... (the tags are lost). Best regards Jens |
From: Christian H. <hi...@ke...> - 2011-08-23 08:51:43
|
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/ |
From: Jens G. <jen...@gm...> - 2011-08-23 01:08:50
|
Hi Christian, thanks for the link towards the manual. I found my configuration mistake: It should be "INBOX/Kalender" instead of "Kalender" ... 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). Best regards Jens Le lundi 22 août 2011 à 20:05 +0200, Christian Hilberg a écrit : > Hi Jens, > > Am Montag 22 August 2011, um 15:30:31 schrieb Jens Getreu: > > Hello Christian, > > > > is finally managed to install the native Debian version of kolab > > (kolabd verison 2.2.4-20100624-4). > > Kolab 2(.2.4) is the best choice for testing evolution-kolab, so you should be > good to go here. > > > Then I started evolution from a new accout (evolution 2.30.3-5) > > with evolution-kolab 0.2.1. As you can see in the attached logfile > > there are still a lot of error messages... > > > > In evolution I can see my kolab account, but not the folders Kalender, > > Aufgaben... I tested to create a folder named "Kalender" which > > evolution refused saying that the folder exists. > > You will not "see" the Kolab PIM folders in the Evolution frontend, only the > Email folders will be shown. > > > Knowing this I created a remote kolab calenar "Kalender" and restarted > > evolution. The calendar shows up, but it is empty. I can not create any > > objects. Same for tasks and contacts. > > You will need to set up the PIM folders (events, notes tasks, contacts) for > accessing them through Evolution. This is done via the "New" entry in the > respective Evolution view (select "kolab2" as the type for the new address > book / calendar / task list / memo list). > > Are you sure you carefully read and followed the configuration procedure as > outlined in the evolution-kolab user manual (you can get it from the project's > "Files" section at SourceForge)? > > Kind regards, > > Christian > > ------------------------------------------------------------------------------ > uberSVN's rich system and user administration capabilities and model > configuration take the hassle out of deploying and managing Subversion and > the tools developers use with it. Learn more about uberSVN and get a free > download at: http://p.sf.net/sfu/wandisco-dev2dev > _______________________________________________ > Evolution-kolab-devel mailing list > Evo...@li... > https://lists.sourceforge.net/lists/listinfo/evolution-kolab-devel |
From: Christian H. <hi...@ke...> - 2011-08-22 18:05:18
|
Hi Jens, Am Montag 22 August 2011, um 15:30:31 schrieb Jens Getreu: > Hello Christian, > > is finally managed to install the native Debian version of kolab > (kolabd verison 2.2.4-20100624-4). Kolab 2(.2.4) is the best choice for testing evolution-kolab, so you should be good to go here. > Then I started evolution from a new accout (evolution 2.30.3-5) > with evolution-kolab 0.2.1. As you can see in the attached logfile > there are still a lot of error messages... > > In evolution I can see my kolab account, but not the folders Kalender, > Aufgaben... I tested to create a folder named "Kalender" which > evolution refused saying that the folder exists. You will not "see" the Kolab PIM folders in the Evolution frontend, only the Email folders will be shown. > Knowing this I created a remote kolab calenar "Kalender" and restarted > evolution. The calendar shows up, but it is empty. I can not create any > objects. Same for tasks and contacts. You will need to set up the PIM folders (events, notes tasks, contacts) for accessing them through Evolution. This is done via the "New" entry in the respective Evolution view (select "kolab2" as the type for the new address book / calendar / task list / memo list). Are you sure you carefully read and followed the configuration procedure as outlined in the evolution-kolab user manual (you can get it from the project's "Files" section at SourceForge)? Kind regards, Christian -- kernel concepts GbR Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ |
From: Jens G. <jen...@gm...> - 2011-08-22 13:30:08
|
Hello Christian, is finally managed to install the native Debian version of kolab (kolabd verison 2.2.4-20100624-4). Then I started evolution from a new accout (evolution 2.30.3-5) with evolution-kolab 0.2.1. As you can see in the attached logfile there are still a lot of error messages... In evolution I can see my kolab account, but not the folders Kalender, Aufgaben... I tested to create a folder named "Kalender" which evolution refused saying that the folder exists. Knowing this I created a remote kolab calenar "Kalender" and restarted evolution. The calendar shows up, but it is empty. I can not create any objects. Same for tasks and contacts. Can you help? Best regards Jens |
From: Christian H. <hi...@ke...> - 2011-08-19 09:57:21
|
Hi Jens, Am Donnerstag 18 August 2011, um 13:06:26 schrieb jens: > [...] > I have to suspend my activity on this now, but I am still interested in > your project. Debian squeeze binaries/repository would be nice! > [...] For future postings to this list, please subscribe with the email address your're actually using for sending your emails to the list. Since this is a subscribers-only list, all emails sent from non-subscribed email addresses will be held for moderator approval, which then need to be tended to. Kind regards, Christian -- kernel concepts GbR Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ |
From: Christoph W. <wi...@ko...> - 2011-08-18 19:16:37
|
On Wednesday 17 August 2011 11:35:49 Christian Hilberg wrote: > We ourselves did not yet test evolution-kolab against Kolab 2.3.2, but our > sponsor did, and there seemed to be no issues related to 2.2.4 vs. 2.3.2 so > far. The testing against 2.3.2, however, was not much intense, so there > might be issues which we are not yet aware of. As the server maintainer I am pretty sure that nothing has changed for the client. > The need to set up every folder individually is due to limitations in the > 2.30 Evolution implementation. We could have hacked around these issues, > but we do not have the resources to do so. We can in no way compete with > Kontact's user experience when using Kolab so far, Kontact has some > developer years more on it's account than we have. :) Don't worry, it's not that evolution-kolab looked particularily bad. kdepim 4.7.0 didn't work either despite of all the manpower they had put into the Akonadi migration. ;) (Any yes, before you ask: The server was fine) > Debugging is possible by starting EDS (it consists of two factory > processes, one for contacts, one for calendar) in a terminal with some > environment variables set and checking the output. I'm about to create a > wiki page for that (will be cut-and-paste from developer emails mostly, in > German, translators welcome). I'll let you know once it is done. Thanks, looking forward to it. Regards, Christoph -- Christoph Wickert Senior Engineer Kolab Systems AG Zürich, Switzerland e: wi...@ko... t: +49 251 871 369 77 w: http://kolabsys.com pgp: 85DACC63 Christoph Wickert |