Bug 408086

Summary:	Can't change layer visibility, lock/unlock, etc. with tablet pen
Product:	[Applications] krita	Reporter:	Autumn Lansing <autumn>
Component:	Layer Stack	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	ghevan, halla
Priority:	NOR
Version First Reported In:	4.2.1
Target Milestone:	---
Platform:	Appimage
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Autumn Lansing 2019-05-29 20:50:52 UTC

SUMMARY
I just tried the newly-released 4.2.0 and discovered that I can no longer change the visibilty of layers, or lock/unlock them, etc. using my tablet pen. I'm an Intuos4 user. When touching the pen to the icons, they quickly blink off and then back on again. Holding the pen on the icons for several seconds does not have any different effect. The mouse works normally.

STEPS TO REPRODUCE
1. Using an Intuos4 pen, tap the layer visibilty icon.

OBSERVED RESULT
Icon blinks off and then on again. Layer does not change visibility.

EXPECTED RESULT
Layer should change visibility and icon should reflect that.

I've had to go back to 4.1.7 until this is fixed, as I'm constantly fiddling with layers, and it's too disruptive to switch back and forth between pen and mouse.

Comment 1 Autumn Lansing 2019-06-05 18:21:14 UTC

This bug still occurs in 4.2.1

Comment 2 Halla Rempt 2019-06-05 18:24:07 UTC

Hi Autumn,

I'm sorry, but I cannot reproduce the issue yet. Could you perhaps add the output of help->system information for bug reports to this report, and make a tablet log? See https://docs.krita.org/en/KritaFAQ.html#what-if-your-tablet-is-not-recognized-by-krita

Do you have any special configuration set for your tablet?

Comment 3 Autumn Lansing 2019-06-06 01:25:37 UTC

I figured out what was happening. I start the Krita appimage from a script (so I can have a menu entry in my DE) and at one point in the past I had to export the environmental variable QT_XCB_NO_XI2_MOUSE=1 as part of that script in order to get Krita to work correctly. Commenting out that export solved the problem. I imagine it's related to your updated QT version.

Comment 4 vanyossi 2019-06-06 01:44:21 UTC

So its not a bug in krita :D, good thing you found the solution. Marking as resolved