Bug 503262 - When saving or opening files on a canvas the space key stops working, a key that works to move the canvas as well as the "ctrl" key, which combined serve to zoom in or out of the canvas
Summary: When saving or opening files on a canvas the space key stops working, a key t...
Status: REPORTED
Alias: None
Product: krita
Classification: Applications
Component: Tools/Move (other bugs)
Version First Reported In: 5.2.2
Platform: Microsoft Windows Microsoft Windows
: NOR major
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-24 02:45 UTC by BuranSan
Modified: 2025-09-11 08:02 UTC (History)
0 users

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 BuranSan 2025-04-24 02:45:36 UTC
SUMMARY
When saving or opening files on a canvas the space key stops working, a key that works to move the canvas as well as the "ctrl" key, which combined serve to zoom in or out of the canvas

STEPS TO REPRODUCE

1. Open Krita.

2. Create a new file or open an existing one.

3. Use the space key or Ctrl + space to pan or zoom — it works as expected.

4. Save the file or open another file (while a canvas is already open).

5. Try to pan or zoom again using the same shortcuts.


OBSERVED RESULT
The space key and Ctrl + space stop working entirely. Panning and zoom shortcuts do nothing. Only restarting Krita restores functionality.

EXPECTED RESULT
The spacebar and Ctrl+space shortcuts should continue working after saving or opening files.

SOFTWARE/OS VERSIONS
Windows: Windows 10, 64-bit
macOS: N/A
Linux/KDE Plasma: N/A
KDE Plasma Version: N/A
KDE Frameworks Version: N/A
Qt Version: N/A
Krita Version: (5.2.2)

ADDITIONAL INFORMATION

I initially thought it was a hardware issue, but it only happens in Krita.

No custom shortcut remapping involved.

Restarting Krita is the only way to fix it.

Happens consistently.
Comment 1 Vitamorus 2025-09-11 08:02:10 UTC
I cannot reproduce this on Linux, could this be a Windows-specific issue? Can somebody else with a Windows (10) machine try to reproduce it?