Bug 327308 - Track playback hang when an ogg and 'Stop playing after this track' selected
Summary: Track playback hang when an ogg and 'Stop playing after this track' selected
Status: RESOLVED DUPLICATE of bug 296100
Alias: None
Product: amarok
Classification: Applications
Component: Playback (show other bugs)
Version: 2.8.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: 2.9
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-08 14:32 UTC by robert marshall
Modified: 2013-11-10 19:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description robert marshall 2013-11-08 14:32:20 UTC
If you select  stop playing after this track when the track is in ogg format, then when playback reaches the end of the track it stops playing but the UI doesn't change - it appears paused but the pause button doesn't change to play and the current track still shows it as playing (and window header still has the track as its title). Inspection of last played time show that hasn't been updated.
Sometimes amarok will return to 'stopped' state - this may take up to 3 minutes though I have waited longer than that with still no change. If you press stop then the interface responds, last played is updated and the UI state is correctly updated.

Reproducible: Always

Steps to Reproduce:
1. select 'stop playing after this track' when the track is .ogg (can be selected either when it is playing or if it is later in the playlist)
2. wait for amarok to report stopped state at the end of the ogg track
3.
Actual Results:  
track appears to be still playing though the time bar is at the end and no sound appears

Expected Results:  
Expect the UI to report amarok stopped

backend gstreamer 4.6.3
Comment 1 Myriam Schweingruber 2013-11-08 15:16:44 UTC
Could you please check if this also happens with the phonon-backend vlc? If not, then this is a known gstreamer problem, not an Amarok one, there must be like 50 duplicates for that already.
Comment 2 robert marshall 2013-11-09 11:52:05 UTC
Were you thinking of (for example) https://bugs.kde.org/show_bug.cgi?id=302652 as a duplicate? 
I'm not seeing that problem at all in my installation so the external symptoms appear different - and not overlapping. I did search for duplicates and couldn't see anything which looked likely.

As you'll see from the bug I've just reported I can't do the test with xine as amarok crashes: https://bugs.kde.org/show_bug.cgi?id=327359
Comment 3 Myriam Schweingruber 2013-11-10 08:30:29 UTC
Erm, no? I never talked about xine, as the xine backend is dead since over 3 years and you shouldn't even have it in the repositories anymore, that is clearly an error on behalf of the distribution packagers.

I asked you if you could test with the phonon-backend-vlc, as there are known file transition problems with the phonon-backend-gstreamer, please read again what I wrote in my first comment.
Comment 4 robert marshall 2013-11-10 15:32:55 UTC
Sorry about that! ..attempts to unscramble mind..,

My guess is that the xine backend came in with the clementine install (the .so was dated Jan 11)

Yes I can confirm that the pause doesn't happen with vlc - (though I don't think I'd seen the problem before the move to 2.8 of amarok) you may assign it as a duplicate!
Comment 5 Myriam Schweingruber 2013-11-10 15:38:39 UTC
Thank you for the feedback.

FWIW: Even Clementine shouldn't drag in Xine, they don't use Phonon at all, but gstreamer directly. I strongly recommend you remove the phonon-backend-xine package from your system, might be a leftover from older installations.

*** This bug has been marked as a duplicate of bug 296100 ***
Comment 6 robert marshall 2013-11-10 16:05:34 UTC
Thank you and have now uninstalled the xine backend; FWIW synaptic showed the information that the xine backend was installed as a replacement for kde-style-oxygen (??) at least something with kde & oxygen in the name which seems crazy; having uninstalled it it doesn't appear in the package list (which is good!)
Comment 7 Myriam Schweingruber 2013-11-10 19:44:19 UTC
But you should in no way have changed the bug status, that was just not something you should do.

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