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

Addition of confined level #10

Open
adrianrudnik opened this issue Jun 7, 2020 · 0 comments
Open

Addition of confined level #10

adrianrudnik opened this issue Jun 7, 2020 · 0 comments

Comments

@adrianrudnik
Copy link

Currently using this lib to build a snap compatible command line tool and while declaring the snap plugs for personal-files I found that it does not consider those paths.

Output of QueryFolders() on an unconfined binary:

/home/adrian/.config/pushover-cli
/etc/xdg/xdg-plasma/pushover-cli
/etc/xdg/pushover-cli
/usr/share/kubuntu-default-settings/kf5-settings/pushover-cli

which is fine. As soon as I use the same method inside a snapped binary:

/home/adrian/snap/pushover-cli/x1/.config/pushover-cli
/etc/xdg/xdg-plasma/pushover-cli
/etc/xdg/pushover-cli
/usr/share/kubuntu-default-settings/kf5-settings/pushover-cli

After I connect the personal-files interface on my snap it still does not consider $HOME/.config a valid directory.

Maybe it could consider /home/$USER as a possible location on linux, even if $HOME is present, as those two can differ in a confined deployment.

I cant use LocalPath as the order is mixed. If I read or write a config, I prefer $HOME/.config over $HOME/snap/ and only if write access to former is not possible, I want to write to $HOME/snap. That does not mean that it should not detect a possible read-only config file in $HOME/.config.

Any idea how to handle this gracefully?

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

1 participant