Although most of the features are self-explanatory, we have elaborated some of them below the comparison table. The table below gives a detailed summary of the key differences between Snap, Flatpak, and AppImage.
Packages without this update information can be updated with a tool like AppImageUpdate. Instead, the AppImage package comes with additional information on how to install updates. Another feature to note is that it does not use repositories to install package updates like Snap and Flatpak. (I imagine it would unless Flatpak gets upset about applications having conflicting/overlapping Owns lines.Users can find the packages on the AppImage website. If you don't want to go to that effort, at least see if adding an Owns for 2.* works rather than granting unfettered D-Bus access.
for Audacious Media Player, .* for Firefox, .* for MPV, .* for Ungoogled Chromium, etc.) I don't use Spotify but, based on what I know of how that MPRIS integration works from trying to keep Plasma from interfacing with Firefox without losing the ability for non-Plasma things to interface with it, and based on it working Just Fine™ for the Flatpak apps I do use, you'll want to add the appropriate under Session Bus > Owns. The proper solution, in the general case, is to use an app like Bustle to figure out the specific D-Bus endpoints it needs.
You're granting full access to tons of D-Bus APIs that can be used to execute arbitrary code outside the sandbox. That's analogous to saying "Add filesystem=host:rw" or advising people to solve permissions problems in a non-Flatpak app with sudo. Under the "socket" section enable "D-Bus session bus" option and restart spotify.
0 kommentar(er)
