SUMMARY Using multi brush, using ctrl+z to undo ends up with the multi brush tool being selected but not, in that now you cant draw with it until you reselect it even though its shown as the selected tool STEPS TO REPRODUCE 1. draw in multi brush a few things 2. ctrl+z at least twice 3. go to draw again OBSERVED RESULT nothing happens, the pointer moves but no brush strokes come out EXPECTED RESULT you continue drawing as you did in 4.2.1 SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION I have an xp-pen tablet
I can't reproduce this one on macOS. Does this happend if you try to reproduce the bug using the mouse to draw?
Created attachment 121241 [details] video demonstrating issue towards the end once I draw some crap in darker purple, I then ctr+z and undo. while it doesnt show the pointer moving, sigh, but you will see some kinda raindrop effects which are me tapping with the pen on the tablet. Showing that it has moved and it is not reacting
Thank you for looking into it. When using the mouse, the behavior is different however, I have a display tablet as Im an uncoordinated clutz and need the assistance. I have included a video for your viewing. I can confirm that in 4.2.1 the behavior is as expected. However, 4.2.2 seems to lose focus with the tablet.. nothing else changes, other than me upgrading to 4.2.2 and uninstalling and putting 4.2.1 back to go from not working to working again.
I can't reproduce this with the 4.2.2 appimage on Debian 9 using a Wacom Intuos Draw tablet. Do you use appimages? In what way is it different with a mouse? Do you have any similar problems when using the horizontal/vertical mirror tools?
Isnt appimages specific to linux?? Im on windows, running the windows app. So, no, no appimages. The difference with the mouse is the mouse pointer continues to draw, the tablet does not, this happens 100% on my machine as I have uninstalled 4.2.2 3x now, and each time Ive reinstalled it, I see the same behavior, 4.2.1 does not do this.
I cannot reproduce it either, on my Windows 10 Yoga laptop with Lenovo pen. Could you perhaps create a tablet log? See https://docs.krita.org/en/KritaFAQ.html#what-if-your-tablet-is-not-recognized-by-krita for instructions.
The bug report Platform says "Other Linux" so I made an assumption :) I can't reproduce this on Window 10 with the installed or the portable version of 4.2.2 using a variety of settings options. I initially tried this with the 4.2.2 portable version. However, the first time I started the installed 4.2.2, it did lock up as you described and if I tried to switch to the ordinary freehand brush tool it showed the 'waiting for operation to complete' indicator. Task Manager showed that krita was slowly but surely using up all the RAM and when it hit about 15GB Windows gave an error message before it black-screened and I had to press the power button. This crash did not happen again after I rebooted and even after I uninstalled 4.2.2, installed 4.2.1 and then reinstalled 4.2.2. I don't know if it's worthwhile to try the portable .zip 4.2.2 but you might want to try it.
Thanks Ahab for trying. Although as per the video it clearly was ctrl+z that stopped the tablet working although its pointer moved, and it works fine in 4.2.1. As for why the bug picked other, when as you can see in the original text I selected windows 10! The fact you got some form of lockup is interesting.. I have 64gb memory, but reselecting the mutli brush tool it continues on, but as an incompetant artist, I undo a lot and constantly having to reselect the tool was doing my head in. I dont entirely want to reinstall it for about the 6th time... I have to admit.
You don't need to uninstall/reinstall -- that doesn't clear Krita's settings (except if you bought the Windows store version), and you don't need it to test different versions. You can use the portable zip version for that.
When I got the lockup during multibrush use, it took a long time for it to use up all my RAM. I watched it slowly increasing and I think it was about a minute in total. If you have 64GB then it would be interesting to get it into the fault mode and use Task Manager to see if it is consuming RAM as it was with me. I'd repeat what Bound said about the portable zip version. It's so easy and convenient to use and you can have different versions of krita and just use any one you want that you've downloaded and extracted.
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
Is this bugreport still relevant? Does this still happen with 4.2.6?
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!