Local Directory Sync Service Add-in broken

Bug #1132503 reported by Redsandro
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tomboy
New
Undecided
Unassigned

Bug Description

I am not sure if this bug is ancient or not because throughout history of Tomboy this plugin has always had version "0.1", but it's fairly simple:

The directory chooser of the plugin preferences starts in ~/ (home), and you can choose a different folder, e.g. ~/Dropbox/tomboy/. So far so good.

But when you actually perform the sync, a new folder will be created called ~/0/0/ and all your notes will be synced here.

Tested on Linux Mint 14 Cinnamon (probably same package as Ubuntu 12.10).

Revision history for this message
Redsandro (redsandro) wrote :

I know, who uses Directory Sync anymore, right? But since Ubuntu One syncing is broken (#1116237), and using the same Dropbox simlink on multiple machines causes too many "conflicted copies" to emerge because rebooting machines automatically re-open notes that were open, even if nothing is changed, I keep getting a lot of conflicted copies. That won't happen when copies outside of Dropbox are open, so I'd rather have every Tomboy sync them to Dropbox every [interval].

information type: Proprietary → Public
dobey (dobey)
affects: ubuntuone-servers → tomboy
Revision history for this message
Redsandro (redsandro) wrote :

@dobey I am not sure what that means, but the Local Directory Sync Service is not related to ubuntuone-servers. The bug concerning U1 is 1116237.

Revision history for this message
Redsandro (redsandro) wrote :

How can I *manually* change the path for the sync settings? This bug is not getting attention so I am trying to find a workaround.

I think the process of choosing a directory is not working (anymore) with recent environments, maybe if I set it manually, I can override the defunct plugin settings.

3/14/2013 9:24:04 PM [DEBUG]: AddinManager.OnAddinLoaded: Tomboy.FileSystemSyncServiceAddin
3/14/2013 9:24:04 PM [DEBUG]: Name: Local Directory Sync Service Add-in
3/14/2013 9:24:04 PM [DEBUG]: Description: Synchronize Tomboy Notes to a local file system path
3/14/2013 9:24:04 PM [DEBUG]: Namespace: Tomboy
3/14/2013 9:24:04 PM [DEBUG]: Enabled: True
3/14/2013 9:24:04 PM [DEBUG]: File: /usr/lib/tomboy/addins/FileSystemSyncService.dll

Revision history for this message
Redsandro (redsandro) wrote :

Workaround found:

1) Set the options for Tomboy.FileSystemSyncServiceAddin 0.1
2) Click save
3) Do NOT choose to sync immediately.
4) Close Tomboy
5) Start gconf
6) Change /apps/tomboy/sync/sync_local_path to your desired path
7) Start tomboy
8) Sync once and setup automatic syncing every x minutes.

Now it will sync to [specified path]/0/0 in stead of ~/0/0

Revision history for this message
Redsandro (redsandro) wrote :

This doesn't seem right either:

[backupdir]/manifest.xml
is exactly the same as
[backupdir]/0/0/manifest.xml

Revision history for this message
Jared L Jennings (jaredljennings) wrote :

We are looking to fix the filesystem sync so that it will properly work with Dropbox or any other such filesystem sync tools. I'm expecting by June a patch will be out for this.

Someone feel free to file an upstream defect if they like.

Revision history for this message
Redsandro (redsandro) wrote :

I am guessing a buffered note sync like this old idea to circumvent the locking mechanism would have solved the problem because files would not be directly locked by the program, it would solve two problems at once.

https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/839188

It's probably more complicated than that though.

Revision history for this message
Redsandro (redsandro) wrote :

FYI, This bug affects:
- Ubuntu 12.10
- Linux Mint 14 Cinnamon

This bug does NOT affect:
- Xubuntu 12.04 LTS

Revision history for this message
Jared L Jennings (jaredljennings) wrote :

I wonder how that can be? I would expect the issue to be the same.
Are you up for taking a debug trace?

mono.exe --trace=N:Tomboy Tomboy.exe --debug > tomboy-trace.log

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.