-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flatpak version can't save files to home #181
Comments
We discussed this here heavily and came to the conclusion that opening all available portals sufficient. For example, if you put the files in ~/Downloads or ~/Videos it'll work. You can open your home directory with the command |
I executed the command you suggested, however it only worked as root (otherwise I got permission denied) - and still, I can't access my home directory - however Downloads / Desktop work as expected. This is a workarround I can live with - however it still seems like a hack. Is the "average user" really expected to cope with stuff like this? I am using several other flatpak applications (netbeans, IntelliJ) which have no issue accessing the whole filesystem as if they were installed nativly. |
Those other applications have full access to the host system. This is something that we restricted a while back because it defeats the sandbox promise. Instead of "home", you can also add "host" to give full access. It need root because you installed it system-wide. |
Why would Your current approach makes no sense. |
Take Pingus ( |
When trying to save files using the linux desktop app installed via signal, I can only save to an "empty" home directory.
My guess is due to flatpak the signal app runs in some kind of sandbox, which provides the signal app with some kind of "fake" home directory - which might be great for security, but actually is painful if you really would like to save files to your real home directory ;)
The text was updated successfully, but these errors were encountered: