Created attachment 192659 [details] test file DESCRIPTION I have a big KRA file with many groups and layers, nested hierarchy (2-3 groups in groups) With new update (5.3.2) krita started to ignore: - the groups that was opened on before KRA file save - the active layer that was active on before KRA file save Now when the file is opened - it always open some fixed group and activate irrelevant layer. Instead of restoring the state that was on file save. It worked before (in 5.3.1) STEPS TO REPRODUCE 1. Open attached Kra in krita 5.3.2 2. Observe the active layer - this is WRONG active layer 3. Open attached Kra in krita 5.3.1 4. Observe the active layer - this is proper active layer I attached screenshot before save and after open SOFTWARE/OS VERSIONS OS: macOS 26.5 Krita Version: 5.3.2 (git 7d1ae74) Hidpi: true Sandbox: false Qt Version (loaded): 5.15.7
Created attachment 192660 [details] before save
Created attachment 192661 [details] after open
Also happens on Linux. This probably has the same cause as bug 520718.
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 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 520718, 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 520718, 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