On Tue, 2012-02-14 at 11:44 +0100, Milan Crha wrote:
> On Tue, 2012-02-14 at 11:20 +0100, Patrick Ohly wrote:
> > Sorry, typo in my email. I meant "the problem can be avoided by always
> > passing only_if_exist=false". In other words, never use
> > only_if_exists=true because it serves no useful pu
On Tue, 2012-02-14 at 11:20 +0100, Patrick Ohly wrote:
> Sorry, typo in my email. I meant "the problem can be avoided by always
> passing only_if_exist=false". In other words, never use
> only_if_exists=true because it serves no useful purpose. Is that correct
> or is there some legitimate usage fo
On Tue, 2012-02-14 at 08:45 +0100, Milan Crha wrote:
> On Mon, 2012-02-13 at 21:52 +0100, Patrick Ohly wrote:
> > * A second invocation of SyncEvolution finds the definition of the
> > system address book via e_book_get_addressbooks() and tries to
> > open it with e_book_open(only_if_exis
On Mon, 2012-02-13 at 21:52 +0100, Patrick Ohly wrote:
> * A second invocation of SyncEvolution finds the definition of the
> system address book via e_book_get_addressbooks() and tries to
> open it with e_book_open(only_if_exists=false), which then fails
> with various errors, depend
Hello!
With EDS 3.2 and 3.3 I've seen the following problem on a clean account
(no databases, no gconf keys):
* An invocation of SyncEvolution to list databases calls
e_book_new_system_addressbook(), which creates a
gconf /apps/evolution/addressbook/sources entry for the syst
