On Thu, 2012-11-22 at 11:12 +0100, [email protected] wrote: > On Thu, Nov 22, 2012 at 11:00:56 +0100, [email protected] > wrote: > > Hi, > > > > I tried the following: > > > > syncevolution --configure autoSyncInterval=30 eazy > > > > This command does not return. According to strace, it seems to wait > > forever in poll(). > > > > Adding --daemon=no to the options does not hang. > > > > Subsequent sync runs will also hang. > > > > This happens with 1.3.1 with commit > > d4b85f9c621267974a9e741b2db142fb98db3ecf cherry-picked. > > It also happens with 1.2.99.1 from Debian Sid. I noticed that the > syncevo-dbus-helper process needs to be killed with SIGKILL after this, > SIGTERM won't suffice.
I can't reproduce that here, using 1.3.1. Is there perhaps a sync running while you invoke the command line? Executing the command line will have to wait until syncing is complete. To collect more information, please kill syncevo-dbus-server and run it manually as SYNCEVOLUTION_DEBUG=1 /usr/libexec/syncevo-dbus-server Then in another shell try to set autoSyncInterval. That should show what the server is waiting for. Then when the helper gets stuck, what is the full stack backtrace? Just poll inside g_main_loop_run()? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
