This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Use different permissions when mounting archive. #520
Labels
type:bug
Something doesn't work as intended
Hi, I'm running Vorta 0.6.26 and Borg 1.1.13 on openSUSE Tumbleweed.
I just discovered a really weird anomaly with Vorta. I tested a backup of my Firefox
~/.mozilla
directory by using Vorta to mount the repo to~/Desktop/a
, renaming my~/.mozilla
folder and using Dolphin to copy it from~/Desktop/a/home/myself/.mozilla
to its normal location. This consistently led to a corrupt Firefox profile, as described here. I don't understand all the moving parts in Firefox, but it's either a permissions problem or some other kind of corruption with one of the sqlite databases it uses.By simply creating a filesystem copy of the
~/.mozilla
profile on my local disk and closing Firefox and renaming the original profile and copying back the backup, Firefox launches as expected as if nothing happened.So I tested again with the same process as described above, except I manually created the backup and manually mounted it with
borg create
andborg mount
, and repeated the profile restore process. This also worked as expected.Then I manually mounted with
borg mount
a backup created with Vorta and restored my profile from that, which also worked correctly.Then I used Vorta to mount the manually created borg backup described above, and this gave me a corrupted profile.
So Vorta must be doing something weird with the way it's mounting the backups. I confirmed this happens every time I tried to mount it via Vorta and restore the profile, both from a USB HD repo and from my NAS over SSH.
Thanks for the help.
The text was updated successfully, but these errors were encountered: