Bug 344685

Summary: [HUION] Tablet intermittently unresponsive.
Product: [Applications] krita Reporter: eatthepath
Component: Tablets (tablet issues are only very rarely bugs in Krita!)Assignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: halla
Priority: NOR    
Version First Reported In: 2.9   
Target Milestone: ---   
Platform: Other   
OS: Other   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description eatthepath 2015-03-01 00:05:30 UTC 
At times during drawing, input outside the drawing area will cause issues with the next attempt to draw. In some cases the cursor follows tablet input but the first to draw produces no mark, and then a second attempt works normally. At other times no visible cursor appears even after repeated attempts, and only using mouse input to focus on another window and then return focus to Krita has so far resolved it. Reliable reproduction has been elusive so far. I attempted to rigorously determine causes on the most recent occurrence, and closing the other Krita subwindow that I had open caused the problem entirely, but opening it back up didn't make it start again. If I nail it down any further I'll provide updates. This is not the first occurrence.

Reproducible: Couldn't Reproduce




Windows 8.1 using a Huion Kenting K58 tablet
Comment 1 Halla Rempt 2016-03-14 20:04:29 UTC 
Hi,

Thanks for your report. Unfortunately we don't have test hardware to try and reproduce the issue. But we did rewrite tablet input support for 3.0, so could you give the 3.0 pre-alpha 3 a try? http://files.kde.org/krita/3/windows/krita3-prealpha3-9694dac.zip
Comment 2 eatthepath 2016-05-27 14:30:57 UTC 
(In reply to Boudewijn Rempt from comment #1)
> Hi,
> 
> Thanks for your report. Unfortunately we don't have test hardware to try and
> reproduce the issue. But we did rewrite tablet input support for 3.0, so
> could you give the 3.0 pre-alpha 3 a try?
> http://files.kde.org/krita/3/windows/krita3-prealpha3-9694dac.zip

I don't currently have an win8.1 machine to test on, but the same tablet on a win10 system has been working with the latest 2.9 version without this issue recurring. There might have been some driver updates in the meantime, too.
Comment 3 Halla Rempt 2016-06-16 09:12:55 UTC 
Assuming a driver issue then.