Summary: | Tablet Pen stops responding for a short period of time after each stroke | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Autumn Lansing <autumn> |
Component: | Tablets (tablet issues are only very rarely bugs in Krita!) | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | halla, pmanims, sven.langkamp |
Priority: | NOR | ||
Version: | 3.0.1 | ||
Target Milestone: | --- | ||
Platform: | Appimage | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Autumn Lansing
2016-09-11 01:40:25 UTC
Hi Autumn, Thanks for your report. I haven't been able to reproduce yet -- except that on gnome, all my applications tend to hickup regularly. Which desktop environment are you using? I use Awesome Window Manager. I tested in Cinnamon, and it works fine in that DE, but not in Awesome. Something new I noticed as well: I have a multi-monitor setup, and if I swipe the pen to the other monitor and then back to Krita again, I can make a new stroke. That seems to break whatever is locking up the pen. It locks up again after making that new stroke though. In that case, I'm afraid that it's a bug in the window manager, not in Krita. The window manager is responsible for sending the events to the Krita window, and krita only can do something with the events once it gets them... Yes, but the problem only came about with 3.0.1. 3.0 works perfectly. Something changed in Krita that's causing the skipping. The tablet and pen work fine in all other apps I've tested them in, such as GIMP. It's only in Krita 3.0.1 that there's a problem, so something in the way that Krita handles events in its latest version is creating the issue. Aside from breaking the lock when moving the pen to the other monitor, the lock is also broken if another app is brought into focus on the same monitor, so as long as Krita is in focus, it keeps the pen locked up for around five seconds before releasing it. What changed in Krita's handling of pen events between versions that might cause this? If I file this with the Awesome team, they may not have the equipment to test it. If the problem is on their end, then I need to be able to point them in the right direction. As it is, Krita seems to be doing something different from all other apps, and I fear they may kick the bug back to you. I'm a developer, though not very experienced with C++, which I assume Krita is written in, but I'd be happy to look into the bug further if I knew where to start. If you know how to build Krita from source, you can use git bisect to narrow it down to the change that caused it. *** Bug 368860 has been marked as a duplicate of this bug. *** I've installed and tested with awesome myself, and I cannot reproduce it. I haven't got any way to take action on this bug report anymore, I'm afraid. |