Bug 205349 - Amarok skips next track in playlist if it is shorter than current one
Summary: Amarok skips next track in playlist if it is shorter than current one
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.1.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-27 16:22 UTC by Alex Frolov
Modified: 2016-05-09 15:21 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 Alex Frolov 2009-08-27 16:22:09 UTC
Version:           2.1.1 (using 4.2.4 (KDE 4.2.4), 4.2.4-6.fc10 Fedora)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.25-170.2.72.fc10.x86_64

Amarok skips next track in playlist if it is strictly shorter than the current one. I also found that it never skip more than 2 tracks at a time.

Player's behaviour is always the same no matter if I use time bar or not or if I got crossfading turned on or off


Amarok 2.1.1 (built on Jun 13 2009)
KDE 4.2.4
Fedora 10 x86_64
Comment 1 Myriam Schweingruber 2009-08-27 17:05:08 UTC
Make sure you use the xine backend in phonon.
Comment 2 Alex Frolov 2009-08-27 18:36:18 UTC
Yes, it's the only backend installed
Comment 3 Mark Kretschmann 2009-08-27 19:24:23 UTC
This is actually caused by the "Now Playing" Plasma applet on your desktop. Removing it or upgrading to KDE 4.3 should fix your problem.

Merging with an older report, please see there.

*** This bug has been marked as a duplicate of bug 189265 ***
Comment 4 Alex Frolov 2009-08-28 01:32:39 UTC
"Now playing" applet is not present on my desktop
Comment 5 Myriam Schweingruber 2009-08-28 08:49:12 UTC
Hm, strange. Could you try narrowing down by removing the desktop widgets one by one? This bug has only appeared with the "Bow playing" widget till now, not unlikely there is another one causing trouble.
Comment 6 Mark Kretschmann 2009-09-18 09:56:07 UTC
Sorry, I don't think this could be Amarok's fault, and noone else can reproduce it. Also no new feedback from the user for quite a while.

Please test again with Amarok 2.2 (beta versions are released at this point).