On Mon, 2014-02-10 at 15:22 +0100, Daniel CLEMENT wrote: > Le dimanche 09 février 2014 à 20:05 +0100, Patrick Ohly a écrit : > > On Fri, 2014-02-07 at 22:23 +0100, Daniel CLEMENT wrote: > > > Perhaps there is a residue of an old config. which is still interfering? > > > On this (test) PC I could try and purge and reinstall everything. > > > > Even if it fails there should be some indication how. Please type the > > commands below in a shell and send the resulting /tmp/syncevo.out text > > file. > > > > script /tmp/syncevo.out > > syncevolution --daemon=no --version > > SYNCEVOLUTION_DEBUG=1 gdb --args /usr/libexec/syncevo-dbus-server > > --no-syslog --stdout --verbosity 3 -d unlimited > > run > > > > Now it should still be running (no gdb command prompt). Run the sync-ui > > separately. If it crashes or quits, gdb will tell you. In that case, > > type > > > > thread apply all bt > > > I get this: > ----- [...]
> ...but the 2nd command produces no further output. I tried to rerun > everything, but on the next runs the syncevo.out remains empty!? Can you please follow the instructions step-by-step and then attach the entire /tmp/syncevo.out file? I can't believe that gdb quits without printing anything. Therefore I want to see exactly what you doing. Otherwise I can't help. Copy-paste each line, press return after each line. The first command starts a script session, the third commands starts gdb (must be installed), then "run" inside gdb starts syncevo-dbus-server. -- 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] https://lists.syncevolution.org/mailman/listinfo/syncevolution
