Are you sure that there was no other syncevo-dbus-server running? It should have complained about that, though.
Regarding "a lot of segfault related forum-threads on the web" - I'm not aware of those. Very few crashes were ever reported to me, and those should all be fixed in 1.2.2. Do you have some pointers?
Can you try again and this time also check what dbus-monitor in another shell window reports? It should show that syncevo-dbus-server claims the bus name org.syncevolution.server when it starts, then show GetConfig method calls and their replies as the sync-ui starts talking to the daemon.
Are you sure that there was no other syncevo-dbus-server running? It should have complained about that, though.
Regarding "a lot of segfault related forum-threads on the web" - I'm not aware of those. Very few crashes were ever reported to me, and those should all be fixed in 1.2.2. Do you have some pointers?
Can you try again and this time also check what dbus-monitor in another shell window reports? It should show that syncevo-dbus-server claims the bus name org.syncevoluti on.server when it starts, then show GetConfig method calls and their replies as the sync-ui starts talking to the daemon.