Bug 516133 - Holding down shift and Space to rotate the Canvas or using touch controls studder or crash
Summary: Holding down shift and Space to rotate the Canvas or using touch controls stu...
Status: NEEDSINFO WAITINGFORINFO
Alias: None
Product: krita
Classification: Applications
Component: Usability (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Other
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-17 05:24 UTC by Nicholas
Modified: 2026-02-17 05:36 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 Nicholas 2026-02-17 05:24:04 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. Hold down Shift and Space or use touch control, use two fingers and turn
2. try and rotate canvas
3. 

OBSERVED RESULT
Studding in rotation  often leads to crashing

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 03.06
Qt Version: 

ADDITIONAL INFORMATION
framework 12 i5 labtop Ubuntu 25.10
Comment 1 dra.w.p.il.e+bugskde 2026-02-17 05:36:47 UTC
You'll have to provide some more information about this.

First, how did you install Krita? Does the problem happen with the AppImage from the krita.org website? 

Second, please attach the information from Help → Show Krita log for bug reports.

Third, also attach the information from Help → Show system information for bug report.

If you can figure out how to do it (it's a bit complicated), a backtrace would also be useful. Like it instructed you in your report:

> If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports