Bug 515639

Summary: Krita 6.0.0-beta-1 bug : stylus related : vector shape stays oddly glued to the cursor movement even after click release
Product: [Applications] krita Reporter: stephen <tgdev001>
Component: Tools/VectorAssignee: Krita Bugs <krita-bugs-null>
Status: REOPENED ---    
Severity: normal CC: dimula73, dra.w.p.il.e+bugskde, info
Priority: NOR    
Version First Reported In: 6.0.0-beta1   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: https://invent.kde.org/packaging/krita-deps-management/-/commit/3c98d5992acf1751c496b62950ce1c3e663656df Version Fixed/Implemented In:
Sentry Crash Report:

Description stephen 2026-02-06 16:47:47 UTC 
SUMMARY
This bug has been around for more than a year at this point.

Using stylus as you manipulate a vector shape from a click and hold
case, the vector after the release of the click, continues to stay glued
to the cursor for a while, and the faster the cursor movement, the longer
the problem holds before committing the action. 

This is frustrating because it is prone to incorrect vector shape adjustment every
time you use the stylus to work. This doesn't happen at all with mouse.

STEPS TO REPRODUCE
1. create a rectangular vector shape
2. using one of the edge's anchor and the vector shape, try to click and drag an edge
3. without stopping the drag, release your click 
4. look at what happens with the movement of the cursor

OBSERVED RESULT
The vector shape stays glued as if you didn't release the drag, 
and will stop only if your cursor movement is still.

EXPECTED RESULT
Right after releasing the click, the vector shape should instantly commit
and the position at which the cursor was when the click has been released.
No glueing of the vector shape to your moving cursor position should
happen after releasing the click

SOFTWARE/OS VERSIONS
Windows 10 Pro

ADDITIONAL INFORMATION
Tested with a Huion H1061P tablet( issue is common to 
Krita 5.3.x prealpha/beta versions,  and now 6.x beta )
Fixing this will probably affect also version 5.3.x so I will restrain from making
a duplicate just because the app version differs.
Comment 1 Wolfgang Baer 2026-02-07 06:31:47 UTC 
Confirmed: Win 10, Huion Pen tablet, Krita 6.1, Windows Ink (WinTab not testet).
Comment 2 Wolfgang Baer 2026-02-08 08:57:12 UTC 
Confirmed with WinTab as well now (Win 10, Huion Pen tablet, Krita 6.1).
Comment 3 Kitty 2026-02-08 16:49:49 UTC 
Confirmed also with Windows 11 Pro, One by Wacom and Krita 5.3.0.-beta1.

I have noticed that this bug occurs with Edit Shapes Tool, Select Shapes Tool and Text Tool (basically every tool where you resize, rotate or move vector shapes). It might have something to do with the pen's hover function since it never occurs when I use mouse. Of course, coding is extremely complex and it might be something completely else.

STEPS TO REPRODUCE
1. Open Krita and create a new document.
2. Add vector layer.
3. Draw a vector shape.
4. Activate Edit Shapes Tool, Select Shapes Tool or Text Tool. Select the vector.
5.  Move the square handles, nodes, segments or side handles with a pen, or move the vector shape itself. Don't lift the pen up in a direct 90-degree angle, but rather slowly drag it higher in an approximately 45-degree angle.

OBSERVED RESULT
Node/segment/handle will keep moving along with the pen even though the pen is not touching the tablet anymore. Krita might even pop up a notification box saying "waiting for image operation to complete…" 

EXPECTED RESULT
Nodes/segments/handles should stop moving the instance pen is no longer touching the tablet.
Comment 4 Dmitry Kazakov 2026-02-13 11:21:18 UTC 
I can somewhat confirm the issue. It is not as stable as bug 515614, but it seems like I get something like that here (Win11 + Wacom + WinTab).
Comment 5 Dmitry Kazakov 2026-02-13 14:29:35 UTC 
Git commit 3c98d5992acf1751c496b62950ce1c3e663656df by Dmitry Kazakov.
Committed on 13/02/2026 at 14:28.
Pushed by dkazakov into branch 'transition.now/qt6'.

[qt][win] Fix duplicated syntetic mouse events on WinTab

It could cause menus not being able to open when a
tablet was connected via WinTab API. It could cause
duplicated mouse events to be generated.
Related: bug 515614

M  +1    -1    ext_qt/CMakeLists.txt

https://invent.kde.org/packaging/krita-deps-management/-/commit/3c98d5992acf1751c496b62950ce1c3e663656df
Comment 6 dra.w.p.il.e+bugskde 2026-04-05 19:17:02 UTC 
*** Bug 518595 has been marked as a duplicate of this bug. ***
Comment 7 dra.w.p.il.e+bugskde 2026-04-05 19:18:23 UTC 
According to the duplicate Bug 518595, this is still not fixed (no other new information there, it's just the same description again.)