Bug 491730 - Canvas Keyboard/Mouse Shortcuts Become Unresponsive After Windows Snipping Tool
Summary: Canvas Keyboard/Mouse Shortcuts Become Unresponsive After Windows Snipping Tool
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Shortcuts and Canvas Input Settings (other bugs)
Version First Reported In: 5.2.4
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-14 21:32 UTC by Vank
Modified: 2024-11-28 03:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Information given to me by Krita for the bug report (709.14 KB, text/plain)
2024-08-14 21:32 UTC, Vank
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vank 2024-08-14 21:32:04 UTC
Created attachment 172627 [details]
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.
Comment 1 Halla Rempt 2024-10-29 12:20:11 UTC
Win+S on my laptop opens the start menu, not the snipping tool. 

It sounds like Krita doesn't get keyboard focus when tabbing back from another application.

I tried the following:

* Start Krita, create a new image
* Start the snipping tool
* alt-tab between the two
* press backspace and delete in krita to fill and clear the canvas

And that worked, so I have not been able to reproduce the issue. Have you since then found out more about this issue?

*
Comment 2 Bug Janitor Service 2024-11-13 03:47:00 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2024-11-28 03:46:58 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.