Notes lost during synchonization

[John]

Binary package hint: tomboy

I'm running Ubuntu Intrepid 8.10 with Tomboy 0.12.0. This bug has been fixed in Tomboy 0.12.2 and 0.13.2. Can Ubuntu get an update for it's package? This bug is critical as it results in data loss. My apologizes if I am not following the proper procedure for reporting a data loss bug in an Ubuntu package.

tomboy:
  Installed: 0.12.0-0ubuntu1
  Candidate: 0.12.0-0ubuntu1
  Version table:
 *** 0.12.0-0ubuntu1 0
        500 http://archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

The following is from Gnome Bug 565102:

In certain sync scenarios, it is possible that Tomboy will think several notes
have been deleted, and cause them to be removed from all synchronized
computers.

Steps to reproduce:

0. Clear sync server; have lots of notes on computer 1 that aren't on computer 2
1. Sync computer 1
2. Sync computer 2
3. Restart Tomboy on computer 2
4. Sync computer 2
5. Sync computer 1

Expected results:

Computer 1 and computer 2 have the same notes, which are equivalent to (computer 1's original notes) + (computer 2's original notes).

Actual results:

Both computers have Computer 2's original notes, but many of Computer 1's original notes are deleted (on both computers).

What's happening here is that when Computer 2 does its original sync (step 2), it is not always saving the new notes to the file system. So once Tomboy is restarted, the notes disappear, which is interpreted as a willful deletion. Computer 1 syncs the results of that deletion, and note disappear.

They can be restored from ~/.tomboy/Backup, but you may need to clear out the sync server and start over again.

[Pedro Villavicencio (pedro)]

Looks like a valid SRU case for me, upstream patch is here: http://bugzilla.gnome.org/attachment.cgi?id=125008&action=view ; nominating it for intrepid.

[Robert Ancell (robert-ancell)]

Fixed in 0.12.2

[Alex Valavanis (valavanisalex)]

Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the
report. The bug has been fixed in newer releases of Ubuntu.