Comment 7 for bug 608474

I have this problem as well. It happens often with text files that I save often, such as code. Nothing is ever lost due to the .u1conflict files, but it's extremely annoying. I found a fairly reliable way to reproduce.
- Create a text file that will be synced via U1.
- Make lots of little edits, saving over and over.
- Restart U1 with: u1sdtool -q; u1sdtool -c
- a .conflict file is created but there should be no conflict. The original file is reverted to a previous state. I use geany as a text editor which alerts me that the file has been changed.

To reproduce I had to manually restart U1. But in practice this happens to me a few times a day. This is potentially very bad. Lets say I am working on code, save the file, exit my text editor, upload to svn or wherever. If I am unlucky U1 might replace the file without me noticing.