https://bugs.kde.org/show_bug.cgi?id=491730
Bug ID: 491730
Summary: Canvas Keyboard/Mouse Shortcuts Become Unresponsive
After Windows Snipping Tool
Classification: Applications
Product: krita
Version: 5.2.4
Platform: Compiled Sources
OS: Microsoft Windows
Status: REPORTED
Severity: major
Priority: NOR
Component: Shortcuts and Canvas Input Settings
Assignee: krita-bugs-n...@kde.org
Reporter: darkennedhe...@gmail.com
Target Milestone: ---
Created attachment 172627
--> https://bugs.kde.org/attachment.cgi?id=172627&action=edit
Information given to me by Krita for the bug report
SUMMARY:
Either immediately after starting Krita or even hours later, if I try to use
the Windows snipping tool (Wins + S), while Krita is in focus, I'm unable to
move the canvas in any way WHILE USING KEYBOARD AND MOUSE SHORTCUTS. I can
still move if I select the pan tool, or zoom with the zoom tool, or rotate
using the dial at the bottom right of Krita. However, shortcuts like Space,
Ctrl + Space, Shift + Space, middle mouse button, or scroll button, it does
nothing. Not even the icon shows up.
STEPS TO REPRODUCE:
1. Open up Krita
2. Open up any image, it can be a regular image or .kra.
3. Use Windows snipping tool.
4. I can no longer use keyboard or mouse shortcuts to move the canvas.
NOTES:
I'll be honest though, this bug is very very finnicky and I have no idea what
the real culprit is. Sometimes it doesn't happen (like after I updated to
latest version 5.2.4, this didn't happen for the first few days, and I use the
snipping tool A LOT so I would've noticed). I've also noticed, at several times
and at several random intervals, certain shortcuts just wouldn't work. Like I
recall one time the deselect shortcut (ctrl + shift + A) wasn't working, and it
was only via restart that it did.
This is in fact my 3rd time writing this, because the 1st time I assumed this
was a bug on my end because you know, it STOPPED happening, and the 2nd time, I
was very very close to finishing this report and I decided to run one final
test. The test goes as follows:
1. Open up my latest version of Krita and repeat the glitch 4x (check steps
above). All of it was successful.
2. Decide to download an older version of Krita, like 5.2.3.
3. Notice that the bug doesn't happen there, so this is, in fact, a bug with
5.2.4.
4. Before sending the report, I repeat the bug one more time, just for
posterity's sake. I can no longer reproduce the bug.
I gave up on the report because something this chaotic would likely be
something on my end, and I wasn't smart enough to know why, after launching
Krita 5.2.3, Krita 5.2.4 no longer does the bug but, BUT!
The bug's back! And even in Krita 5.2.3! I'll be willing to send more
information but I genuinely cannot use Krita if this bug keeps showing up, it's
not even consistent.
Embedded below is the log that the Krita client gave me. I'll be paying
attention to my email and I'll be down to give more information, including live
video of this bug happening (if it decides to happen again).
Thank you.
--
You are receiving this mail because:
You are watching all bug changes.
