Bug 457166

Summary: Touchpad doesn't work in Wayland session
Product: [Plasma] kwin Reporter: Dr. Prepper <crib.moneywise773>
Component: libinputAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: nate, xaver.hugl
Priority: NOR Keywords: wayland-only
Version First Reported In: 5.25.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Output of sudo libinput debug-events while using the touchpad
kwin debug info for input devices

Description Dr. Prepper 2022-07-26 17:31:52 UTC
SUMMARY
Touchpad does not work. It began in 5.24.4 and still happens in 5.25.3 I've had to use the X11 session as a workaround.

The laptop is a Yoga 6 13ARE05.


STEPS TO REPRODUCE
1. Boot to login screen
2. Select Wayland session
3. Login
4. Attempt to move mouse cursor with trackpad

OBSERVED RESULT

Mouse cursor does not move with touchpad input. Touchpad buttons do not cause any action. Touchscreen functions as expected.

EXPECTED RESULT

Touchpad causes mouse cursor to move and touchpad buttons are accepted as input.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  openSUSE Tumbleweed 22020719 Kernel 5.18.11
(available in About System)
KDE Plasma Version:  5.25.3
KDE Frameworks Version:  5.96
Qt Version:  5.15.5

ADDITIONAL INFORMATION

Output of hwinfo --all

80: PS/2 00.0: 10500 PS/2 Mouse
  [Created at input.249]
  Unique ID: AH6Q.Jng17+PwDNA
  Hardware Class: mouse
  Model: "MSFT0002:00 04F3:31AA Touchpad"
  Vendor: 0x04f3 
  Device: 0x31aa "MSFT0002:00 04F3:31AA Touchpad"
  Compatible to: int 0x0210 0x0001
  Device File: /dev/input/mice (/dev/input/mouse1)
  Device Files: /dev/input/mice, /dev/input/mouse1, /dev/input/event3, /dev/input/by-path/platform-AMDI0010:00-event-mouse, /dev/input/by-path/platform-AMDI0010:00-mouse
  Device Number: char 13:63 (char 13:33)
  Driver Info #0:
    Buttons: 1
    Wheels: 0
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=no, avail=yes, need=no, active=unknown
Comment 1 Dr. Prepper 2022-12-25 21:42:45 UTC
Still a problem on 5.26.4

Is there anything else I can provide to help?

Thanks.
Comment 2 Vlad Zahorodnii 2023-01-06 09:30:10 UTC
Run

  sudo libinput debug-events

use your touchpad, press Ctrl-C, and then attach libinput's output to this bug report
Comment 3 Vlad Zahorodnii 2023-01-06 09:30:27 UTC
.
Comment 4 Dr. Prepper 2023-01-06 21:51:58 UTC
Created attachment 155080 [details]
Output of sudo libinput debug-events while using the touchpad
Comment 5 Dr. Prepper 2023-01-09 20:33:22 UTC
.
Comment 6 Zamundaaa 2023-01-11 13:00:03 UTC
Please open the kwin debug console (by typing "kwin" in krunner) and check if the touchpad is enabled under the input devices tab
Comment 7 Dr. Prepper 2023-01-11 19:00:57 UTC
Created attachment 155218 [details]
kwin debug info for input devices

The touchpad isn't enabled according to the kwin debug input devices section.
Comment 8 Zamundaaa 2023-01-11 20:05:40 UTC
If you go into the touchpad settings in system settings, is it enabled there? If not, does enabling it make it work?
Comment 9 Dr. Prepper 2023-01-11 20:17:17 UTC
(In reply to Zamundaaa from comment #8)
> If you go into the touchpad settings in system settings, is it enabled
> there? If not, does enabling it make it work?

That worked! I'm not sure why the touchpad was disabled for wayland sessions.

I apologize for not looking there before.
Comment 10 Zamundaaa 2023-01-11 20:43:49 UTC
thanks. Not sure why it would be disabled by default either, but unless more people experience the same issue I think we can close this bug