When using Spotify client, the media player plasmoid shows correctly the name of the track currently beeing played. But clicking on any button in it makes no effect. Moreover sometimes either the play/pause icon displayed on the tray or the one inside the plasmoid is incorrect (play when paused or vice-versa). Reproducible: Always Steps to Reproduce: 1. Open the plasmoid when Spotify client is open. 2. Click on any button. 3. Actual Results: Nothing happens. Expected Results: Spotify client and the plasmoid should both act according to the action.
Works here (Plasma 5.4) Spotify 0.9.17.8 What Spotify version?
Should be the one provided in Arch Linux AUR repository (https://aur.archlinux.org/packages/spotify/), so 0.9.17.8. Will confirm tomorrow as I am now in another machine.
Today I tried again. This time the play/pause and the track change buttons seemed to work. The progress bar above them instead was not working correctly, it just moved forward whatever its prior position when the music was playing, and clicking on it just moved that progress bar without affecting the reproduction. I confirm Spotify version to be 0.9.17.8.
Another update after other tentatives. The bug I originally described only happens sometimes, when it happens the progress bar in the plasmoid is NOT shown. Closing and reopening Spotify sometimes fixes it (except for the progress bar which behaves like in my last comment).
It look like it does not work anymore with Spotify version 1.0.17.75.g8f111100. But not sure to understand why. I have seen and be able to use mdbus2 in order to command spotify: http://www.frandieguez.com/blog/2010/11/playing-with-d-bus-interface-of-spotify-for-linux/ https://community.spotify.com/t5/Spotify-Announcements/Spotify-beta-1-0-13-for-Linux-released/td-p/1197675 They talk about it here: https://community.spotify.com/t5/Spotify-Community-Blog/Spotify-beta-1-0-13-for-Linux-released/ba-p/1197675/page/2#comments
I have the same problem, but Plasma reacts to Spotify loading the mediacontroller applet, but then it fails with: [mpris.cpp:137] Unrecognized or unimplemented MPRIS MediaPlayer2 method 'GetAll' plasma.engine.mpris2: "org.mpris.MediaPlayer2.spotify" does not implement org.freedesktop.DBus.Properties correctly plasma.engine.mpris2: Error message was "org.freedesktop.DBus.Error.InvalidArgs" "Non existe a interface" (interface does not exist) plasma.engine.mpris2: Failed to find working MPRIS2 interface for "org.mpris.MediaPlayer2.spotify" The "GetAll" method returns nothing at all, tested in QDBusViewer. I assume this is a Spotify bug, it used to work perfectly some versions ago.
This isn't working in plasma 5.5.4 with spotify 1.0.23.93 (Kubuntu + backports). It auto loads the applet but says "No media playing".
Linux Spotify is somewhat known to be broken, here's nice summary about why: http://www.omgubuntu.co.uk/2016/03/spotify-linux-no-development
*Linux Spotify's MPRIS, I meant.
You can talk about it here: https://community.spotify.com/t5/Help-Desktop-Linux-Windows-Web/Linux-Spotify-client-1-x-now-in-stable/td-p/1300404/page/4
Can you try the latest version of Spotify? Upgrading fixed the problem for me. I couldn't control Spotify when it was at version 1.0.25.127.g58007b4c-22, but everything was fine after upgrading to 1.0.28.89.gf959d4ce-37. FYI: I am using the Debian package from Spotify's APT repository.
I installed version 1.0.33.106 (latest right now at AUR). It works.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!