Latest Spotify client re-packaged from the Ubuntu packages for supported Fedora and RHEL/CentOS distributions.
This package tries to comply as maximum to the Fedora Packaging Guidelines; this means the packages has debuginfo packages, default Fedora’s GCC compile time options (where possible) and standard locations for binaries, data and docs.
The provided client is binary only and compiled for Ubuntu, so the Fedora package de-assembles the original Ubuntu package and moves all files in the appropriate places. The Spotify client requires assets (icons, data packages, etc.) from where its run, so I’ve left it in its own folder and and left it with its
RUNPATH enabled for finding libraries on its own:
$ cd /usr/lib64/spotify-client $ ls -l lib* -rwxr-xr-x. 1 root root 87179392 Dec 13 09:20 libcef.so -rwxr-xr-x. 1 root root 681296 Dec 13 09:20 libwidevinecdmadapter.so $ chrpath -l spotify spotify: RPATH=$ORIGIN
Instead of bundling Ubuntu’s libgcrypt library along with OpenSSL; it uses the compat-libgcrypt and compat-opensslpackages from the same repository.
The package requires FFmpeg libraries younger than 3.1 to enable playback of local files. You can install them by enabling the Multimedia repository and install
Starting from Fedora 25, the Spotify client is available for installation by default also in Gnome Software.
To install the repository on a supported Fedora 22+ distribution, run as root the following command:
dnf config-manager --add-repo=http://negativo17.org/repos/fedora-spotify.repo
To do the same on CentOS/RHEL:
Then, to install the client and its data files, perform the following command:
# yum -y install spotify-client
Spotify Connect configuration
The package includes the required service definitions for FirewallD. If you have installed a default desktop, FirewallD should be your firewall solution. To make sure that Spotify can listen on the required ports through your firewall software, execute the following commands as
According to the documentation, Spotify Connect uses TCP and UDP port 57621.
After installation of the package you should be able to see the word “spotify” by running:
firewall-cmd --get-services | grep spotify
Then get the firewall zone you are in, and enable the service for it. For example, on my system, to get the firewall zone I’m using:
# firewall-cmd --get-active-zones public interfaces: em1
Then enable it permanently (i.e. at reboot) and immediately with these commands:
firewall-cmd --zone=public --add-service=spotify --permanent firewall-cmd --zone=public --add-service=spotify
Now start up Spotify and you should see all the available devices in your network.
If you don’t have SSDP (Simple Service Discovery Protocol) already enabled on your system, you also need to enable it. Paste the following XML file in
<?xml version="1.0" encoding="utf-8"?> <service version="1"> <short>Multicast SSDP (upnp)</short> <description>Simple Service Discovery Protocol for advertisement and discovery of network services and presence information.</description> <port protocol="udp" port="1900"/> <destination ipv6="ff02::c" ipv4="22.214.171.124"/> </service>
Then run the following commands, with the same zone you have used above:
firewall-cmd --reload --quiet firewall-cmd --zone=public --add-service=ssdp --permanent firewall-cmd --zone=public --add-service=ssdp
Just open an issue to the specific package on Github.