Bug 419331 - Resume every track from the previous position (of a different track)
Summary: Resume every track from the previous position (of a different track)
Status: RESOLVED DUPLICATE of bug 408295
Alias: None
Product: Elisa
Classification: Applications
Component: general (show other bugs)
Version: 19.12.3
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Matthieu Gallien
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-28 11:40 UTC by Pietro F. Fontana
Modified: 2020-11-11 19:01 UTC (History)
2 users (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 Pietro F. Fontana 2020-03-28 11:40:18 UTC
SUMMARY
When I open Elisa and play a track it will not start from the beginning, but from the position at which I stopped the last track before closing Elisa.
The problem is that this happens with every track, not only with the last played track.

STEPS TO REPRODUCE
1. Play track A, pause it at 1:45, close Elisa.
2. Open Elisa, play track B.

OBSERVED RESULT
Elisa starts playing track B at 1:45.

EXPECTED RESULT
Elisa starts playing track B from the beginning.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1
Kernel Version: 5.5.13-1-MANJARO
OS Type: 64-bit
Elisa Version: 19.12.3
Comment 1 Matthieu Gallien 2020-03-28 20:17:11 UTC
Thanks for the report.

This is already tracked by an existing bug.

*** This bug has been marked as a duplicate of bug 408134 ***
Comment 2 Matthieu Gallien 2020-03-28 20:18:18 UTC
Sorry, I have again confused bug 408134 with the bug you are reporting.
Comment 3 Matthieu Gallien 2020-04-05 19:58:00 UTC
I have just reproduced it by accident.

I will have a look at it in the near future but might be unable to fix it for the next stable release.
Comment 4 Nate Graham 2020-04-15 17:48:12 UTC
Yeah I see this too. It's a variant of bug 408134, but not exact same thing.
Comment 5 Nate Graham 2020-11-11 19:01:24 UTC

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