-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 16/02/12 21:56, Patrick Ohly wrote: > On Thu, 2012-02-16 at 20:52 +1300, Jane Atkinson wrote: >> On 16/02/12 20:20, Patrick Ohly wrote: >>> On Thu, 2012-02-16 at 09:07 +1300, Jane Atkinson wrote: >>>> I'm running the current Ubuntu development release (12.04) >>>> for testing purposes. I have the syncevolution repository in >>>> my sources.list. >>>> >>>> I've noticed that I need to run syncevolution twice whenever >>>> I sync. The first time, no error messages show up, but the >>>> changes don't migrate to the phone. The second time, the >>>> changes appear on the phone as expected. >>> >>> What changes are these? In Evolution? Contacts or calendar? >>> Are you perhaps synchronizing a CalDAV calendar in Evolution >>> with the phone? >>> >>> There was a problem like that with CalDAV calendar where >>> Evolution Data Server did not refresh its copy of the data the >>> first time that SyncEvolution asked for the calendar. >>> >> Yes, the calendar is a Radicale CalDAV calendar, synced via >> Evolution (over bluetooth). It's been a while since I synced any >> contacts, so I haven't noticed anything there. If necessary, I >> can test those as well. >> >> The issue only shows on Ubuntu 12.04. 10.04 behaves as expected. >> >> I can run some tests tomorrow. It's a little late here for me to >> do this tonight. > > The easiest test would be a "syncevolution --print-items <config > name> calendar": if that fails to show a recently added item, then > EDS is not updating itself quickly enough.
I added a couple of dummy items to the calendar, and they don't show the first time the command is run. It has to be run a second time for the new items to show. > > The workaround that I have in SyncEvolution (open+close+open) > really is just a hack. A proper solution has to be in EDS, > something like "open and refresh now, even if it takes a while". I could file a bug against EDS, though I suspect I'll be told that it's an upstream problem (and probably not likely to be fixed in time for release, unfortunately). > Do you absolutely need the data in Evolution? It's not currently > working yet, but it would be feasible to let SyncEvolution > synchronize a phone with a CalDAV server directly. > Good question. There are two things that have held me back here. One is figuring out the config necessary (laziness on my part?). The other is that I've been using bluetooth, and it sounds as though direct CalDAV sync involves setting up other servers as well. As a separate issue, Thunderbird / Lightning doesn't have a method of dealing with memos, which Evolution does. If anyone knows of another lightweight (i.e. not a full PIM) way of reading and editing memos, I'd be interested to hear about it. Thanks Jane Atkinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPPUm/AAoJEERzSJEx033jayUH/1mFEVBs+GdjgAYlfPByc6Om 0iNHQ/oFR/KGlQkiX6vNeSZj2CR7Qa1jxmrkjDBb4MRokqDrqs0Lv5ByzLKQuwjT Wt8dN6IwjFbDMIn4BxZ2KfN+t4E8UXlh6VxfDJIMmFGPOyHkd8jQSJt42Y7xnlkb nFFrvwzbJ61ijPt/2vz9iBC+MOY3OxEf8G2Mn7YQuxTiV61H6qf5qbpUsmY5jUgh jjvT0R2ynohWtZe3yqqKRaKVnVOTOIBS1qWsQWM3i+/6kWpI3tm3Nutioqj/VBZy W2sGroqYudhhwyZbrDyXH/kZm17BxZBVTI6CAgRu+P9Q3JcUizqCJY7oOXgmP20= =js+U -----END PGP SIGNATURE----- _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
