http://bugs.meego.com/show_bug.cgi?id=10265
--- Comment #13 from pohly <[email protected]> 2010-11-22 04:44:25 PST --- (In reply to comment #12) > Indeed, this is what seems to be happening: syncevolution connects to > Evolution > Data Server, which only seems to poll caldav _after_ the connection (or at > least _after_ feeding its state to syncevolution). Strange, but given that timing doesn't seem to matter, this looks plausible. > So, a workaround would be to run syncevolution --status first (on PC), and > only > then run the syncevolution client from the mobile. > > Syncevolution seems to communicate with EDS using DBUS. Maybe there is one > DBUS > command which causes EDS to "refresh" itself from caldav which is being sent > too late? Is there a "tcpdump"-like tool for DBUS, so that I could find out > what happens? There is dbus-monitor. I have no idea what could be triggering it via libecal, though. Perhaps a simple libecal open/close would be enough? Do you think you can extract the relevant calls from either libecal example code (Google search) or the EvolutionCalendarSource.cpp to try this out? -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
