Bug 405047

Summary: "Banned sign"-shaped cursor when using stylus; can't draw normally
Product: [Applications] krita Reporter: tusooa <tusooa>
Component: Tablets (tablet issues are only very rarely bugs in Krita!)Assignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: scottpetrovic
Priority: NOR    
Version First Reported In: nightly build (please specify the git hash!)   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description tusooa 2019-03-03 22:22:41 UTC
SUMMARY

When drawing with the stylus, the cursor becomes a banned sign. Only a part, if any, of the intended stroke appears on the canvas.

Surface Pro 4.
Windows 10 x64.
version: krita-nightly-x64-v4.2.0-prealpha-333-g917d6980fc-setup.exe
AND 4.1.7.101 (git 55a1810). 

STEPS TO REPRODUCE
1. Create Document.
2. Draw with mouse.
3. Draw with stylus.
4. Draw with mouse.

This is *not* limited to Freehand tool only. Other tools like Move, Line also experience this bug.

OBSERVED RESULT
2. Can draw normally.
3. The cursor becomes a banned shape. Only a part of the intended stroke goes into the canvas. (See video: http://45.32.228.177:8000/krita-stylus.mp4 too large to upload)
4. Can draw normally.

EXPECTED RESULT
2, 3, 4 can all draw normally.

SOFTWARE/OS VERSIONS
Windows: 10
MacOS: N/A
Linux/KDE Plasma: N/A
(available in About System)
KDE Plasma Version: N/A
KDE Frameworks Version: (Does not display)
Qt Version: (Does not display)

ADDITIONAL INFORMATION

This bug does not happen in 4.1.1.
Comment 1 tusooa 2019-03-03 23:44:30 UTC
Krita 4.1.7 does not encounter this problem.
Comment 2 Scott Petrovic 2019-04-05 15:39:44 UTC
Does this only happen on a Surface Pro 4? I am testing git master on a Windows 10 + Huion device and am not running into this issue.
Comment 3 tusooa 2019-04-05 18:53:57 UTC
(In reply to Scott Petrovic from comment #2)
> Does this only happen on a Surface Pro 4? I am testing git master on a
> Windows 10 + Huion device and am not running into this issue.

git 917d698 from Krita nightly builds (latest version till now) does not have this problem. Chances are this is fixed in some commits after the version in question.