Bug 514563 - Pasting an external image with ctrl+V messes with the layer selection
Summary: Pasting an external image with ctrl+V messes with the layer selection
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Layer Stack (other bugs)
Version First Reported In: nightly build (please specify the git hash!)
Platform: Mint (Ubuntu based) Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2026-01-14 00:16 UTC by Regis
Modified: 2026-01-30 09:20 UTC (History)
1 user (show)

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 Regis 2026-01-14 00:16:55 UTC
Hi,

In the latest nightly builds, the behavior when pasting an image from the system clipboard (copied from outside Krita) affects layer selection differently if I use the ctrl+V shortcut instead of using the menu button (Edit -> paste), while it shoud be the same.

To reproduce :

Take a full or partial screeenshot of your desktop.
In Krita, in a document with one layer called "Paint Layer 1" selected, paste the clipboard content with the edit menu: "Edit" -> "Paste". A new layer is created with the data from the previously made screenshot, and this new layer is now the selected one. This is the expected result.
But, if instead of pasting the clipboard image content through the edit menu, you choose to paste it wit the ctrl+V shortcut, the result is different: it still creates the new layer correctly, but both this new layer and the previous one (Paint Layer 1) end up selected. And if you keep hitting ctrl+V it continues to expand the layer selection with each new layer.

This only happens when pasting clipboard content from outside Krita, and with the ctrl+v shortcut. When copy/pasting layers from one Krita file to the other (or inside the same file) the behavior is fine: only the last copy of the layer is selected.

Tested on Krita 5.3.0-prealpha (git f49c72d), on both Linux Mint Cinnamon 22.3 and Windows 11
I think I noticed it a few weeks back in a nightly, but I didn't keep any older build where this worked. I think in early December or late November this still worked fine in the nightlies (as it does in the last official release).
Comment 1 dra.w.p.il.e+bugskde 2026-01-14 06:59:17 UTC
Thanks for the report, it's reproducible. A note on the reproduction steps: the image has to come from an external source (a screenshot or other application) and you must have set the color management paste jumpscare dialog to "remember" so that it doesn't show up and give you a chance to release the Ctrl key before the layer is created.

This is related to Bug 514427 and reverting commit d3eaaf15976380a5df6370dfa9ccd7f5b281f34f also fixes it. To make sure that the fix actually gets tested against both behaviors, I'll leave both bugs open though.
Comment 2 Bug Janitor Service 2026-01-15 15:47:16 UTC
A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/2601
Comment 3 Dmitry Kazakov 2026-01-28 09:11:27 UTC
Git commit 071d8bdd5ec0eba01b3297d646300a420c59570d by Dmitry Kazakov, on behalf of Luna Lovecraft.
Committed on 28/01/2026 at 09:11.
Pushed by dkazakov into branch 'master'.

Layer selection fixes

This fixes layer selection on qt5 (as i forgot to test my
previous patch on qt5), fixes an issue where layer selection
was behaving different from how it does in stable, and 
properly fixes shift selection on qt6
Related: bug 514427

Test Plan
---------

1. Build with qt5
2. Create a bunch of layers
3. Ctrl click an unselected layer
4. Layer gets selected/unselected properly


1. Build with qt6
2. Create a bunch of layers
3. Shift click to select multiple layers
4. Layers get selected properly

M  +18   -0    plugins/dockers/layerdocker/NodeDelegate.cpp
M  +48   -9    plugins/dockers/layerdocker/NodeView.cpp

https://invent.kde.org/graphics/krita/-/commit/071d8bdd5ec0eba01b3297d646300a420c59570d
Comment 4 Regis 2026-01-30 09:20:36 UTC
Thanks a lot for fixing this, since the last nightly, it works great :)