On Mon, 2016-02-08 at 09:19 +0100, deloptes wrote:
> Patrick Ohly wrote:
>
> > In case of a local sync, two processes are involved. You need to attach
> > to syncevo-local-sync (gdb -p `pidof syncevo-local-sync`) and have a
> > look where that one is stuck when the problem occurs.
>
> Thanks
Patrick Ohly wrote:
> LocalTransportAgent::storeSyncReport() is the parent side and logs "got
> child sync report" once the data made it across the local D-Bus
> connection. Do you see that when running with SYNCEVOLUTION_DEBUG and
> loglevel=10?
yes I see status=200 - everything went good, but
