We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/ublue-os/bazzite/blob/main/system_files/desktop/shared/usr/libexec/bazzite-flatpak-manager#L43 Bazzite runs this command to globaly make the xdg-data/icons folder read-only. However, this folder equates to ~/.var/app/<app>/data/icons, which is a logical place to store icons specific for the usage of the application.
xdg-data/icons
~/.var/app/<app>/data/icons
I would not expect Bazzite to lock me out of creating/writing to folders inside of my own application workspace.
rpm-ostree status
I am not a bazzite user, so I don't have access to this. This original report came from a user.
No response
Here's a very simple flatpak that can reproduce this issue
id: com.imdevinc.IconTest runtime: org.freedesktop.Platform runtime-version: '23.08' sdk: org.freedesktop.Sdk command: hello modules: - name: hello buildsystem: simple build-commands: - install -Dm755 hello.sh /app/bin/hello sources: - type: script dest-filename: hello.sh commands: - echo "Hello world, from a sandbox" - mkdir -p $XDG_DATA_HOME/icons - touch $XDG_DATA_HOME/icons/test-icon
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
https://github.com/ublue-os/bazzite/blob/main/system_files/desktop/shared/usr/libexec/bazzite-flatpak-manager#L43
Bazzite runs this command to globaly make the
xdg-data/icons
folder read-only. However, this folder equates to~/.var/app/<app>/data/icons
, which is a logical place to store icons specific for the usage of the application.What did you expect to happen?
I would not expect Bazzite to lock me out of creating/writing to folders inside of my own application workspace.
Output of
rpm-ostree status
I am not a bazzite user, so I don't have access to this. This original report came from a user.
Hardware
No response
Extra information or context
Here's a very simple flatpak that can reproduce this issue
The text was updated successfully, but these errors were encountered: