FWIW, this one is a big deal for me. That system tray icon is how I control spotify 99% of the time. I don't typically want or need a window open for my music player. Just updated to 126.96.36.199.gd6cfae15 this morning & was greeted with what I consider a regression. What's it take to get something proritized?
Not that much. Enough people complaining about it, like you just did here. Considered it prioritized. The problem is more that nobody is working on linux specific features, so even though I have now added it to our internal bug tracker of things to fix, nobody is going through that list. When that happens, someone will eventually get to it.
Meanwhile, I saw this post on stackoverflow about this issue. Spotify does not have icon on systray in Ubuntu 14.04 Since it is not really a programming question, it's more like a power user answer, it will probably be deleted from stackoverflow, so I will quote it here for reference:
Today the Spotify was updated and its icon disappear on systray on ubuntu 14.04. I used to use this icon to play and stop the musics.
I modified the spotify.desktop and put some entries to control the music using the own spotify icon.
To edit the spotify.desktop, you need to run the following command:
What? They are making money off it so they have to show some respect to users and hire some guy(s). At least, until the program is more useful. They are making million dollars but can not hire a Linux guy(s). Shame on you Spotify!
Well, thanks for the update, but like others have pointed out this is very worrying. Five months it's too much time to be vulnerable to bugs and security fails that may exist. Others small company’s, such as Vivaldi and pCloud, have updated Linux versions of their apps, so I don't understand why Spotify, receiving huge investments every year, can't do this. I hope something change about this.
Spotify Premium user here. Rapidly losing patience, though! On Ubuntu Precise (12.04) 32-bit the 1:188.8.131.52.gd6cfae15-5 client won't install due to an unmet libudev1 dependency. There is a symlink hack you can use to get around it that's existed since the beta, but it's yet another problem in addition to all the others reported in this thread. Yeah, I know there are only 10 of us on Linux, management obviously doesn't care, etc.. Thanks for your efforts, at least, Jooon...