You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Xournal++ on flatpak should save each new unsaved file to a different folder inside the cache autosave directory. However, they all save to 2.autosave.xopp, overwriting each other and leaving only the last autosaved file.
Expected Behaviour
Each new file should autosave with a unique filename, even on flatpak.
Steps to Reproduce
Create and write on a new, unsaved Xournal++ file, and wait until an autosave is created in ~/.var/app/com.github.xournalpp.xournalpp/autosaves/.autosaves.xopp
Create a second unsaved file and wait until that file is autosaved
The autosave from the second file will overwrite the autosave from the first file
Additional Context
To my understanding, this is because Flatpak apps run in an isolated namespace, and Xournal++ always runs inside the isolated namespace with a PID of 2 , so all autosaves of new files are saved to 2.autosave.xopp
The text was updated successfully, but these errors were encountered:
Operating System
Linux
(Linux only) Distribution
Fedora
(Linux only) Desktop Environment
GNOME
(Linux Only) Display Server
Wayland
Installation Method
Flatpak
Xournal++ Version
1.2.3
libgtk Version
3.24.43
Bug Description
Xournal++ on flatpak should save each new unsaved file to a different folder inside the cache autosave directory. However, they all save to 2.autosave.xopp, overwriting each other and leaving only the last autosaved file.
Expected Behaviour
Each new file should autosave with a unique filename, even on flatpak.
Steps to Reproduce
Additional Context
To my understanding, this is because Flatpak apps run in an isolated namespace, and Xournal++ always runs inside the isolated namespace with a PID of 2 , so all autosaves of new files are saved to 2.autosave.xopp
The text was updated successfully, but these errors were encountered: