Skip to content
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

Closed
ceisserer opened this issue Mar 28, 2021 · 5 comments
Closed

Flatpak version can't save files to home #181

ceisserer opened this issue Mar 28, 2021 · 5 comments

Comments

@ceisserer
Copy link

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 ;)

@bermeitinger-b
Copy link
Collaborator

bermeitinger-b commented Mar 28, 2021

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
flatpak override --filesystem=home org.signal.Signal

@ceisserer
Copy link
Author

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.

@bermeitinger-b
Copy link
Collaborator

bermeitinger-b commented Mar 28, 2021

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.

@Buggem
Copy link

Buggem commented Sep 20, 2024

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 flatpak override --filesystem=home org.signal.Signal

Why would home dirs be blocked by default? Config files are stored there, whereas it wouldn't make sense to allow the place where personal files are stored (~/Documents).
If anything, reverse your approach and make it that Documents, Videos, Music etc. can't be accessed without user permission.

Your current approach makes no sense.

@Buggem
Copy link

Buggem commented Sep 20, 2024

Take Pingus (org.seul.Pingus) for example. It stores its config in ~/.{app name} (~/.pingus in this case), like many other programs do. Why is it sandboxed from accessing that folder, it breaks the game and makes it impossible to save!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants