Comment 12 for bug 515253

It looks like what's happening here is that Exaile still misreports its playback status when starting to play a radio stream. Panflute trunk tries to account for this by ignoring the status that Exaile says in its StatusChange signal and calling GetStatus, which ordinarily returns the correct information. I say ordinarily, because it seems there's a time window when it too is wrong, so Panflute is now convinced that Exaile isn't playing. When you hit the Play button, Panflute tells Exaile to start playing the stream anew; the "pause" is actually Exaile stopping the stream and re-starting it. Then the same problem occurs, and Panflute still thinks Exaile is stopped, because Exaile still reports the wrong information.

If you pause and unpause the stream in Exaile first, though, then the workaround currently in Panflute trunk works, which was why I was having problems reproducing this behavior.

I'm going to hope that using Exaile's native D-Bus interface instead of MPRIS reports correct status information and use that for the workaround instead. If not, the alternative is an ugly ask-Exaile-for-its-status-again-in-a-couple-seconds hack.