Version: 2.1.1 (using KDE 4.3.0) OS: Linux Installed from: Debian testing/unstable Packages When it starts playing or stops/pauses, Amarok doesn't send the correct MPRIS signals: when it passes from stop to play, it sends (2,0,0,0) and then immediately (0,0,0,0) (the digits other then the first may differ according to Repeat and Random settings) when it passes from play to stop, it sends (0,0,0,0) twice when it passes from pause to stop, it sends (1,0,0,0) twice when it passes from play to pause, it does the right thing, sending once (1,0,0,0) I didn't check if there is the same problem with the digits corresponding repeat and random settings, but I noticed that amarok doesn't send the signal on random setting changes. Amarok should send one single signal on every status change, with the tuple corresponding to its new status.
*** This bug has been marked as a duplicate of bug 206028 ***
Sorry, I fail to see how the two bugs are related. The original bug is about D-Bus methods, mine is about the signals amarok sends. I took a look at your commit and I think it's completely irrelevant to the bug
I've also noticed that at song change, after the StatusChange signal has been sent, the PositionGet method still returns the old song was at, not the new one (i.e. 0) This seems related: the StatusChange is sent before the new information has been set for the MPIRS method to return.
Is this still valid for Amarok 2.2.1 or 2.2-git?
Closing for lack of feedback. Please only reopen this report if you can reproduce it with Amarok 2.2.2 final, to be released later this week.