Crash while trying to sync notes using local folder on an external hard drive about tomboy-ng

[davidbannon]

Hi Erik, thanks for the report.

Most of that stack trace you have sent is about LCL components complaining about exiting before cleanup so have happened after the problem.

My guess is you have a corrupted note and, to my chagrin, tomboy-ng is not reporting it correctly ! If you can work out which note you can have a look at it. Otherwise, best idea would be for me to make a special binary (I'm guessing you don't have Lazarus installed) with a lot more debugging turned on.

I assume you have the latest tomboy-ng ? v0.15 ? I have a bit more error reporting in there, however, I expect in the event of a crash, you won't see it. Sigh ...

A possible test might be to open each note, one by one and see if one of them fails, again, some error reporting will appear in the Search form. If you can find the offending note, look at the xml (if you can). If the note itself does not have any sensitive info, I'd love to see it so please keep a safe copy before trying to fix it.

Of course, if the corrupted note is in the sync repo rather than the local note directory, thats harder....

tomboy-ng is 'designed' to recover from a sync problem by starting from scratch but I strongly advise against that until we have no choice. Tomboy is a bit inclined to double up on notes doing that too I'm afraid.

David

[erik-brangs]

I don't know how to find the problematic note and I've got about 2000 notes. Therefore, I'd prefer the binary.

I tried throwing away the local directory and sync from the folder but it also crashed. So I suppose the problematic note is in the sync folder.

I'm not sure about Lazarus. I installed the 0.15 amd64 Debian package from the releases page.

[davidbannon]

OK, there is now a new binary in that release, tomboy-ng-special.gz. You can ungzip that, it contains only a tomboy-ng binary, for Linux 64bit. Its basicily the same as the one you have now but accepts a command line switch that turns on a quite wordy dump of lines during sync. Hopefully will show, note by note, report of which one we are looking at. Last one we see before the crash is the problem.

./tomboy-ng --debug-sync

If you look at that one, and either determine whats wrong or, better still, after checking it has nothing sensitive, send it to me. Once I know whats wrong, I can build another binary that will at worse skip that note, ideally fix it.

We may be able to fix that not "by hand".

David

[davidbannon]

A further thought, if you have 2k notes, then that list of debug messages will be quite long.

./tomboy-ng --debug-sync >> debug.report

might be a good idea. You will generate a file up to a meg or so, depending on when it crashes.

..... and the last line of my previous message should have been -

"we may be able to fix that "by hand""

Davo

[erik-brangs]

I sent you an e-mail with the information a while back. You should have received it by now unless it was caught by some spam filter.

[davidbannon]

(an off line discussion ensured).
Fixed in current head and will be fixed in release v0.16
Thanks for the report and subsequent testing.