Bug 459282

Summary: Touch mode is not enabled automatically on a Lenovo convertible laptop
Product: [Plasma] kwin Reporter: Ilya Bizyaev <bizyaev>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 5.25.90   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Ilya Bizyaev 2022-09-17 14:41:28 UTC 
SUMMARY
When I flip my laptop's keyboard back, I do not see any difference that would indicate the touch mode getting enabled.

I tried using D-Bus to check, but for some reason qdbus fails:
$ qdbus-qt5 org.kde.KWin /org/kde/KWin org.kde.KWin.TabletModeManager.tabletMode
Error: org.freedesktop.DBus.Error.UnknownInterface

Then I tried qdbusviewer, and, according to it, tabletModeAvailable is true, but tabletMode is false.

STEPS TO REPRODUCE
Log in to the Plasma Wayland session, ensure that the "Touch Mode" is set to "Automatic" in System Settings, then flip the convertible laptop

OBSERVED RESULT
I get an OSD saying "Touchpad is disabled", which I get on X11 as well; but the touch mode is not activated.

EXPECTED RESULT
The touch mode is activated.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Leap 15.4
KDE Plasma Version: 5.25.90
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.5
Kernel Version: 5.14.21-150400.24.21-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-10210U CPU @ 1.60GHz
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: LENOVO
Product Name: 81TC
System Version: Lenovo Yoga C740-14IML

ADDITIONAL INFORMATION
This is not a regression, it never worked for me, but since Wayland session seems to be doing better overall these days, I'd like it to work at some point :)
Comment 1 Nate Graham 2022-09-22 17:24:34 UTC 
Do the laptop's keyboard and touchpad actually get disabled?
Comment 2 Ilya Bizyaev 2022-09-24 10:38:39 UTC 
Yes, they do actually both get disabled
Comment 3 Nate Graham 2022-09-26 16:26:54 UTC 
That's interesting. It means that your hardware and Libinput are doing the right things, so the issue may be in KWin, yeah.
Comment 4 Ilya Bizyaev 2024-03-16 16:44:48 UTC 
This works for me now