"Synchronize active database with a file" fails on linux
A lightweight and easy-to-use password manager
Brought to you by:
dreichl
Menu
▾
▴
#2011 "Synchronize active database with a file" fails on linux
The trigger action "Synchronize active database with a file" is currently broken on linux (Fedora and Arch tested). I tested with version 2.47 and 2.46. It fails with error:
Failed to import the specified file!
Root element is missing.
The file does exists and it fail even if it is 100% identical. It used to work and it started failing recently.
Root element is missing implies one of the databases is corrupt.
Create a new database, save it, copy it, then sync to the copy. Does this work?
Have you changed / updated anything just before it stopped working?
cheers, Paul
It seem that my google drive is doing some weird things. I can't even explain what happened as it doesn't make sense. I copied my database manually on my google drive and it would fail to sync through my trigger (which copy the db to /tmp/ before syncing) but manually syncing with a local copy would work. In any case the problem is with google drive.
Why the copy to tmp?
You have a database open, sync to GD, done.
cheers, Paul
Because I'm using kioclient5 to access the google drive and it doesn't work like a traditional mount. I see that a fuse based kio mounter got released very recently so maybe I'll have a look at that. I also couldn't find an add-on that would work on linux to sync to google drives, unless that also recently changed.
Does https://rclone.org/ behave better?
cheers, Paul
rclone indeed work good so far. I can mount and sync to my google drive directly. Thank you and all is good for now I hope.