After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 548391 - Play Queue should return to previous source and state
Play Queue should return to previous source and state
Status: RESOLVED DUPLICATE of bug 547213
Product: banshee
Classification: Other
Component: Playback
git master
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-19 07:19 UTC by Mathijs
Modified: 2008-09-25 17:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mathijs 2008-08-19 07:19:16 UTC
When banshee 1.2.1 is done playing all the tracks in the play queue, playback should stop. Instead, banshee then starts playing tracks from the music library. 
This is wrong.

Steps to reproduce:
1) drag a single song to the play queue
2) select the play queue and click the song to start playback

Expected behavior: banshee plays this one song and then stops

Actual behavior: after playing the song, banshee continues playing tracks from your library. With normal play order selected, it will start playing the first track in the library.
Comment 1 Andrew Conkling 2008-09-08 04:18:47 UTC
An additional case: I am playing from another source (e.g. Music Library, a playlist).
1. I add something to the play queue.
2. When that song is done, the play queue starts.
3. When the Play Queue is finished, playback should return to my previous source (and pick up at the right song).

In general, the play queue should remember what was happening when it started and return there when finished.
Comment 2 Wouter Bolsterlee (uws) 2008-09-23 13:02:11 UTC
Well, I'd say that Muine should *always* stop playing after the last item in the play queue has been played.
Comment 3 Michael Martin-Smucker 2008-09-24 23:01:01 UTC
Is this a dupe of Bug 547213 ?
Comment 4 Andrew Conkling 2008-09-25 17:59:50 UTC
Yes, thanks for catching that.

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