Well, maybe my comment about the many segfault related threads were a bit exaggerated. They just jumped into my eye when I googled all these different messages and warnings I got ;-)
syncevo-dbus-server was not running before I started sync-ui. But when I started sync-ui again (with the old syncevo-dbus-server from the first try was still running), it didn't complain either.
The output of dbus-monitor is attached. I see that it claims the name org.syncevolution.Server and calls the GetConfig method, but the reply of the daemon is close to nothing.
Well, maybe my comment about the many segfault related threads were a bit exaggerated. They just jumped into my eye when I googled all these different messages and warnings I got ;-)
syncevo-dbus-server was not running before I started sync-ui. But when I started sync-ui again (with the old syncevo-dbus-server from the first try was still running), it didn't complain either.
The output of dbus-monitor is attached. I see that it claims the name org.syncevoluti on.Server and calls the GetConfig method, but the reply of the daemon is close to nothing.