Hello, I've noticed that scheduled sync doesn't work anymore even if the "Automatic sync" is checked. As well the "Sync now" button is always grayed out, though if I run syncevolution from command line, everything works as expected. I suppose it's something to do with dbus interaction. I'd appreciate any ideas. I'm using the latest version 1.2.99.2.

Patrick, You're right, I don't use any of the network managers you mentioned and my distro is Gentoo. Hopefully the next version will fix this issue. Regards, Vlad. P.S. Thanks for the quick replay. On Mon, 2012-07-16 at 07:43 +0200, Patrick Ohly wrote: > On Mon, 2012-07-16 at 06:25 +0200, Vladimir Elisseev wrote: > > Hello, > > > > I've noticed that scheduled sync doesn't work anymore even if the > > "Automatic sync" is checked. As well the "Sync now" button is always > > grayed out, though if I run syncevolution from command line, everything > > works as expected. I suppose it's something to do with dbus interaction. > > I'd appreciate any ideas. > > I'm using the latest version 1.2.99.2. > > What is your Linux distro and setup, in particular regarding network > connectivity? Do you by any chance run a system without NetworkManager > and ConnMan? > > I recently found a bug which triggers in combination with a recent > libdbus, where syncevo-dbus-server no longer detects that both are > missing. In that case it incorrectly assumes to be offline (which > prevents syncing). > > Fix will be in 1.2.99.3. > _______________________________________________ SyncEvolution mailing list SyncEvolution(a)syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution

On Mo, 2012-07-30 at 14:18 +0200, Elisseev V. wrote: > First of all, thanks for the updated version 1.2.99.3! This version > fixed one problem with always disabled "Sync now" button, but it looks > like "Automatic sync" still doesn't work. Please kill the running syncevo-dbus-server and restart it with logging enabled: $ killall syncevo-dbus-server $ SYNCEVOLUTION_DEBUG=1 /usr/libexec/syncevo-dbus-server 2>&1 | tee /tmp/syncevo.log Please send the output. There should be statements about "auto sync" which explain for which config it is enabled and why the sync is not starting.

On Di, 2012-07-31 at 10:18 +0200, Vladimir Elisseev wrote: > Patrick, > > See debug log: http://pastebin.com/PmUaCrwx > Personally, based on the debug info, I can't understand what's going on. The relevant part is here: [DEBUG syncevo-dbus-server 00:30:00] auto sync: reschedule, funambol interval timer [DEBUG syncevo-dbus-server 00:30:00] auto sync: funambol: https://xxx.xxx.xxx:8443/funambol/ds uses HTTP [DEBUG syncevo-dbus-server 00:30:00] auto sync: funambol: presence delay of transport for https://xxx.xxx.xxx:8443/funambol/ds expires in -1500s Somehow the check for "have we been online long enough" fails. Probably another side effect of not really having a running network manager of any kind - I'll check.

On Thu, Aug 02, 2012 at 11:39:56 +0200, Patrick Ohly wrote: > On Di, 2012-07-31 at 10:35 +0200, Patrick Ohly wrote: > > On Di, 2012-07-31 at 10:18 +0200, Vladimir Elisseev wrote: > > > Patrick, > > > > > > See debug log: http://pastebin.com/PmUaCrwx > > > Personally, based on the debug info, I can't understand what's going on. > > > > The relevant part is here: > > > > [DEBUG syncevo-dbus-server 00:30:00] auto sync: reschedule, funambol interval timer > > [DEBUG syncevo-dbus-server 00:30:00] auto sync: funambol: https://xxx.xxx.xxx:8443/funambol/ds uses HTTP > > [DEBUG syncevo-dbus-server 00:30:00] auto sync: funambol: presence delay of transport for https://xxx.xxx.xxx:8443/funambol/ds expires in -1500s > > > > Somehow the check for "have we been online long enough" fails. Probably > > another side effect of not really having a running network manager of > > any kind - I'll check. > > Actually, autoSyncDelay > 0 (the default) was broken in general. Thanks > a lot for trying this out! It'll be fixed in the next release. Hi, I got the same when trying out sync-ui from 1.2.99.2. I'll check if this is fixed in git and report back.