On Mon, 2012-07-09 at 02:09 +1200, Jane Atkinson wrote:
On 09/07/12 01:32, Patrick Ohly wrote:
> On Sat, 2012-07-07 at 16:24 +1200, Jane Atkinson wrote:
>> Can you quote the output? What kind of changes did you expect to
> get synced?
It's a day or two now since I did this, so it's from memory. I had
changed the end time of an event - something I've done regularly in
the past with no problems. The messages in the terminal were exactly
what I'd expect to see if no changes had been made.
Only a calendar.before directory was created - nothing else. And a log
file, of course.
Then the sync process crashed without completing normally. Otherwise
there would be a calendar.after directory. Can you send me that
syncevolution-log.html file?
Can you reproduce the problem? If yes, then try to capture a stack
backtrace of the crash, like this:
- killall syncevo-dbus-server
- SYNCEVOLUTION_SYNC_DELAY=60 /usr/libexec/syncevo-dbus-server &
- in another shell, run the command line
- in a third shell, run "gdb -p `pidof syncevo-dbus-helper`"
followed by "cont" (when debugger has attached) and
"thread apply all bt" (once/if it crashed)
--
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.