Created attachment 192673 [details] recording Layer selection behaves oddly (probably with vector layers, but I'm not sure). I was able to reproduce this bug with every document, but exactly how it happened was so random. I cannot provide steps to reproduce this bug consistently. I'll attach a recording and my .kra file used in the recording. SOFTWARE/OS VERSIONS Operating System (available in the Info Center app, or by running `kinfo` in a terminal window): Windows 10 (x64) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Created attachment 192674 [details] kra file used in the recording
Ok, I found a way to reproduce it somewhat consistently: 1. Open a document (with the background as a raster layer). 2. Add more than 2 vector layers in a row right above the background layer. It should look like - Vector Layer - Vector Layer - Background Layer 3. Try to select different layers in the layers docker (with the arrow keys or mouse clicks; the method doesn't matter). 4. The results: It selects random layers, the selection can be stuck in between layers, etc.
Can confirm, same cause as bug 520718 and bug 520723.
A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/2803
Git commit 3713225956c74ba68702a7b57f492f6e6a753d9c by Dmitry Kazakov, on behalf of Carsten Hartenfels. Committed on 28/05/2026 at 13:20. Pushed by dkazakov into branch 'master'. Revert keyframe selection changing layer selection This reverts commit 8965a0dd68ca7a34cd770642499e417a78520b65 because the logic is broken, it will react to *any* change of the current index, not just ones that are initiated by the user interacting with the timeline. That causes all sorts of mayhem, like switching between documents changing the layer selection, opening a file selecting the wrong layer and moving through the layer list with the arrow keys causing various weird effects on the current and selected layer. This would be fixable by detecting whether the user triggered the change via the timeline, but that's sufficiently complicated that it'll need more testing first. The bugs this change causes are too major, so just reverting it for now. Related: bug 520718, bug 520723 M +0 -6 plugins/dockers/animation/KisAnimTimelineFramesModel.cpp M +0 -2 plugins/dockers/animation/KisAnimTimelineFramesModel.h M +0 -4 plugins/dockers/animation/KisAnimTimelineFramesView.cpp https://invent.kde.org/graphics/krita/-/commit/3713225956c74ba68702a7b57f492f6e6a753d9c
Git commit 1eb41e5befde48bd69834a7d17536c73ac7ddc6b by Dmitry Kazakov, on behalf of Carsten Hartenfels. Committed on 28/05/2026 at 13:22. Pushed by dkazakov into branch 'krita/6.0'. Revert keyframe selection changing layer selection This reverts commit 8965a0dd68ca7a34cd770642499e417a78520b65 because the logic is broken, it will react to *any* change of the current index, not just ones that are initiated by the user interacting with the timeline. That causes all sorts of mayhem, like switching between documents changing the layer selection, opening a file selecting the wrong layer and moving through the layer list with the arrow keys causing various weird effects on the current and selected layer. This would be fixable by detecting whether the user triggered the change via the timeline, but that's sufficiently complicated that it'll need more testing first. The bugs this change causes are too major, so just reverting it for now. Related: bug 520718, bug 520723 M +0 -6 plugins/dockers/animation/KisAnimTimelineFramesModel.cpp M +0 -2 plugins/dockers/animation/KisAnimTimelineFramesModel.h M +0 -4 plugins/dockers/animation/KisAnimTimelineFramesView.cpp https://invent.kde.org/graphics/krita/-/commit/1eb41e5befde48bd69834a7d17536c73ac7ddc6b
*** Bug 520729 has been marked as a duplicate of this bug. ***
Git commit b1ffdd65d4ff5cb2c34caf6121acf893f2c3e499 by Dmitry Kazakov, on behalf of Carsten Hartenfels. Committed on 29/05/2026 at 21:17. Pushed by dkazakov into tag 'v6.0.2.1'. Revert keyframe selection changing layer selection This reverts commit 8965a0dd68ca7a34cd770642499e417a78520b65 because the logic is broken, it will react to *any* change of the current index, not just ones that are initiated by the user interacting with the timeline. That causes all sorts of mayhem, like switching between documents changing the layer selection, opening a file selecting the wrong layer and moving through the layer list with the arrow keys causing various weird effects on the current and selected layer. This would be fixable by detecting whether the user triggered the change via the timeline, but that's sufficiently complicated that it'll need more testing first. The bugs this change causes are too major, so just reverting it for now. Related: bug 520718, bug 520723 M +0 -6 plugins/dockers/animation/KisAnimTimelineFramesModel.cpp M +0 -2 plugins/dockers/animation/KisAnimTimelineFramesModel.h M +0 -4 plugins/dockers/animation/KisAnimTimelineFramesView.cpp https://invent.kde.org/graphics/krita/-/commit/b1ffdd65d4ff5cb2c34caf6121acf893f2c3e499