Spotify client

spotify-client

Latest Spotify client re-packaged from the Ubuntu packages for supported Fedora and RHEL/CentOS distributions.

Supported distributions:

  • Fedora – x86_64
  • RHEL/CentOS – x86_64

This repository does not require any additional repository be enabled on your system.

Table of Contents

Package information

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/Snap and moves all files in the appropriate places. As such, the spotify binary has a RUNPATH of its origin folder. Depending on the distribution, it requires Ubuntu compatible libraries compiled with minimum options (no external dependencies) for local file playback and conversion. Due to this, I’ve removed the RUNPATH from the binary, put all the libraries in its private folder and made sure that only the spotify binary can access them.

$ cd /usr/lib64/spotify-client
$ ls -l lib*
lrwxrwxrwx. 1 root root        27 Mar  5 18:33 libavcodec-ffmpeg.so.56 -> /usr/lib64/libavcodec.so.56
lrwxrwxrwx. 1 root root        23 Oct  5  2017 libavcodec.so.53 -> libavcodec.so.53.61.100
-rwxr-xr-x. 1 root root   6990472 Oct  5  2017 libavcodec.so.53.61.100
lrwxrwxrwx. 1 root root        28 Mar  5 18:34 libavformat-ffmpeg.so.56 -> /usr/lib64/libavformat.so.56
lrwxrwxrwx. 1 root root        24 Oct  5  2017 libavformat.so.53 -> libavformat.so.53.32.100
-rwxr-xr-x. 1 root root   1194888 Oct  5  2017 libavformat.so.53.32.100
lrwxrwxrwx. 1 root root        22 Oct  5  2017 libavutil.so.51 -> libavutil.so.51.35.100
-rwxr-xr-x. 1 root root    136328 Oct  5  2017 libavutil.so.51.35.100
-rwxr-xr-x. 1 root root 127184368 Mar 23 19:16 libcef.so
lrwxrwxrwx. 1 root root        23 Apr 23 16:23 libcurl-gnutls.so.4 -> libcurl-gnutls.so.4.5.0
-rwxr-xr-x. 1 root root    591288 Apr 23 16:23 libcurl-gnutls.so.4.5.0
-rwxr-xr-x. 1 root root    372560 Mar 23 19:16 libEGL.so
-rwxr-xr-x. 1 root root   5046304 Mar 23 19:16 libGLESv2.so
lrwxrwxrwx. 1 root root        23 Oct  5  2017 libpostproc.so.52 -> libpostproc.so.52.0.100
-rwxr-xr-x. 1 root root    114104 Oct  5  2017 libpostproc.so.52.0.100
lrwxrwxrwx. 1 root root        24 Oct  5  2017 libswresample.so.0 -> libswresample.so.0.6.100
-rwxr-xr-x. 1 root root     40432 Oct  5  2017 libswresample.so.0.6.100
-rwxr-xr-x. 1 root root    444472 Apr 23 16:25 libwidevinecdmadapter.so
$ chrpath -l spotify
spotify: no rpath or runpath tag found.

Installation

To install the repository on a supported Fedora distribution, run as root the following command:

dnf config-manager --add-repo=https://negativo17.org/repos/fedora-spotify.repo

To do the same on CentOS/RHEL:

dnf config-manager --add-repo=https://negativo17.org/repos/epel-spotify.repo

Then, to install the client and its data files, perform the following command:

# yum -y install spotify-client

If your system already has an ffmpeg package, that would be used instead of the compatibility package spotify-ffmpeg. FFmpeg libraries are required for playback of local files.

Bugs

The address for contacting me is in the package’s changelog.

396 thoughts to “Spotify client”

  2. Hi, since switching from FC25 to FC27, I experience frequent “hangs” of the spotify client. Everything works quite normal, but sometimes clicks in the gui get effective after 5-20 seconds. Also the progress bar does not update as expected. Funny thing: I tried the flatpack version, same thing happens. Suggestions anyone?

    spotify-curl-7.53.1-1.fc27.x86_64
    spotify-client-1.0.69.336.g7edcc575-1.fc27.x86_64
    spotify-ffmpeg-0.10.16-3.fc27.x86_64
    spotify-openssl-1.0.0t-4.fc27.x86_64

    regards
    Jens

    Reply

    1. Found it: it’s triggered by the “Show desktop notification when the song changes” feature. Switch that off, problem gone. Maybe it helps someone with similar problems.

      Reply

    2. Can you try with the latest build? They switched from OpenSSL 1.0 to 1.1, so there is no longer a compatibility package on Fedora (there is now one on RHEL/CentOS, though).

      Reply

  3. Im installing this on pretty much new Redhat 7.2 and getting error:
    /usr/lib64/spotify-client/spotify: /lib64/libcurl.so.4: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /usr/lib64/spotify-client/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /lib64/libcurl.so.4: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /usr/lib64/spotify-client/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/spotify-client/spotify)
    /proc/self/exe: /lib64/libcurl.so.4: no version information available (required by /proc/self/exe)
    /proc/self/exe: /usr/lib64/spotify-client/libcrypto.so.1.0.0: no version information available (required by /proc/self/exe)
    [1205/143417.146756:FATAL:nss_util.cc(632)] NSS_VersionCheck(“3.26”) failed. NSS >= 3.26 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer.

    I tried recreating libcurl links but to no use, do you know what else can be done?

    Reply

  4. I have spotify of this repo on fedora 27 and I can’t input CJK words in spotify of this version.
    I use the ibus input method on the gnome desktop.

    Reply

  5. Hello,
    Gettting a segault on fedora 27 after login page?

    cat /etc/redhat-release
    Fedora release 27 (Twenty Seven)
    [aillsley@localhost .config]$ /usr/lib64/spotify-client/spotify
    /usr/lib64/spotify-client/spotify: /lib64/libcurl.so.4: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /usr/lib64/spotify-client/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /lib64/libcurl.so.4: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /usr/lib64/spotify-client/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/spotify-client/spotify)
    /proc/self/exe: /lib64/libcurl.so.4: no version information available (required by /proc/self/exe)
    /proc/self/exe: /usr/lib64/spotify-client/libcrypto.so.1.0.0: no version information available (required by /proc/self/exe)
    Segmentation fault (core dumped)

    Reply

    1. Further backtraces, maybe it is to do with SSL?

      0x00007fffeafafbc0 in ?? () from /lib64/libssl.so.1.1
      (gdb) bt
      #0 0x00007fffeafafbc0 in ?? () from /lib64/libssl.so.1.1
      #1 0x00007fffef10d42c in SSL_CTX_new ()
      from /usr/lib64/spotify-client/libssl.so.1.0.0
      #2 0x00007ffff74986b9 in ossl_connect_step1 () from /lib64/libcurl.so.4
      #3 0x00007ffff749bebf in ossl_connect_common () from /lib64/libcurl.so.4
      #4 0x00007ffff749d301 in Curl_ssl_connect_nonblocking ()
      from /lib64/libcurl.so.4
      #5 0x00007ffff744e9d2 in https_connecting () from /lib64/libcurl.so.4
      #6 0x00007ffff7461f06 in Curl_protocol_connect () from /lib64/libcurl.so.4
      #7 0x00007ffff7476866 in multi_runsingle () from /lib64/libcurl.so.4
      #8 0x00007ffff74777b4 in curl_multi_perform () from /lib64/libcurl.so.4
      #9 0x00007ffff746d69a in curl_easy_perform () from /lib64/libcurl.so.4
      #10 0x00000000015bc3a9 in ?? ()
      #11 0x00000000015bc361 in ?? ()
      #12 0x00000000015bc349 in ?? ()
      #13 0x00000000015bc229 in ?? ()
      #14 0x00000000015bc184 in ?? ()
      #15 0x00000000015bc0fd in ?? ()
      #16 0x00000000016d7db2 in ?? ()
      #17 0x00000000016d7d89 in ?? ()
      #18 0x00000000016d7d31 in ?? ()
      #19 0x00000000016d7c6c in ?? ()
      #20 0x0000000000667dc0 in boost::asio::detail::task_io_service_operation::comple—Type to continue, or q <re—Type to continue, or q to quit—
      te(boost::asio::detail::task_io_service&, boost::system::error_code const&, unsigned long) ()
      #21 0x000000000066798a in boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) ()
      #22 0x00000000006676a5 in boost::asio::detail::task_io_service::run(boost::system::error_code&) ()
      #23 0x00000000006675f6 in boost::asio::io_service::run() ()
      #24 0x00000000016d8cf5 in ?? ()
      #25 0x00000000016d8cb3 in ?? ()
      #26 0x00000000016d8c89 in ?? ()
      #27 0x00000000016d8c69 in ?? ()
      #28 0x00000000016d8bad in ?? ()
      #29 0x00007fffebeeb390 in ?? () from /lib64/libstdc++.so.6
      #30 0x00007fffeeaf5609 in start_thread () from /lib64/libpthread.so.0
      #31 0x00007fffeb94ce6f in clone () from /lib64/libc.so.6

      Reply

      1. The Spotify package is using its own SSL library in a private directory:

        $ rpm -qa spotify\*
spotify-openssl-1.0.0t-4.fc26.x86_64
spotify-ffmpeg-0.10.16-3.fc26.x86_64
spotify-client-1.0.66.478.g1296534d-1.fc26.x86_64
$ ls -al /usr/lib64/spotify-client/lib*1.0.0
-rwxr-xr-x. 1 root root 1892472 Oct  4 08:58 /usr/lib64/spotify-client/libcrypto.so.1.0.0
-rwxr-xr-x. 1 root root  406136 Oct  4 08:58 /usr/lib64/spotify-client/libssl.so.1.0.0
        Reply

        2. I modified /etc/gdm/custom.conf to boot into x11 however I am still getting a segmenation fault.

          loginctl show-session 2 -p Type
          Type=x11

          Reply

    1. Epel 20? Fedora 20? It seems to me that you added both EPEL and Fedora repository definitions to a Fedora 20 installation. Fedora 20 is EOL since forever, so no package for it.

      Reply

  9. Goodmorning, from Fedora27!
    Spotify is segfaulting:

    /usr/lib64/spotify-client/spotify: /lib64/libcurl.so.4: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /usr/lib64/spotify-client/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /lib64/libcurl.so.4: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /usr/lib64/spotify-client/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/spotify-client/spotify)
    /proc/self/exe: /lib64/libcurl.so.4: no version information available (required by /proc/self/exe)
    /proc/self/exe: /usr/lib64/spotify-client/libcrypto.so.1.0.0: no version information available (required by /proc/self/exe)
    Segmentation fault (core dumped)

    —
    okt 09 10:17:58 alux systemd-coredump[8651]: Process 8586 (spotify) of user 1000 dumped core.

    Stack trace of thread 8615:
    #0 0x00007ffb9b476bc0 n/a (libssl.so.1.1)
    #1 0x0000000000000000 n/a (n/a)

    okt 09 10:18:00 alux abrt-server[8676]: Package ‘spotify-client’ isn’t signed with proper key
    okt 09 10:18:00 alux abrt-server[8676]: ‘post-create’ on ‘/var/spool/abrt/ccpp-2017-10-09-10:17:59.181769-8586’ exited with 1
    okt 09 10:18:00 alux abrt-server[8676]: Deleting problem directory ‘/var/spool/abrt/ccpp-2017-10-09-10:17:59.181769-8586’

    Reply

  10. Hi! 🙂
    I just installed Fedora 26 Workstation, this is what happens:

    [janeahri@Jane ~]$ sudo dnf config-manager –add-repo=https://negativo17.org/repos/fedora-spotify.repo
    Adding repo from: https://negativo17.org/repos/fedora-spotify.repo
    [janeahri@Jane ~]$ sudo yum -y install spotify-client
    Last metadata expiration check: 0:00:00 ago on Wed 04 Oct 2017 11:02:58 PM WEST.
    No package spotify-client available.
    Error: Unable to find a match

    Am I doing something wrong? Or do I need to install something before?

    Thanks in advance!

    Reply

  12. Hi! first of all, thank you, a lot, you really saved us all!! Also, your blog is cool, I’m subscribing.

    I wanted to ask: is there a document I could read to learn how to de-assemble a .deb package? You say

    «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.»

    Is there somewhere I can learn more about that? I mean, I know I can just google “How to fedora rpm from ubuntu deb”, but since you already did the job with this package, maybe you have methodological recommendations or something.

    Greetings!

    Reply

  16. When I try to install, I have this message : “Failed to synchronize cache for repo ‘fedora-spotify’, désactivation.” Any idea ?

    Reply

    1. Server has been fine for a long time, no issues in the past year.
      Maybe for some reason it has been unreachable for you for a while.

      Reply

      1. Hi… seems the server is reachable but downloading is too slow, and stops after a while.

        Reply

  18. Thanks a lot. Now that the web player is useless (although it no longer uses Flash, which is its only redeeming quality) this is a godsend.

    Reply

    1. Web player still works, but you have to use a user-agent cloaker. (I use “User-Agent Switcher For Chrome”). If you go to play.spotify.com while setting the cloaker to IE10, it doesn’t redirect to open.spotify.com and you get to keep the ‘old’ working experience. It’s just a pain have to set it and then set it back. What I was hoping for coming here was some way of installing the client without root access, so that I didn’t have to do that… no joy, I guess.

      Reply

  25. I got an issue with compat-openssl, I can’t use this if I wanna play certain games, dunno if this happens with all Feral Games (devs porting games for Linux, like Mad Max and Deus EX), but AFAIK Mad Max is giving my trouble if I have compat-openssl, I need to remove it, so the game uses the other version of openssl available.

    Any words on how I can manage to keep Spotify and the game running with out removing compat-openssl? ’cause of course that deletes Spotify.

    Reply

    1. Will look into it. I guess I need to modify it somehow and skip it from the library paths or Steam games will use that.

      Reply

        3. I completely forgot about this as there was no issue open. Can you try again with the updates that I just pushed? It contains also a specific libcurl version.

          Reply

    2. Hello, I’ve made the OpenSSL 1.0.0t compatibility library a private library in Spotify’s own folder that the client then loads through its run path. There should be no more issues of Steam games compiled for the Ubuntu Runtime loading my custom library. It will be online in a few minutes.

      Reply

    1. I had this same problem, but I found a work-around to get to settings by going to the “Local Files” section on the left under “Your Music” then “Go to Preferences” in the middle of the screen. I don’t know what’s causing it but at least there is a work-around.

      Reply

  28. hello,these steps could help you all.
    — Open spotify
    –Click Log in with facebook
    –I had to open one more tab with facebook in it obviously already logged, try it until you get the message “you can close this window”
    –After because the spotify’s window will not go in, close the window and open again spotify.

    Linux, Fedora 25, spotify-client

    Reply

    1. Fixed the problem for me too. Thanks for taking the time to write down the solution 🙂
      I hope negativo17 won’t struggle to fix it (Great work by the way!)

      Reply

        1. I’m using your latest version, downloaded today (spotify-client-1.0-5.fc25.x86_64.rpm) but the problem persist.

          Reply

    1. Same setup as here (X + binary drivers on Fedora 25), but sorry it doesn’t happen. Unfortunately the client is a horrible binary blob with no chance for me to do anything.
      I guess there is something wrong when the client starts fresh (i.e. no previous configuration) on Fedora 25.

      Reply

        1. Ok, searching in internet I found this error depends by spotify client version 1.0.45.182.
          With previous version 1.0.44.100 it’s all ok.

          Problems appears with a fresh spotify client installation and not with an upgrade from an older version.

          So, can you rebuild a package with 1.0.44.100 stable version so we can upgrade later to 1.0.45.182?
          Or we can waiting for a new version that fix this problem?

          Thanks

          Reply

  33. Hi,
    Try to install spotify-client in my fresh Fedora 25 Workstation. Launch spotify open login page, but when i try to login it crash!
    This is the output in the terminal:
    [code]
    spotify: /lib64/libssl.so.1.0.0: no version information available (required by spotify)
    spotify: /lib64/libcrypto.so.1.0.0: no version information available (required by spotify)
    spotify: /lib64/libcurl.so.4: no version information available (required by spotify)
    /usr/lib64/spotify-client/spotify: /lib64/libssl.so.1.0.0: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /lib64/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /lib64/libcurl.so.4: no version information available (required by /usr/lib64/spotify-client/spotify)
    [1218/104331:ERROR:main_delegate.cc(752)] Could not load cef_extensions.pak
    /proc/self/exe: /lib64/libssl.so.1.0.0: no version information available (required by /proc/self/exe)
    /proc/self/exe: /lib64/libcrypto.so.1.0.0: no version information available (required by /proc/self/exe)
    /proc/self/exe: /lib64/libcurl.so.4: no version information available (required by /proc/self/exe)
    [1218/104331:ERROR:main_delegate.cc(752)] Could not load cef_extensions.pak
    [1218/104334:ERROR:PlatformKeyboardEvent.cpp(94)] Not implemented reached in static bool blink::PlatformKeyboardEvent::currentCapsLockState()
    Segmentation fault (core dumped)
    [/code]

    Reply

  34. On fresh Fedora 25 (running Wayland), I get a crash right after logging in:

    `
    spotify: /lib64/libssl.so.1.0.0: no version information available (required by spotify)
    spotify: /lib64/libcrypto.so.1.0.0: no version information available (required by spotify)
    spotify: /lib64/libcurl.so.4: no version information available (required by spotify)
    /usr/lib64/spotify-client/spotify: /lib64/libssl.so.1.0.0: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /lib64/libcrypto.so.1.0.0: no version information available (required by /usr/lib64/spotify-client/spotify)
    /usr/lib64/spotify-client/spotify: /lib64/libcurl.so.4: no version information available (required by /usr/lib64/spotify-client/spotify)
    [1216/113255:ERROR:main_delegate.cc(752)] Could not load cef_extensions.pak
    /proc/self/exe: /lib64/libssl.so.1.0.0: no version information available (required by /proc/self/exe)
    /proc/self/exe: /lib64/libcrypto.so.1.0.0: no version information available (required by /proc/self/exe)
    /proc/self/exe: /lib64/libcurl.so.4: no version information available (required by /proc/self/exe)
    [1216/113255:ERROR:main_delegate.cc(752)] Could not load cef_extensions.pak
    [1216/113303:ERROR:PlatformKeyboardEvent.cpp(94)] Not implemented reached in static bool blink::PlatformKeyboardEvent::currentCapsLockState()
    [1216/113304:ERROR:PlatformKeyboardEvent.cpp(94)] Not implemented reached in static bool blink::PlatformKeyboardEvent::currentCapsLockState()
    [1] 4254 segmentation fault (core dumped) spotify
    `

    Reply

    1. You should probably raise the flag upstream, I’m just repackaging the binaries. The Spotify client is horrible; I don’t think that suppports Wayland (running X on Fedora 25 here).

      Reply

      2. Actually this does not seem related to Wayland. I’m also using Fedora 25 with Wayland and I have it working properly using spotify-client@1:1.0-3.fc25. I was configuring another machine today and noticed the newer version (1:1.0-4.fc25) doesn’t work anymore (even on X).

        Are older versions from negativo repo still available somewhere? I can only see the latest one here – http://negativo17.org/repos/spotify/fedora-25/x86_64/

        Reply

    2. I am having the same issue with Fedroa 25 Workstation x86_64 fresh install. Crashes after login with the error descripted on previous message.

      Reply

  35. Menu towards the top right of the screen is clickable, but its options don’t work (Private session, Account, Settings, Logout). I tried pkcon refresh force and reboot, but these buttons still do nothing for me.

    Reply

    1. pkcon refresh is for refreshing the software lists in Gnome software, it has nothing to do with the Spotify client.

      The last version of the client seems to have problems, they released again a minor update (1.0.43.125) but haven’t tried it yet. Will build it when I have a bit more time.
      The client is a binary blob, if things don’t work inside the client there’s not much I can do, you should open a bug to Spotify.

      Reply

  36. Somehow the newer versions of Spotify don’t discover Spotify Connect devices on my network. The devices make themselves visible through avahi. They are only visible when they are linked to the same Spotify account, but before it worked just fine through automatic discovery. Any idea what could be causing this? A missing dependency, or just some regression at Spotify’s side? Sadly I can’t point to a specific version that still worked for me. Other devices can see the Spotify Connect devices just fine.

    Reply

    1. Sadly there’s no changelog with the Spotify. They’ve released a new different build today for x86_64, will update to that, maybe it’s fixed.

      Reply

  37. Comments from a fresh F25 installation. Seems to be a bit rough around the edges in comparison to the version I used for my F24 fresh install.

    Minor inconveniences I see:
    – Login in with facebook crashes the app. Have to type in login credentials.
    – The menu settings dont do anything if you click on them, ie. account | settings | logout

    Other than that the app is running fine. Thank you for providing this HOW TO!

    Question, your blog says in F25 it should show by default on Gnome Software. That was not the case for me, eventhough I selected to add the propietary repository in the gnome welcome menu. Did I miss anything?

    Reply

  38. Weird, I’m using Fedora 25 and I’ve already added the repo, but I can’t find Spotify anywhere in the Gnome Software Center.

    However, manually installing it with dnf seems to work fine.
    Is anything wrong with my installation?

    Reply

  39. Hi!
    I have noticed that my viber (http://www.viber.com/en/) seems to be conflicting with compat-openssl which goes with spotify-client. Viber starts consuming 300% CPU and doesn’t send images, etc.
    After compat-openssl removal viber starts working properly. Are there any suggestions?

    Reply

      2. I can be wrong but I suppose it’s a viber issue because as i understand it shouln’t use this compat lib. Created a ticket to their support but no result so far.
        Still if anybody knows a workaround I would appreciate.

        Reply

      3. Hello, I’ve made the OpenSSL 1.0.0t compatibility library a private library in Spotify’s own folder that the client then loads through its run path. There should be no more issues of Steam games compiled for the Ubuntu Runtime loading my custom library. It will be online in a few minutes.

        Reply

    2. Hello, I’ve made the OpenSSL 1.0.0t compatibility library a private library in Spotify’s own folder that the client then loads through its run path. There should be no more issues of other programs loading the library. It will be online in a few minutes.

      Reply

  40. please, for what are reason are you always providing the ‘yum’ (deprecated) command instead of ‘dnf’. It might create confusion in my opiniom

    Reply

  41. Today’s update is trying to install compat-openssl, but it’s conflicting with openssl package already installed on Fedora 23! Halp!

    Reply

    1. Can you paste the output here? I’m not seeing how it could conflict with OpenSSL 1.0.2 and its shared libraries versions’.

      Reply

      1. I actually upgraded to F24 and removed the openssl1 package, so now everything’s okay. But, from what I remember, it was having file conflicts (lib64/libcrypto.so.1.0.0 and lib64/libssl.so.1.0.0).

        Reply

        1. I don’t ship a package called openssl1; neither Fedora nor RPMFusion. I’ve seen that it comes from the postinstaller RPMs on Sourceforge.

          Reply

          1. Puede borrar los paquetes de la caché ejecutando ‘dnf clean packages’.
            Error: Transaction check error:
            el archivo /usr/lib64/libcrypto.so.1.0.0 de la instalación de compat-openssl-1.0.0t-1.fc23.x86_64 entra en conflicto con el archivo del paquete openssl1-1.0.0-3.fc23.x86_64
            el archivo /usr/lib64/libssl.so.1.0.0 de la instalación de compat-openssl-1.0.0t-1.fc23.x86_64 entra en conflicto con el archivo del paquete openssl1-1.0.0-3.fc23.x86_64

          2. Don’t know if you’ve noticed, but everyone here writes in english.
            Just remove the package openssl1. I’m guaranteeing compatibility with Fedora and RPMFusion repositories, not everything that’s around.

  42. hello friends! i am trying to listen to local M4A’s using spotify, but it either crashes or does nothing when trying to play one; any suggestions ? (already installed ffmpeg-libs)

    Reply

  44. This is awesome, thanks for maintaining this!

    Is there a way to install spotify locally, as I don’t have sufficient permissions to dnf config-manager –add-repo, or even to dnf –enable-repo?

    Reply

    1. Really? Then the package is not very useful. Try to unpack it, create a script and set the appropriate library paths before starting it.

      Reply

  45. In Fedora 24, I had to remove xterm -e “wget …” and execute wget directly in shell, because it wasn’t working otherwise

    Reply

      1. Hello, I don’t understand. The path you specified is a link to a binary. What are you referring to?

        $ ls -al /usr/bin/spotify 
lrwxrwxrwx. 1 root root 33 Jun  9 12:07 /usr/bin/spotify -> /usr/lib64/spotify-client/spotify
$ file /usr/lib64/spotify-client/spotify
/usr/lib64/spotify-client/spotify: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=8aba5fb1191078be1e87a1a5e2e8657c3c962271, stripped
        Reply

  47. Hey, so i tried to install it, and it gives me the following:

    Error: nothing provides ffmpeg-libs needed by spotify-client-1.0.28.89.gf959d4ce-1.fc23.x86_64

    Many thanks,

    Reply

  48. A big thanks for your work, it’s great to see that some people care about distributing all these closed-source apps to RedHat users as well!

    Reply

  49. It seems there is a new version on the testing repository:

    1.0.27.71.g0a26e3b2-9

    Spotify devs claim it fixes MPRIS2. Anyone tried it yet on Fedora?

    Reply

Leave a Reply