Today we've released Spotify client version 1.0.11 for Linux. There are some big changes in this version, and it's still considered to be a beta release, and will be in beta until the items in the "known issues" list below are resolved. If you want to try out this version, installation instructions remain the same as for the other betas:
or if you have a previous version installed, simply:
sudo apt-get upgrade
Since the previous public release (version 1.0.9), we've made the following Linux-specific changes:
32-bit binaries are now available! Now users on i386 systems can try out the 1.x betas as well. Please reply to this thread with any technical problems that you encounter on that architecture.
libnotify is now an suggested package dependency. If you don't have that library installed, this feature will simply be unavailable.
Updated application icon in the spotify.desktop entry
GPU acceleration is disabled (see below)
This build ships with the following limitations, of which we are still currently working on:
Proper dbus support for MPRIS MediaPlayer2
There is no application menu
It is not possible to re-enable GPU acceleration through the settings
Important: regarding GPU acceleration, this is now completely disabled in the client, and we do not yet have a way to enable it in the preferences. This change was originally made in Chromium for Linux, but since the Spotify client uses CEF, we inherited this change from them. According to the Launchpad bug report, faulty GPU driver support was the single largest cause of crashes for Chromium on Linux (this graph shows how Chromium crashes on Linux have dramatically decreased after the setting was changed).
Depending on your hardware and GPU drivers, this change is either going to be a big annoyance for you or a huge blessing. For our users who experienced frequent and strange crashes with the client, this change will probably greatly increase client stability. For other users with certain video cards, scrolling performance and redraw rates may be noticeably choppier. Some users won't notice anything at all.
The obvious solution here is that our Linux client needs a toggle to manually re-enable this feature in the settings. Exposing this feature is not as straightforward as you might believe, or else we would have done it already. 😉 However, we're working on a way to do just that, and hopefully will have something in place for the next beta release.