On Do, 2010-12-16 at 17:01 +0100, Patrick Ohly wrote: > On Do, 2010-12-16 at 15:39 +0000, Giuseppe Gerace wrote: > > Excuse me, the one I've previously posted is syncevo-dbus-server > > output. > > What you posted (Thu, 16 Dec 2010 12:27:52 +0000) is the output from > syncevo-http-server, the Python script which implements the HTTP part. > The error message you show is related to something which has gone wrong > earlier in syncevo-dbus-server, so the output from that process would be > more useful. > > syncevo-dbus-server also writes very detailed -log.html files (see > "syncevolution --print-sessions @default"), which is what is needed if > the stdout output of syncevo-dbus-server doesn't explain the problem. > > I understand that is all not as easy as it could be. Issues are open to > improve it (http://bugs.meego.com/show_bug.cgi?id=10270, > http://bugs.meego.com/show_bug.cgi?id=6369), but no-one has had the time > to work on those.
I've completed work on these issues over the Christmas vacation. Giuseppe, if you are still interested, then please try again with the syncevo-http-server.py script from http://meego.gitorious.com/meego-middleware/syncevolution/blobs/raw/master/test/syncevo-http-server.py Use its command line options to setup the server instead of following the HOWTO (will update that soon). All relevant output will be printed by syncevo-http-server, so syncevo-dbus-server can run in the background. -- 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
