Bug 513875 - (sometimes) it needs two presses on the "go to current track" to work
Summary: (sometimes) it needs two presses on the "go to current track" to work
Status: REPORTED
Alias: None
Product: amarok
Classification: Applications
Component: Playlist (other bugs)
Version First Reported In: 3.3.1
Platform: Arch Linux Linux
: NOR minor
Target Milestone: kf5
Assignee: Amarok Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-27 13:07 UTC by Quentin Guyot
Modified: 2025-12-27 13:07 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Quentin Guyot 2025-12-27 13:07:04 UTC
SUMMARY
It needs two presses on the "go to current track" to work
The thing triggering the issue is (I think, it might not be true) is when there is a track change, the new track isn’t visible, and Amarok is not focused.


STEPS TO REPRODUCE
1. launch playback
2. make sure the next track isn’t visible in the playlist
3. give focus to another window. (I think it needs Amarok not to be visible at all for the bug to occur)
4. go back to Amarok and press "go to current track"

OBSERVED RESULT
it doesn’t work at first, and you need a second press to work

EXPECTED RESULT
It should work immediately

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.18.2-arch2-1 (64-bit)
Graphics Platform: Wayland


ADDITIONAL INFORMATION
If the track change is triggered by the queue, it worked as intended when I tested. The track change has to come from "normal" playlist behavior.

I’m not certain I have figured out entirely what triggers the need to double press. My usual Amarok use is with a very long playlist of varied tracks played at random, if that helps.