Bug 440763

Summary:	Krita 5.0.0 prealpha bug : Unexpected pen pressure failure
Product:	[Applications] krita	Reporter:	stephen <tgdev001>
Component:	Tablets (tablet issues are only very rarely bugs in Krita!)	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	halla
Priority:	NOR
Version First Reported In:	git master (please specify the git hash!)
Target Milestone:	---
Platform:	Other
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description stephen 2021-08-09 01:57:53 UTC

SUMMARY
An unexpected failure about pen pressure detection

STEPS TO REPRODUCE
1. Open Krita and create a new document
2. Keep the windows unfocused for about 8-6 hours
3. Return to Krita and try paint to see if pressure is there

OBSERVED RESULT
you would notice that the pen pressure detection
has failed and pen input is registered as mouse input

EXPECTED RESULT
No pen detection failure due to having Krita not being actively used after 6-8 hours

SOFTWARE/OS VERSIONS
Windows 10 1909

Krita git hash : v5.0.0(11dd91c)

Comment 1 Halla Rempt 2021-08-10 07:40:49 UTC

Sorry, not a Krita bug. Krita does not contain any code whatsoever that handles tablet api's directly. If something breaks it's either a local problem, and OS problem or a driver problem, but it cannot be a bug in Krita's code.

Comment 2 stephen 2021-08-12 10:17:26 UTC

(In reply to Halla Rempt from comment #1)
> Sorry, not a Krita bug. Krita does not contain any code whatsoever that
> handles tablet api's directly. If something breaks it's either a local
> problem, and OS problem or a driver problem, but it cannot be a bug in
> Krita's code.

Please, if it's not a bug, then at least, allow Krita to re-detect the tablet without restarting itself. This issue nevertheless is real and annoying. The fact that I reinstalled my tablet didn't fix it. Once again, this issue is only happening with Krita 5 build, not the 4.x ones. Do something if it can help.

Comment 3 stephen 2021-08-12 10:18:49 UTC

*re-installed my tablet driver...*

Comment 4 Halla Rempt 2021-08-12 13:02:11 UTC

Krita CANNOT detect that, since it's the driver that stops sending tablet events, probably because its context for the krita process got corrupted. A tablet driver keeps data about running applications, and that data can get cleared away, or corrupted, and then it's possible that the driver cannot recreate that data, but all the same, Krita does not get any indication of that state. It just doesn't get tablet events anymore, but that's all.

And PLEASE do not EVER AGAIN change the status of a bug report. Only developers should do that.