Comment 56 for bug 804936

Seems a bit far fetched (and possibly dumb, please beware): this issue arises with my installation, too, but very rarely so. My Zim-notebook is stored on a file share over the network. The server serving this file share is of course up 24/7. Sometimes I have to keep my workstation up 24/7, too. It seems to me that the issue arises if my workstation has been up for a week or more. Would it be a possibility that we're looking at an issue at operating system level? Could the clocks of the computers involved be out of sync and could this cause the problem?
On February 23rd I applied the folder patch proposed by Jaap and haven't had the issue since. Admittedly I also manually re-synced the internal clock and have over this time restarted the computer a couple of times.

I'm running Zim 0.65 on Windows 7 x64. As far as I know Windows will only re-sync the clock with an NTP server at startup and then once every week (except if manually triggered). So, if the clock drifts during this time it could explain the issue.

If my remark was a bit dumb, please disregard it.