Bug 368573 - Tablet Pen stops responding for a short period of time after each stroke
Summary: Tablet Pen stops responding for a short period of time after each stroke
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (show other bugs)
Version: 3.0.1
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
: 368860 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-09-11 01:40 UTC by Autumn Lansing
Modified: 2016-11-01 10:43 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Autumn Lansing 2016-09-11 01:40:25 UTC
I have an Intuos 4 tablet. With the latest 3.0.1 version of Krita, the pen stops drawing after making a stroke. The pen still moves on screen, but it doesn't lay down paint and the brush outline is gone. I'm also unable to move the drawing around by holding down the pen's buttons during this time. After a few seconds, the pen starts responding normally again until after making another stroke, when it stops again.

The size of the brush outline also changes while making strokes. It becomes very small when first starting the stroke then grows to a larger size as the stroke continues. It doesn't seem to affect the stroke width on the canvas however, as far as I've seen.

The pen and tablet work fine in 3.0. The problem is only in 3.0.1. I tested with a new rc file just to check if my settings might be to blame and that made no difference. I'm unsure how to debug this, so please let me know what I can do to help.

Reproducible: Always

Steps to Reproduce:
1. Make a stroke with the pen, then lift up the pen from the tablet
2. Start a new stroke. The stroke doesn't appear on the canvas, and the brush's outline doesn't show on screen.
3. Wait a few seconds and try again. It works. Repeat steps.
Comment 1 Halla Rempt 2016-09-15 13:22:35 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?
Comment 2 Autumn Lansing 2016-09-16 03:12:02 UTC
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.
Comment 3 Halla Rempt 2016-09-16 06:08:37 UTC
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...
Comment 4 Autumn Lansing 2016-09-16 16:23:13 UTC
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.
Comment 5 Sven Langkamp 2016-09-17 08:57:08 UTC
If you know how to build Krita from source, you can use git bisect to narrow it down to the change that caused it.
Comment 6 Halla Rempt 2016-09-17 10:04:20 UTC
*** Bug 368860 has been marked as a duplicate of this bug. ***
Comment 7 Halla Rempt 2016-11-01 10:43:50 UTC
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.