Bug 170054

Summary: (MPRIS) TrackChange signal passes wrong values when pushing play button
Product: [Applications] amarok Reporter: Mazhe <vmazhe>
Component: Tools/Script ManagerAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED FIXED    
Severity: normal CC: peterzhoulei
Priority: NOR    
Version: 2.0-beta   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description Mazhe 2008-08-29 21:33:57 UTC 
Version:           2.0-beta1 (using KDE 4.1.0)
Compiler:          gcc 4.1.2 (Gentoo 4.1.2 p1.0.2) Target: x86_64-pc-linux-gnu
OS:                Linux
Installed from:    Compiled From Sources

Amarok does not return correct values in MPRIS-defined signal StatusChange (see http://wiki.xmms2.xmms.se/wiki/MPRIS#.2FPlayer_object_signals for a description of those signals) when the interface play/pause/stop/next/prev buttons are used.

Here is an example of what is happening :
0. The player is stopped
1. The "play" button is pushed -> the signal StatusChange is called but carry the values (2xxx) where xxx correctly reflects the lasts integers but the first (2) tells dbus listener that the player is stopped. (note that the same thing is happening in fact when double-cliking an element of the playlist)
2. The "pause" button is pushed -> the status is correctly sent.
3. The "play" button is pushed -> no signal (should send one carrying values (0xxx)).
4. The "next"/"previous button is pushed, the status is correctly sent

The signal is also correctly sent when amarok is jumping to anthoer track once the current is finished.
Comment 1 Mazhe 2008-09-08 20:40:08 UTC 
Upgraded to rev 858723, I noticed that now pushing previous/next buttons now sends the right status signal. I don't know if this report helped, but I'm still happy to see this, there is only the play/pause signal to correct now.
Comment 2 Mark Kretschmann 2008-10-20 11:55:06 UTC 
I think this was fixed recently in SVN. If it's not fixed, please feel free to reopen the report.