Spotify 0.9.11 for GNU/Linux

[parbo]

Hi, fellow penguin fans!

Today we've pushed version 0.9.11.26 of the Linux desktop client to our public repo. Just update your system!

General release notes: http://community.spotify.com/t5/Help-Desktop-Linux-Mac-and/Release-Notes-Spotify-for-Desktop-0-9-11/...

Linux specific changes:

 - collectionCache.bnk is no longer written to $HOME

Known issues:

 - It still doesn't work to drag from an HTML5 view to a legacy view (such as the sidebar).

 - On first start, the HTML5 views may not appear (just empty black views), try restarting the app if it happens

 - Some users have reported problems with the new track change notifications. If you experience problems, you can start the client with "spotify --ui.track_notifications_enabled=false", or you can edit the file called ~/.config/spotify/Users/<your-spotify-username>-user/prefs and add a line with "ui.track_notifications_enabled=false". Sorry for not having this option available in the UI.

 - No 32-bit build is available

 - This build is not compatible with debian squeeze or wheezy

If you don't already have the Linux client installed, install like this:

# 1. Add our repository. As root or with sudo, create
#    a file called /etc/apt/sources.list.d/spotify.list and add
#    "deb http://repository.spotify.com/stable non-free" to it.
#    Here's a one-liner:
sudo sh -c 'echo "deb http://repository.spotify.com/stable non-free" > /etc/apt/sources.list.d/spotify.list'
 
# 2. If you want to verify the downloaded packages,
#    you will need to add our public key
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 94558F59
 
# 3. Run apt-get update
sudo apt-get update
 
# 4. Install spotify!
sudo apt-get install spotify-client
 
You don't have a debian based system? Well, it's still possible to get things running. Either you convert the debian package to something else using alien, or you can just download and extract the stuff you need from the package. There is no need to install the client, it can be run from anywhere.
 
# 1. Get the right filename
SPOTIFY_DEB=http://repository-origin.spotify.com/pool/non-free/s/spotify/spotify-client_0.9.11.26.g995ec04.78-1_`uname -m | sed s/x86_64/amd64/ | sed s/i686/i386/`.deb
 
# 2. Download the package
wget repository.spotify.com/pool/non-free/s/spotify/$SPOTIFY_DEB
 
# 3. Extract the required parts
ar p $SPOTIFY_DEB data.tar.gz | tar -zx --strip-components=3 ./opt/spotify/spotify-client
 
# 4. Go in to the extracted folder
cd spotify-client
 
# 5. Setup symlinks to libs (NOTE: this script assumes Fedora 17, edit to suit your needs)
./linklibs-fedora.sh
 
# 6. Optionally register icons and menu item
#    Note: for the menu item to work, you need to ensure
#    spotify is in your $PATH, either by symlinking
#    it from /usr/bin or /usr/local/bin, or by adding
#    the spotify-client folder to your $PATH
./register.sh
 

[sleeksorrow]

---

@olejon wrote:
@parbo: Great with such a fast update for Linux users. However, I wish the client would report metadata through D-Bus/MPRIS even if one disables desktop notifications. In the 0.9.10 thread you (developers) said that this was a mistake, so I was hoping for a fix.

---

Indeed that's a bit disappointing, after the reply in the 9.10 thread sounded like it was some small glitch... Combined with the fact, that the built-in notification still is quite senseless (it does not show artist info? lolwut?) that's kind of sad. It causes that I cannot replace it with own notification code based on dbus, because that would mean I get double notifications.

[user-removed]

It is written in Qt, so it isn't that difficult to create a client for the platform, especially if the devs are Linux geeks, too 😄 I'm sure there are one or two people who are dealing with all the gotchas that would claim that it isn't as easy as people think, though, hah.  I can relate.

Spoiler

>> ldd /usr/bin/spotify
        linux-vdso.so.1 =>  (0x00007fff7fffe000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007ff9bd08e000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ff9bce70000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007ff9bcc67000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ff9bc961000)
        libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007ff9bc659000)
        libgthread-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x00007ff9bc456000)
        libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x00007ff9bb7a3000)
        libQtDBus.so.4 => /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 (0x00007ff9bb528000)
        libQtXml.so.4 => /usr/lib/x86_64-linux-gnu/libQtXml.so.4 (0x00007ff9bb2e2000)
        libQtNetwork.so.4 => /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 (0x00007ff9baf9a000)
        libQtCore.so.4 => /usr/lib/x86_64-linux-gnu/libQtCore.so.4 (0x00007ff9baab5000)
        libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007ff9ba811000)
        libgtk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 (0x00007ff9ba1d5000)
        libgdk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 (0x00007ff9b9f23000)
        libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x00007ff9b9c17000)
        libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x00007ff9b99ca000)
        libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007ff9b97bd000)
        libpangoft2-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x00007ff9b95a7000)
        libpangoxft-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangoxft-1.0.so.0 (0x00007ff9b939e000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x00007ff9b917d000)
        libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007ff9b8f78000)
        libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007ff9b8c05000)
        libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x00007ff9b89e3000)
        libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007ff9b8791000)
        libcef.so => not found
        libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007ff9b8533000)
        libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007ff9b8158000)
        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007ff9b7f3d000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ff9b7d39000)
        libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 (0x00007ff9b7a48000)
        libXss.so.1 => /usr/lib/x86_64-linux-gnu/libXss.so.1 (0x00007ff9b7844000)
        libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007ff9b750f000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007ff9b72f8000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff9b6f32000)
        /lib64/ld-linux-x86-64.so.2 (0x00007ff9bd3c1000)
        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007ff9b6cf4000)
        libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007ff9b6ab7000)
        libaudio.so.2 => /usr/lib/x86_64-linux-gnu/libaudio.so.2 (0x00007ff9b689f000)
        libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 (0x00007ff9b6679000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007ff9b645f000)
        libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x00007ff9b6257000)
        libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x00007ff9b603b000)
        libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007ff9b5e2a000)
        libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007ff9b5c20000)
        libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007ff9b5a0e000)
        libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007ff9b57c8000)
        libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007ff9b55c2000)
        libXinerama.so.1 => /usr/lib/x86_64-linux-gnu/libXinerama.so.1 (0x00007ff9b53be000)
        libXrandr.so.2 => /usr/lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007ff9b51b4000)
        libXcursor.so.1 => /usr/lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007ff9b4faa000)
        libXcomposite.so.1 => /usr/lib/x86_64-linux-gnu/libXcomposite.so.1 (0x00007ff9b4da6000)
        libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007ff9b4ba3000)
        libpixman-1.so.0 => /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x00007ff9b48f9000)
        libxcb-shm.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007ff9b46f6000)
        libxcb-render.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007ff9b44ed000)
        libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007ff9b42cd000)
        libthai.so.0 => /usr/lib/x86_64-linux-gnu/libthai.so.0 (0x00007ff9b40c4000)
        libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007ff9b3e6e000)
        libXft.so.2 => /usr/lib/x86_64-linux-gnu/libXft.so.2 (0x00007ff9b3c59000)
        libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007ff9b3a35000)
        libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007ff9b382d000)
        libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007ff9b3602000)
        libXt.so.6 => /usr/lib/x86_64-linux-gnu/libXt.so.6 (0x00007ff9b339c000)
        libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007ff9b3198000)
        libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007ff9b2f92000)
        libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007ff9b2d8c000)
        libdatrie.so.1 => /usr/lib/x86_64-linux-gnu/libdatrie.so.1 (0x00007ff9b2b84000)
        libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 (0x00007ff9b2968000)

[heavyheaded]

The main repository is throwing errors on "apt-get update" again as of 2014-07-07 11:30 AM CDT. The alternate repository "http://repository-origin.spotify.com" is working in its stead.

[devnill]

No dice. I'm still getting 403's on both repos. Is there a direct link?

[laptaper]

You might have to delete the repositories from your software sources list, do sudo apt-get update, then go to https://www.spotify.com/us/download/previews/ and follow the directions to add the repository back in.  Worked on my end.

[Klap-in]

At askubuntu.com an employee of Spotify tells the issue is fixed.

See http://askubuntu.com/a/491607

Solution is removing the file that contains HTML

for example for the English localisation:

sudo rm /var/lib/apt/lists/repository.spotify.com_dists_stable_non-free_i18n_Translation-en%5fUS

 But the language code at the end will differ when you use another system language.

[Schw4rz]

The Linux client is superb! Works smootly on Debian 7.5 with Gnome Desktop. No problems so far. 

[n3rdXcore]

I can't get Spotify to upgrade from 0.9.10.17.g4129e1c9 to 9.11 on Ubuntu 12.04 LTS (64-bit). I'm a total Linux / Ubuntu newbie (I have to use it at work), so please bear with me if any of this stuff is super inaccurate.

I installed Spotify about six weeks ago using these instructions:

# 1. Add this line to your list of repositories by editing your /etc/apt/sources.list
deb http://repository.spotify.com stable non-free
# 2. If you want to verify the downloaded packages, you will need to add our public key
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 94558F59
# 3. Run apt-get update
sudo apt-get update
# 4. Install spotify!
sudo apt-get install spotify-client

Then I tried to update today using the instructions in this thread:

#Step 1

sudo sh -c 'echo "deb http://repository.spotify.com/stable non-free" > /etc/apt/sources.list.d/spotify.list'

#Step 2

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 94558F59

#Step 3

sudo apt-get update

That returned some errors:

E: Malformed line 1 in source list /etc/apt/sources.list.d/spotify.list (dist parse)
E: The list of sources could not be read.

So I followed rannyakuza's steps to fix it:

As a workaround, place the following in /etc/apt/sources.list.d/spotify.list:
deb http://repository-origin.spotify.com stable non-free

That still returned the same errors, so I tried his fix in reply 22:

Clear your cached lists: sudo rm /var/lib/apt/lists/* -vf

The same errors are still popping up. Does anyone have any idea how to fix this? Additionally, about a week ago the right-hand social pane disappeared from my Spotify client, and that's one of my favorite features. 😞

[user-removed]

Well, after update I noted a annoying problem affecting Spotify. The thing is that in my system the cursor gets sometimes stuck and moves but it's impossible to click anywhere (nothing happens). This situation only happens when I'm using Spotify. To fix I always have to restart or log out.

It started to happen after upgrade and in another system that I have, using 32 bits (so an older version of the app) It does not happen. Anyone else having something similar?

Using Xubuntu 14.04 64 bits. 

[laptaper]

I've found that instantly resolved simply by minimizing the window and then remaximizing it.  It sometimes happens several times a session, though, and it IS very annoying.

[user-removed]

Thanks laptaper, it works. I hope someone take a look at this. 

[BNo1]

That is my main annoyance, happens when using Spotify client everything comes unresponsive except mouse cursor.

I hope this issue is getting fixed soon.

Ubuntu 12.04 64bit

[Peter__]

I think this is this legacy issue:
http://community.spotify.com/t5/Help-Desktop-Linux-Mac-and/Spotify-Linux-Preview-hijacks-mouse-click...

Pressing Alt+F4 then reopening might work?

[andresmoreira]

Hi guys, 

Do you know if there is a way, using Spotify on Linux, to get the current streaming bit rate of a song?

Thanks, 

 Andrés

[sleeksorrow]

---

@andresmoreira wrote:

Do you know if there is a way, using Spotify on Linux, to get the current streaming bit rate of a song?

---

https://support.spotify.com/us/learn-more/faq/#!/article/What-bitrate-does-Spotify-use-for-streaming

[andresmoreira]

Thanks, besides that document. I want to know if the *app* has the availability to output the bitrate of the song (as many players does). 

Andrés

[sleeksorrow]

---

@andresmoreira wrote:

Thanks, besides that document. I want to know if the *app* has the availability to output the bitrate of the song (as many players does). 

---

Could you please elaborate on your question? What's the goal you want to achieve?

You know the bitrate already. If you enabled high quality, then it's 320kbit/s. Always. No change. Static. If you disable high quality, it's 160kbit/s. As before: Won't change. You could make a screen backdrop showing the bitrate if you like. 😉

[andresmoreira]

Besides I did know because Spotify stated in their page, I was intrested in check some tracks I listened to if they are in 320, to compare against ones I have in ogg 320 too and they sound difference (same album). 

In Windows it is possible to be know: http://community.spotify.com/t5/Newcomers-and-Contribution/Guide-How-to-see-a-bitrate-in-Spotify/td-... but in Linux that option doesn't work.

It shouldn't difficult to log it, because of that I'm just wondering, maybe there is some hide option.

[djxvillain]

Thank you so much for the much needed Linux update.  Really.

[sleeksorrow]

---

@andresmoreira wrote:

In Windows it is possible to be know: http://community.spotify.com/t5/Newcomers-and-Contribution/Guide-How-to-see-a-bitrate-in-Spotify/td-... but in Linux that option doesn't work. 

---

Okay, I see from the screenshots that it seems to be shown on Windows and I verified that it's not shown on Linux. 

Nevertheless I doubt that you are hunting for the correct way to reach your goal.

If you hear differences in quality of spotify songs, that will most probably not be a result of lower bitrate, but a lack in quality of the original material. Perhaps it helps if you imagine this issue in another context. Let's take Bitmap images with JPEG compression.

If you have a high quality image like from a modern DSLR camera and you have a high JPEG quality, it will look great. If you use a low JPEG quality it will be very small, but has ugly artefacts.

If you have an image made with a very old smartphone, blurred, out of focus and noisy, you can set the JPEG quality as high as you want, it will be always have crappy quality.

So back to spotify: Be assured, the bitrate of the material you get is always the one that you set in your preferences. Looking at a static bitrate number would not help you finding a reason for low quality tracks.