▲ | alkonaut 14 hours ago | |||||||||||||||||||||||||
Why do these things not work properly when apps are flatpaks? e.g. if an app tries to query the environment and ask "what's the theme", how would it get a different answer when run from a flatpak? | ||||||||||||||||||||||||||
▲ | thyristan 13 hours ago | parent | next [-] | |||||||||||||||||||||||||
Different answers for different problems, but basically two reasons. First, library/software/data versions inside the flatpak can and will be different from the ones outside. So a flatpak might as "what is the current Qt5 theme", and get the answer "don't know about Qt5, but the Qt6 theme is cute-cats-qt6" which it cannot interpret. Things like themes might not even be available inside the flatpak, so even if the answer were parseable, cute-cats-qt6 might just not be available on the inside. Second, flatpaks are sandboxed, so things will be filtered. This means that a query might not get through, an answer might not get through, both might be altered. Or maybe an answer might be useless because "you can get the theme at /usr/share/themes/cute-cats-qt6" points to a path that the flatpak is not allowed to access. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
▲ | afiori 11 hours ago | parent | prev [-] | |||||||||||||||||||||||||
I don't actually know but I guess the issue is that the theme/gui libraries are sandboxed too |