Bug 278265 - Playback stops after every track
Summary: Playback stops after every track
Status: RESOLVED DUPLICATE of bug 268892
Alias: None
Product: amarok
Classification: Applications
Component: Services/Magnatune (show other bugs)
Version: 2.4.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 2.4.2
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-22 11:59 UTC by Marcus Harrison
Modified: 2011-07-23 23:28 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Harrison 2011-07-22 11:59:10 UTC
Version:           2.4.1 (using KDE 4.6.4) 
OS:                Linux

While streaming music without an account from Magnatune, the end of every track stops music playback, requiring the user double-click the next track to continue playing.

Reproducible: Always

Steps to Reproduce:
Navigate to the Magnatune music section in Amarok
Drag multiple tracks to the Now Playing section of Amarok (or into the, "Replace Playlist" Context Area hover section)
Play the first Magnatune track by double-clicking it
Relax
At the end of the track, wait for the next track to play
Be disappointed.

Actual Results:  
Amarok stops playing, prompting manual intervention from the user to play the next track

Expected Results:  
The next track plays automatically

OS: Linux (i686) release 2.6.38.8-35.fc15.i686
Compiler: gcc
Comment 1 Myriam Schweingruber 2011-07-23 11:59:49 UTC
Which phonon backend and version are you using?
Comment 2 Marcus Harrison 2011-07-23 13:33:33 UTC
GStreamer backend, version 4.5.1 using Phonon 4.5.0 (according to Yum, is there a better way to find out?).
Comment 3 Myriam Schweingruber 2011-07-23 23:28:58 UTC
I don't know for RPM based systems, in apt-based systems you just do apt-cache showpkg <packagename> or alternatively aptitude show <packagename>.

Anyway, this is a known bug in the gstreamer backend.

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