This is also true for Debian- and many Ubuntu-forks. Flatpak also is available for almost every distro and many do support it out of the box.

That's why, with this topic I suggest to also support flatpak, via flathub as distribution option.įlatpak will bring an always sandboxed, stable environment, so that the actual user support is pretty minimal and limited to the 'flatpak environment', not for example 'Arch, Fedora, Gentoo'. If you do not run Ubuntu or Debian you have to do a lot of, sometimes strange, actions to make spotify work for you, tbh even the Debian setup is sub-optimal. Official support flatpak and the distribution on f.Ĭurrently Spotifys distribution options are: Snap and general Debian apt-repository.(I imagine it would unless Flatpak gets upset about applications having conflicting/overlapping Owns lines. 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.

Flathub spotify