Skip to content
This repository has been archived by the owner on Dec 7, 2020. It is now read-only.

Stop doesn't change Mopidy state #77

Closed
morgoth opened this issue Mar 31, 2015 · 2 comments
Closed

Stop doesn't change Mopidy state #77

morgoth opened this issue Mar 31, 2015 · 2 comments
Assignees
Labels
C-bug Category: This is a bug
Milestone

Comments

@morgoth
Copy link

morgoth commented Mar 31, 2015

When using "stop" on gmusic song, Mopidy is still in "playing" state.
There is no music, as it somehow stopped playing, but the state is invalid.
I have no such issue when stopping song from local backend.
For the background how I found this issue you can see mopidy/mopidy.js#5

@jodal jodal added the C-bug Category: This is a bug label Sep 25, 2015
@jodal jodal added this to the v1.0.0 milestone Oct 5, 2015
@jodal jodal self-assigned this Oct 5, 2015
@jodal
Copy link
Member

jodal commented Oct 5, 2015

I'm quite confident that this was fixed as a side effect of 7652f25.

@jodal jodal closed this as completed Oct 5, 2015
@jodal
Copy link
Member

jodal commented Oct 5, 2015

To be a bit more verbose: Previously, the GMusicPlaybackProvider.stop() method was overridden. It is no longer changed in any way, and should work identical to stop in any other Mopidy backend.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C-bug Category: This is a bug
Projects
None yet
Development

No branches or pull requests

2 participants