On Tue, Oct 7, 2014 at 12:08 PM, Patrick Ohly <[email protected]> wrote: >> Sorry, I was just looking in google/ and didn't think to look in default/: >> >> $ cd ~/.config/syncevolution >> $ find . -name config.ini -print | xargs grep goa >> ./default/peers/google/config.ini:username = goa:account_... >> ./google/peers/target-config/config.ini:username = goa:account_... > > Do you have an idea how it got there? I don't think previous > SyncEvolution versions worked with such a config.
I'm not sure, but my guess is that it was the direct result of an earlier, misguided attempt to correct a problem with my configuration, maybe even by directly editing a configuration file. >> > Anyway, removing it in the "google" config should allow you to run syncs >> > again: syncevolution --configure username= google >> >> Yes, authentication is successful now, but I'm still having some >> problems with the sync. Perhaps we'll have to go into details off-list >> about the contents of the events, > > That would be good. A target-config@google log file at loglevel=4 would > be useful. Coming soon by private email. --Todd _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
