DESCRIPTION Krita doesn't remember the last chosen layer in your document when switching to another document. The bug first appears in 5.3.2. It is not present in 5.3.1.1 or earlier. STEPS TO REPRODUCE 1. Create 2 new documents 3. In the first document, in the layer docker, choose the background layer at the bottom 4. Switch to the second document 5. Switch to the first document OBSERVED RESULT The chosen layer is the top paint layer EXPECTED RESULT The chosen layer is the background layer SOFTWARE/OS VERSIONS Android 16 arm64 Krita 5.3.2
Also happens on Linux.
Bug 520723 probably has the same cause.
Yes, it's caused by 8965a0dd68ca7a34cd770642499e417a78520b65. It was supposed to select the current layer on the animation timeline when you select a frame, but it also incorrectly reacts to a bunch of other things and messes up the layer selection.
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 520723, bug 520744 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 520723, bug 520744 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
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 520723, bug 520744 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