Bug 206660

Summary:	D-bus StatusChange signal reports status
Product:	[Applications] amarok	Reporter:	ciro.scognamiglio
Component:	general	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	2.1.1
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:

Description ciro.scognamiglio 2009-09-07 20:05:56 UTC

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.

Comment 1 Myriam Schweingruber 2009-09-07 20:16:41 UTC


*** This bug has been marked as a duplicate of bug 206028 ***

Comment 2 ciro.scognamiglio 2009-09-07 20:39:58 UTC

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

Comment 3 ciro.scognamiglio 2009-09-07 22:29:20 UTC

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.

Comment 4 Myriam Schweingruber 2009-12-08 11:59:46 UTC

Is this still valid for Amarok 2.2.1 or 2.2-git?

Comment 5 Myriam Schweingruber 2010-01-05 00:49:15 UTC

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.