Bug 222559 - amarok stops after each further track when one track was not found on the HD
Summary: amarok stops after each further track when one track was not found on the HD
Status: RESOLVED DUPLICATE of bug 192114
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.3-GIT
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-13 17:18 UTC by Mathias Panzenböck
Modified: 2010-01-13 21:37 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mathias Panzenböck 2010-01-13 17:18:17 UTC 
Version:           2.2-GIT (using 4.3.4 (KDE 4.3.4), 4.3.4-1.fc11 Fedora)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.30.9-102.fc11.x86_64

Git Version: 8a35ca8ae31f61545c50965f1cb59a649254c74f

When a file of the playlist was not found on the HD (because it was deleted/moved) amarok will skip to the next track, but then will stop playing after this track. When you hit play to play the next track it will stop after this one. This keeps happening until you restart amarok.

The file was deleted even before amarok was started. I don't know if that is significant.
Comment 1 Myriam Schweingruber 2010-01-13 21:37:21 UTC 

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