Bug 433318 - tools can get "stuck" in a non-functioning way
Summary: tools can get "stuck" in a non-functioning way
Status: RESOLVED DUPLICATE of bug 441232
Alias: None
Product: krita
Classification: Applications
Component: Tools (show other bugs)
Version: 4.4.2
Platform: Homebrew (macOS) macOS
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
Depends on:
Reported: 2021-02-20 11:42 UTC by Tobias Richter
Modified: 2021-09-08 09:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

screen recording showing non-working tool switch (1009.80 KB, video/quicktime)
2021-02-20 11:42 UTC, Tobias Richter

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Richter 2021-02-20 11:42:54 UTC
Created attachment 135962 [details]
screen recording showing non-working tool switch

I use a Wacom tablet and most of the time everything works fine and krita is amazing!
Sometimes when switching pens krita accidentally enters an unwanted mode. I have observed that to be either "rotate" or "zoom". The problem is that this only works very briefly. For example rotating the canvas a little. But the rotate tool or magnifying glass stays stuck to the cursor. Pressing Escape, selecting another tool etc do not get rid of the changed cursor. While the pointer works to select menu items, tools, pretty much anywhere in the UI - it does not have any effect to the canvas image. Not even the advertised zoom or rotate function. The only work around I found is to save the work, restart krita and load the file back in.

Here are two reports that sound very similar:

This happens with a low but sufficiently annoying frequency in my setup. 
1. switch brush/tool (from right click menu or docker)
2. get annoyed when something unexpected like zoom or rotate happens

* selected tool non-functional and cannot be deselected
(screen recording attached)

* regardless of what tool was accidentally selected somehow the tool picker should restore the cursor to a working state

macOS: 11.2.1

Comment 1 Tobias Richter 2021-02-20 23:27:43 UTC
https://bugs.kde.org/show_bug.cgi?id=433285 sounds very similar.
Comment 2 tomtomtomreportingin 2021-02-20 23:57:56 UTC
The issue might be similar, but the root cause might be rather different, as this is not something I seem to be able to reproduce on Linux. The developers require reproduction steps that consistently enables this buggy behavior, or else the problem is rather difficult to diagnose and fix.
Comment 3 wolthera 2021-09-08 09:31:58 UTC

*** This bug has been marked as a duplicate of bug 441232 ***