SUMMARY I use Wacom Intuos 5 and Krita freezes when I usually switch between brush engines, fro example from cloning to blender, I mean there is no cursor movement, palette popup, etc. I found out some workaround, sometime it's solvable if I click with the mouse right button or switch between Trilinear Filtering and High Quality Filtering for example. However there are cases when I have to save the document and restart Krita, in this case there is no palette popup, only a right click menu when I click with the mouse right button. Although I wasn't able to find other similar report here, I hope there is already some info and experiences by others about this problem. STEPS TO REPRODUCE 1. Connect drawing pad, in my case Wacom Intuos 5 2. Fire up krita with some stuff and try to use cloning, blender, airbrush by switching between them using your drawing pad. 3. Try to solve the freezing with your mouse or switching between Scaling Mode. OBSERVED RESULT Krita freezes, no cursor movement, palette popup. EXPECTED RESULT No freeze, flawless work. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.15 (available in About System) KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.15.0-45-generic ADDITIONAL INFORMATION X.Org X server -- Wacom input driver version: 1:0.36.1-0ubuntu1
I too am encountering this. After switching between brushes or tools (for me, always with the right-click menu), the canvas will freeze. Just the canvas though. I can still save and change tools, but I can't draw. The cursor won't even appear when I mouse over the canvas. I can only fix this by closing and reloading. Mac OS 10.14 Krita: 4.1.7 Wacom Intuos S
This might be fixed in master, can you check the latest nightlies? (They're named 'krita next' on the download page.)
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!
There is no Mac version for Krita next. The other guy would have to do this.
No, the original reporter will have to test. We're working on nightlies for macOS, and have the scripts ready, but they haven't been put in production.
Oh, yep, that's great. What have to test...? Really? I think any one or 'even' you guys should be able to test it too with a miserable wacom pad and a simple neon install, lol. Ridiculous, sorry maybe I got tired today and I just lost my temper but let me put it simple. Don't close bug reports after 1.5 month if the waiting time for any reaction is the very same time if not a lot more. Don't get me wrong, I understand the policy and rules however developments should consider the fact that reporter may got tired to check given report after more then a month waiting. Also I have no time neither. I try to report back soon as I got a little time. Otherwise if it'll be closed then let me know if I should open an other one or whatever.
Ok, it seems promising now. Sorry for my previous feedback, I'm undeniably hothead lol. Sometimes it's still freezing a little with 4.1.8, mostly it's not so it seems there is already an improvement too. I got no wacom related freezing with downloaded krita-4.2.0-pre-alpha-4e2b1b5-x86_64.appimage at all. I have to note I'm not sure these freezing issues on my system related to Krita however it really could be something with Nvidia too. I mentioning this because recently I changed a significant settings, I just turned off composition pipeline and got Nvidia to work with triplebuffer instead. Probably it's not related, I thought just in case worth noting such a change. So basically it works great for me now. Thanks
Okay, then it is resolved by the tablet bugfixes of 4.2