See the same on my system. Unfortunately it only happens sometimes, so might be a little bit difficult to reproduce. But it still seems to be there in 1.8.0.

I have the same issue on 1.6.1 (running on debian squeeze), and I managed to get a consistent repro. The steps are the following:

1. Clear the play queue
2. Go to Music
3. Drag some songs to the play queue.
4. Double click the play queue in the sources list to start the playback.
5. Wait for the playback stop after having played all songs.
6. Now, drag some more songs to the play queue.
7. Double click the play queue again to start playback.
8. After the first song, playback will stop.

It seems the key step to reproduce is the 5th. 
Note that clearing the queue will cause the next bunch of songs to be played correctly, so it seems there's some status somewhere not being correctly set/reset when songs are added to a play queue that already contains songs (even thou they are already played).

It might also be relevant to note that adding songs to a running playlist will cause a similar issue, causing the playlist to stop after the last song that was available in the queue when playback was started (i.e. before starting to add songs).

Hope this helps to get it fixed, because it's super annoying :)

I'm making a note for myself to test this tonight, however it wouldn't hurt for one of the original reporters to also confirm that this is still happening with the latest versions of Banshee (preferably 1.9.3 or git master).

Also, I don't know if anyone has tried to capture a debug log while this issue is happening, but if we're lucky, something useful might be written to the log.  Instructions: http://live.gnome.org/Banshee/CommonQuestions/Logs

I will try to get a log file tonight, but I'm still on 1.6.1 (I've updated my Squeeze to the new testing, but the banshee package is still the same).

I just tried again. Can confirm the problem still exists in 1.8.1 and 1.9.3.

As far as I can gather, it only occurs after you have played through the entire queue (as in comment#2).

Then, if you add new tracks, and doubleclicks the first to start playback, it will play that one song. Then it will either stop, or, if there is an active cursor in some other playlist, continue there.

In my experience the same happens if you add another item to the play queue only when Banshee is playing the *last* entry. Symptoms as above then materialises: Even though you have added another entry, it will finish playing the song, then stop, or continue on some other playlist or library view. 

If there are several entries yet to be played, everything seems to be OK here (contrary to commenter in coment #2).


I have queue fill sett to Manual.
Banshee 1.9.3, debian/sid.

Created attachment 181830 [details]
annotated debug log

Created attachment 181831 [details]
complete debug log (not annotated nor cut down)

I'm having the same issue on Banshee 2.2 out of the box on ubuntu 11.10.
I've always had this bug since 1.6.

The steps described by Gonzalo Casas are exactly my common use case, so this bug is really annoying. It would be really great if this was corrected.

How I am reproducing it :

1- launch banshee
2- add some songs to the play queue
3- play all the play queue
4- woups, no music in my ears, let's add some again in the play queue
5- double clicking on the first one
6- the music stops at the end of the first new song, but banshee do not read the next one.

It really seams that the playing queue is in a weird state at the end of the first full lecture.

If someone could change the status to "Confirmed" I would be grateful !

send me a message for more informations.

Can anyone confirm if this bug is still reproducible with Banshee 2.6.x? And if yes, does the bug disappear if you turn off Gapless playback?

Thanks

Seems to be solved nowadays