Description
Summary
When using Extract from the Vorta archive browser and selecting a destination folder (e.g. ~/Downloads/Testing-Vorta-Borg-Mount), Vorta restores files to their original absolute-ish paths (e.g. media/S_Drive/projects/.../gemini.md) instead of the chosen destination. The Borg command logged by Vorta does not include any destination argument (e.g. no --destination), so extraction goes to the default working directory and preserves paths. UI reports “Restored files from archive … original path …”, matching observed behavior.
Mount + copy works after installing llfuse; Extract-to-folder still does not.
Also tested:
Vorta (Flatpak): com.borgbase.Vorta (latest stable at time of test)
Borg (Flatpak): /app/bin/borg --version (bundled)
Steps to Reproduce
Open Vorta and configure an existing Borg repo: /media/darren/4TB-Usb-Backup/borg.
Go to Archives, select any archive.
Click Extract…
In the restore dialog / destination picker, select a destination folder (e.g. ~/Downloads/).
Select a single file from the tree (example: media/S_Drive/projects/strategy-tester/docs/gemini.md).
Start Extract.
Expected
The selected file is extracted into the user-selected destination folder, e.g.:
~/Downloads/gemini.md (or a relative subtree under Downloads).
Actual
The file is restored to the original path (or into a structure matching that path), e.g.:
/home/darren/projects/strategy-tester/docs/gemini.md (original location)
and Vorta reports “Restored files from archive … media/S_Drive/projects/…/gemini.md”.
Evidence (log excerpts)
Vorta runs extract with no destination parameter:
See below extracts: apt Vorta log (/tmp/vorta.log):
UI responsiveness / “not responding” popups
Both apt and Flatpak Vorta intermittently show GNOME “Vorta/python3 not responding” popups during archive browse / extract, but Borg commands complete and Vorta recovers after ~10–30s.
Workarounds
Use Mount (after installing llfuse) and copy the desired file to any folder.
Use Borg CLI with an explicit destination (not preferred; this is a GUI issue).
Question
Is Extract-to-folder expected to work in Vorta 0.8.x? If yes, is Vorta missing a destination parameter for borg extract, or is there an alternate “Extract to…” implementation expected to set the extraction working directory / destination?
Reproduction
OS
OS: Ubuntu 24.04 (GNOME, Wayland)
Version of Vorta
Vorta (apt): Vorta 0.8.12-2 (/usr/bin/vorta) Repo encryption: repokey-blake2
What did you install Vorta with?
Other
Version of Borg
Borg (apt): 1.2.8 (/usr/bin/borg) shown in Vorta GUI
Logs
Running command /usr/bin/borg extract --list --info --log-json /media/darren/4TB-Usb-Backup/borg::darren-pc-2025-12-28-090606 --patterns-from /tmp/tmpz58srkte
media/S_Drive/projects/strategy-tester/docs/gemini.md
Running command: /app/bin/borg extract --list --info --log-json /media/darren/4TB-Usb-Backup/borg::darren-pc-2025-12-28-090606 --patterns-from /tmp/tmpj6o6i3_7
media/S_Drive/projects/strategy-tester/docs/gemini.md
There is no --destination passed.
Related: Mount initially failed due to missing FUSE backend
Mount failed until llfuse was installed:
Running command /usr/bin/borg --log-json mount ... /home/darren/Downloads/Testing-Vorta-Borg-Mount
ERROR - borg mount not available: no FUSE support, BORG_FUSE_IMPL=pyfuse3,llfuse.
Fix:
sudo apt install python3-llfuse fuse3
After that, Vorta Mount works and files can be copied out manually from the mount.
Description
Summary
When using Extract from the Vorta archive browser and selecting a destination folder (e.g. ~/Downloads/Testing-Vorta-Borg-Mount), Vorta restores files to their original absolute-ish paths (e.g. media/S_Drive/projects/.../gemini.md) instead of the chosen destination. The Borg command logged by Vorta does not include any destination argument (e.g. no --destination), so extraction goes to the default working directory and preserves paths. UI reports “Restored files from archive … original path …”, matching observed behavior.
Mount + copy works after installing llfuse; Extract-to-folder still does not.
Also tested:
Vorta (Flatpak): com.borgbase.Vorta (latest stable at time of test)
Borg (Flatpak): /app/bin/borg --version (bundled)
Steps to Reproduce
Open Vorta and configure an existing Borg repo: /media/darren/4TB-Usb-Backup/borg.
Go to Archives, select any archive.
Click Extract…
In the restore dialog / destination picker, select a destination folder (e.g. ~/Downloads/).
Select a single file from the tree (example: media/S_Drive/projects/strategy-tester/docs/gemini.md).
Start Extract.
Expected
The selected file is extracted into the user-selected destination folder, e.g.:
~/Downloads/gemini.md (or a relative subtree under Downloads).
Actual
The file is restored to the original path (or into a structure matching that path), e.g.:
/home/darren/projects/strategy-tester/docs/gemini.md (original location)
and Vorta reports “Restored files from archive … media/S_Drive/projects/…/gemini.md”.
Evidence (log excerpts)
Vorta runs extract with no destination parameter:
See below extracts: apt Vorta log (/tmp/vorta.log):
UI responsiveness / “not responding” popups
Both apt and Flatpak Vorta intermittently show GNOME “Vorta/python3 not responding” popups during archive browse / extract, but Borg commands complete and Vorta recovers after ~10–30s.
Workarounds
Use Mount (after installing llfuse) and copy the desired file to any folder.
Use Borg CLI with an explicit destination (not preferred; this is a GUI issue).
Question
Is Extract-to-folder expected to work in Vorta 0.8.x? If yes, is Vorta missing a destination parameter for borg extract, or is there an alternate “Extract to…” implementation expected to set the extraction working directory / destination?
Reproduction
OS
OS: Ubuntu 24.04 (GNOME, Wayland)
Version of Vorta
Vorta (apt): Vorta 0.8.12-2 (/usr/bin/vorta) Repo encryption: repokey-blake2
What did you install Vorta with?
Other
Version of Borg
Borg (apt): 1.2.8 (/usr/bin/borg) shown in Vorta GUI
Logs