Sometimes when using liquify with a tablet, the transform is randomly applied, without touching the enter key. This is completely random. Sometimes, it gets applied after the first stroke, contantly, sometimes I can go for an hour without any applying. Bollebib experienced something similar. Reproducible: Always
How do you think, can the touch support be involved? Or switching layers or switching tools or pressing Ctrl+Z?
(In reply to Dmitry Kazakov from comment #1) > How do you think, can the touch support be involved? Or switching layers or > switching tools or pressing Ctrl+Z? Well, I turned the touch support off using your kritarc entry. It also does not matter whether I touch or don't touch the screen. I did not switch layers, or use ctrl+z.
yes I encounter this constantly. The annoying thing is I can't enforce it,it seems random indeed.
*** Bug 351440 has been marked as a duplicate of this bug. ***
While using wacom tablet to do Liquify transformations, sometimes Transformation tool is switched to another (maybe randomly choosen) tool, and applying changes without press "apply button". In this case there may be another unexpected behaviour. Sometimes Transform mask loose part of changes, made in previous transformations. But undo can bring it back. Steps to Reproduce: I cannot describe steps to reproduce precisely, but if you have wacom tablet, you can just apply Liquify Transformations to transform mask with wacom tablet, and using mouse to change tool parameters. And after some trying you will see behaviour I describe. I use image ~4000x3000px (8bit sRGB). tablet = Wacom Intuos CTH-680
I believe this is caused by another bug I experience, which is brush preset randomly changing with Wacom tablet. It usually happens when changing between mouse and pen, or when I lift pen off, out of the tablet's detection range. My theory is that there is a "phantom device", in addition to existing devices like pen, eraser and mouse, and when this happens it is the phantom device that gets activated. To theorize further, this may be related to the fact that Wacom tablets report as several devices. I wonder if this only happens with tablets that have extra function like quick buttons, or also on ones that don't? Mine is a new Intuos Pen & Touch Medium.
(In reply to Storm from comment #6) > My theory is that there is a "phantom device", in addition to existing > devices like pen, eraser and mouse, and when this happens it is the phantom > device that gets activated. > > To theorize further, this may be related to the fact that Wacom tablets > report as several devices. I wonder if this only happens with tablets that > have extra function like quick buttons, or also on ones that don't? > > Mine is a new Intuos Pen & Touch Medium. I agree with that theory. For me it seems like same behaviour. I wonder if there is some workaround, maybe to disable other wacom devices, except pen... I will try to do this maybe with xinput...
(In reply to sghpunk from comment #7) > I wonder if there is some workaround, maybe to disable other wacom devices, > except pen... That will most likely break some functionality of the tablet. In think we should focus on finding a real fix instead.
Actually the workaround is known already: the ghost input device is the touch input, disable that and this dissapears.
No wonder I never can reproduce... I always disable touch :-)
(In reply to wolthera from comment #9) > Actually the workaround is known already: the ghost input device is the > touch input, disable that and this dissapears. I have touch disabled, yet I can reproduce. I have it disabled via the little switch on the tablet itself. There is no other way I know of to disable it, the linuxwacom driver doesn't have any interface I know of, and the AUR package that would add control panel entry to KDE is broken.
(In reply to Storm from comment #11) > I have touch disabled, yet I can reproduce. I just tried to disable all devices, and even mouse with "xinput disable ..." leaving only Wacom pen and eraser, but bug is still present. I cannot disable eraser, because then pen is disabled automatically. So there is no workaround (for me) in this way...
(In reply to wolthera from comment #9) > Actually the workaround is known already: the ghost input device is the > touch input, disable that and this dissapears. for the reported bug? I always disable touch,so that seems strange to me as it still happens. unless you were discussing something else.
Any update on this? It's really annoying and often causes various issues. I disabled touch both via the little switch on the tablet, and via the kcm-wacomtablet GUI, and still constantly have this.
(In reply to wolthera from comment #2) > Well, I turned the touch support off using your kritarc entry. Hmmm actually, maybe that is the difference why we still get it with touch disabled? We didn't disable it in Krita, but on the tablet or in its driver. How do I disable it via kritarc? I was looking around in it, nothing about touch.
I disabled it in the kritarc as well, the bug still present, the phantom device is still there.
*** Bug 387998 has been marked as a duplicate of this bug. ***
I forgot this old ticket existed.
Is this still valid? Did anyone experience it after 4.1.7? There were some changes to the tablet code that could've helped.
Theoretically, the bug could have been caused by autosave code. And autosave has been rewritten in May 2018... So the bug might have been fixed already. Could someone check if the bug is still valid in Krita 5? PS: I have checked the bug locally and couldn't reproduce the problem. Autosave doesn't cause any interruptions to the transform tool :(
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!