tomboy
tomboy copied to clipboard
tomboy-notes
Sync with local folder stopped working
Tomboy 1.15.9 Ubuntu MATE 17.10
Sync with local folder (in Dropbox) fails. "Failed to Synchronize Could not synchronize notes. Check the details below and try again." Nothing is listed in details.
I think the problem started after upgrading from Ubuntu 17.04 to 17.10. Sync is still working fine on Windows.
From tomboy.log:
11/22/2017 10:37:20 AM [ERROR]: Synchronization failed with the following exception: /home/lee/Dropbox/AppDocuments/tomboy/4/419/6fc91641-2e3c-4e77-b6b5-0137091a4056.note does not exist
at System.IO.File.Copy (System.String sourceFileName, System.String destFileName, System.Boolean overwrite) [0x000d1] in <8f2c484307284b51944a1a13a14c0266>:0
at Tomboy.Sync.FileSystemSyncServer.GetNoteUpdatesSince (System.Int32 revision) [0x0016d] in
Lee, I guess you have checked that the directory indicated is visible and writable with Linux ?
/home/lee/Dropbox/AppDocuments/tomboy/ ?
Can you see a file called 6fc91641-2e3c-4e77-b6b5-0137091a4056.note there ?
David
On 23/11/17 02:54, Lee Raulin wrote:
Tomboy 1.15.9 Ubuntu MATE 17.10
Sync with local folder (in Dropbox) fails. "Failed to Synchronize Could not synchronize notes. Check the details below and try again." Nothing is listed in details.
I think the problem started after upgrading from Ubuntu 17.04 to 17.10. Sync is still working fine on Windows.
From tomboy.log: 11/22/2017 10:37:20 AM [ERROR]: Synchronization failed with the following exception: /home/lee/Dropbox/AppDocuments/tomboy/4/419/6fc91641-2e3c-4e77-b6b5-0137091a4056.note does not exist at System.IO.File.Copy (System.String sourceFileName, System.String destFileName, System.Boolean overwrite) [0x000d1] in <8f2c484307284b51944a1a13a14c0266>:0 at Tomboy.Sync.FileSystemSyncServer.GetNoteUpdatesSince (System.Int32 revision) [0x0016d] in :0 at Tomboy.Sync.SyncManager.SynchronizationThread () [0x001d6] in :0
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tomboy-notes/tomboy/issues/79, or mute the thread https://github.com/notifications/unsubscribe-auth/AF__MBYsmm0lzQN6Nt68KijYlgqi0D4yks5s5EOggaJpZM4QnnlV.
I must confirm, that local sync is not working using 17.10. I was testing 2 machines. Sync with local NAS was working like brilliantly with older systems. Sync-notes appear in cache, but can not find their way into application. I am unable to remove application an purge. Old settings will always show again. Nerve wrecking situation.
First problem to solve: How can I delete old installation from profile?
2ndly: Why doesn't sync? I is always syncing it's own 2 or 3 notes from blank installation and will not give up on them. Local note should to be overwritten by server notes. 17.10 seems to follow Win10 in terms of causing problems to established software.
Tmails, I suspect I can only be limited help to you but I'll try. Some suggestions, in no particular order.
On a Linux box, to remove the full profile, you probably need to remove the directory ~/.config/tomboy I would shut Tomboy down, move the config dir, start Tomboy up again.
I would be very surprised if there is something specific about Ubuntu 17.10 that causes sync to fail. More likely you are not getting shared drive mounted as expected, perhaps its mounted in a different place ? Or some file share is mounted read only maybe ? I am just guessing here.
I personally have not used file sync with Tomboy, my only understanding of it comes from implementing what I think is how it works for tomboy-ng. So please be careful with what I say ! I think you should be able to safely stop Tomboy, move all your notes and all Tomboy config out of the way (not delete!) and then start Tomboy up again and reconfigure, inc setup your file sync. That process will have a good look at where you are pointing to and if it thinks it does not make sense, should tell you. Hmm, you may need to run the deb setup again (to create empty config files) after moving the existing Tomboy files, sorry, I don't know.
Its worth starting Tomboy from the command, sometimes you see warnings and error messages sent to the console.
If you get really desperate, grab a copy of tomboy-ng and try and point it at your sync repo. Because of my cowardliness, I make a report about what the initial sync will do and make the user look at it before proceeding, it might just tell you something that Tomboy did not spot. Good luck !
After installing Tomboy 1.15.4-0ubuntu3 into Linux Mint 18.3, I have hit an issue with the same symptoms. This is what I see in the log:
4/23/2018 8:30:30 PM [ERROR]: Synchronization failed with the following exception: /home/mce/Dropbox/Notes/15/1591/2bedfc20-28c0-4356-9a3c-73d78a438b52.note does not exist
at System.IO.File.Copy (System.String sourceFileName, System.String destFileName, Boolean overwrite) <0x7f9f62959b00 + 0x002c0> in <filename unknown>:0
at Tomboy.Sync.FileSystemSyncServer.GetNoteUpdatesSince (Int32 revision) <0x405ee1f0 + 0x00564> in <filename unknown>:0
at Tomboy.Sync.SyncManager.SynchronizationThread () <0x405e2c20 + 0x0069d> in <filename unknown>:0
ls -la /home/mce/Dropbox/Notes/15/1591/
total 28
drwxrwxr-x 2 mce mce 4096 Apr 23 20:04 .
drwxrwxr-x 102 mce mce 4096 Apr 23 20:02 ..
-rwxrwxr-x 1 mce mce 4503 Sep 13 2016 manifest.xml
I am synchronizing Notes folder by DropBox. I'm using another two machines with Ubuntu Linux variants without a problem, output of ls in that specific directory looks same as above.
I just found that the working Tomboy package is 1.15.9-0ubuntu1. Maybe the older package, although installed along with the newer release-date OS ubuntu 18.3, cannot read the data created by a newer package included in ubuntu 17.10.
Thank you all for your helpful comments and participation. I did solve my problem after all by deleting the local tomboy-profile. After creating a new exported version of sync files with another machine, I was able to use this as a base to sync the new machines. So I didn't get to the root of the problem, but I found my work-around to fix it.
Sorry, I just noticed all this. I'll try to look into it more soon. It would be nice if it would work... I had been using it quite a bit, and I used it mainly for easily syncing notes between machines. I don't think it's worked anywhere since I upgraded to Ubuntu 18.04, which I have on two laptops and VirtualBox.
In case anyone is still interested in this... I was using Tomboy in both Windows and Linux, and I was syncing them all to the same Dropbox folder. It still works fine on Windows, but syncing stopped working after upgrading to I think Ubuntu 17.10.
One thing I notice is that the notes folder on Windows (%APPDATA%\Tomboy\notes) just has a bunch of *.note files and one manifest.xml file.
In Linux, the corresponding directory (~/.local/share/tomboy/) has folders numbered 0-6, and each one has about a hundred numbered folders (ie 6/ has 600/ 601/ etc). Some have notes, but most just have manifest.xml. Tomboy's synch feature creates these nested folders. I'm not sure how it's supposed to work, but apparently it doesn't work properly when I sync to the same folder from different computers.
My Tomboy on Windows was the most up to date, so I deleted the contents of the notes folder in Linux and pasted in the contents from Windows, and it works fine. So if you want to sync more than one computer with Dropbox, the best way might be to not use the synchronize feature and just symlink the notes folder to a folder in Dropbox.
Stupidly late to respond, sorry ! Your linux install of Tomboy does not sync ? But in its (~/.local/share/tomboy/) folder it has hierarchical folders with number for name ? That sounds like a sync directory. But the location is where your working notes should be. I'd suggest you check your config, pretty sure you have your sync dir set to ~/.local/share/tomboy/ instead the dropbox location.
Now, those hierarchical directories in your notes directory will do no harm but sure will do no good either. Its apparently syncing there but, obviously that dir is not accessible to other systems.
Sorry I did not spot this a lot earlier, might be an easy fix if you are still interested.
Davo