By default, Snapcraft should already be installed on Ubuntu systems unless it was removed previously. The third way to install Spotify on Ubuntu is by using the Snapcraft package manager.
Trying to connect to unix:/run/user/1000/pulse/native. Method 3: Install Spotify with Snapcraft. Using shared memory pool with 1024 slots of size 64,0 KiB each, total size is 64,0 MiB, maximum usable slot size is 65472 I would suggest reaching out to spotify and asking them to add it. It may well be the case that spotify does not have the right slot declared in the snap.
Once connected it should be able to use the media player interface from your confined snap. Please double check that these are connected: snap interfaces spotifyĪnother thing you can try is run spotify from the console and enable debugging logs and paste the output: PULSE_LOG=4 SNAPD_DEBUG=1 SNAP_CONFINE_DEBUG=1 /snap/bin/spotifyįWIW, libpulse logs I get here are: Parsing configuration file '/etc/pulse/nf' AFAICT the spotify snap needs to expose a mpris slot, while your snap needs a similar plug. Albeit, this was with some older version and I don’t recall seeing it recently. deb which you can install in Ubuntu instead of using the snap. Snapcraft supports multiple build tools and programming languages, such as Go, Java, JavaScript, Python, C/C++ and Rust. I’ve seen the problem with spotify not closing before when using spotify from AUR and with a repacked spotify RPM on Fedora. Kernel tried the LTS kernel 4.9.70-1-lts, got the same results. Apparmor-related denials for Spotify snap - snap - snapcraft.io I’m running the Spotify snap (version 1.1.46.916.g416cacf1, snapd 2.48+20.04 on Ubuntu 20.04), and noticed repeated apparmor audit messages for stuff that was denied.
0 kommentar(er)
