Created attachment 124020 [details] xinput shows two touchpad — HAILUCK and Elantech, but touchpad module in system settings only detects one SUMMARY When my laptop is docked, I tend to use external touchpad and keyboard. However, the dropdown menu for selecting the touchpad I want to configure is disabled even after I've attached the second touchpad. If I plug in touchpad before boot or while laptop is in sleep, settings module will select the HAILUCK touchpad and gray out the 'Device' dropdown. EXPECTED BEHAVIOUR: 'Device' dropdown is not disabled and allows me to choose the touchpad I want to configure. This is a problem because if I plug the touchpad in _after_ boot/wakeup/login, the Elantech touchpad will be selected and I will not be able to configure the right touchpad. STEPS TO REPRODUCE 1. Have a laptop with a touchpad 2. Plug in a second (external, USB) touchpad 3. open touchpad settings OBSERVED RESULT 'Device' dropdown menu is greyed out and I am unable to select which touchpad I want to configure. EXPECTED RESULT 'Device' dropdown menu is not greyed out. I should be able to select my touchpad. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 Kernel Version: 5.3.11-1-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4720HQ CPU @ 2.60GHz Memory: 15,6 GiB of RAM ADDITIONAL INFORMATION n/a See screenshot for bug demonstration.
Correction: I said that settings module will select HAILUCK touchpad if the touchpad is plugged while laptop is in sleep. It did that the first time I tested. It didn't do that the second or third time, so that one might be a fluke. In any case, this is only a minor detail — that doesn't change anything about the core issue: that only the first touchpad (as listed by xinput) is visible in the dropdown
*** Bug 416943 has been marked as a duplicate of this bug. ***
I assume this under X11, please correct me if this in a Wayland session. I don't have a USB touchpad (and this is not common) so I won't be able to reproduce the bug, so bear with me. Do you know if you are using libinput ? I think you are not, because the Xlib code handles only one touchpad which is unfortunate... Wayland should not have this issue. Could you run `kcmshell5 touchpad` or `kcmshell touchpad` (whichever is present and your system) and report the output here to make sure ?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
> I assume this under X11 This is correct. > Do you know if you are using libinput ? > I think you are not, because the Xlib code handles only one touchpad which is unfortunate... I'm 95% sure I do use libinput. In theory, xorg.conf files specify that touchpads should be using libinput. There's two such config files that I have on my system (that I know of): `/etc/X11/xorg.conf.d/30-touchpad.conf` and `/usr/share/X11/xorg.conf.d/40-libinput.conf`. 40-libinput.conf contains: ``` [...] Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" EndSection [...] ``` (Other classes of devices — including tablet, touchscreen and pointer — are also set to use libinput). 30-touchpad.conf contains: ``` Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" Option "Tapping" "on" Option "TappingButtonMap" "lrm" EndSection ``` (This is the entire file) > Could you run `kcmshell5 touchpad` or `kcmshell touchpad` (whichever is present and your system) and report the output here to make sure ? Yes. I get this: ``` Couldn't load plugin: "The shared library was not found." kcm_touchpad: Using X11 backend qml: Touchpad configuration of device '1 : ETPS/2 Elantech Touchpad' opened ``` The output doesn't get any more verbose than that, and `kcmshell --help[-all]` doesn't list any options to convince it to print more. The window still opens normally and all options, in general, work (as in: I can click things).
To clarify — when I say "all options work/are clickable" I mean "all options except the device select dropdown," of course. I apologize for the double post, I should have been more precise in my original comment.
Same for me: Touchpad 'Devices' drop-down disabled with multiple libinput touch devices in X using libinput driver. STEPS TO REPRODUCE 1. Plug >1 libinput touch devices 2. Open System Settings -> Input Devices -> Touchpad 3. Attempt to select alternative device using 'Device' drop-down OBSERVED RESULT 'Device' drop-down is disabled / greyed out. EXPECTED RESULT All compatible devices listed and selectable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Also reported here: https://forum.kde.org/viewtopic.php?f=17&t=166738&p=442399#p442399
Also ran into this issue with a Bluetooth keyboard/touchpad connected to a laptop. Everything works fine on Wayland, I can configure both, but on X11 I do not even have the device selection drop-down. Here is the result of xinput list: ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpad id=20 [slave pointer (2)] ⎜ ↳ Asus TouchPad id=13 [slave pointer (2)] ETPS/2 Elantech Touchpad is the built-in touchpad, Asus TouchPad is the external. Here is the result of xinput list-props 13 and it seems it is using libinput: Device 'Asus TouchPad': Device Enabled (191): 1 Coordinate Transformation Matrix (193): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 libinput Tapping Enabled (328): 0 libinput Tapping Enabled Default (329): 0 libinput Tapping Drag Enabled (330): 1 libinput Tapping Drag Enabled Default (331): 1 libinput Tapping Drag Lock Enabled (332): 0 libinput Tapping Drag Lock Enabled Default (333): 0 libinput Tapping Button Mapping Enabled (334): 1, 0 libinput Tapping Button Mapping Default (335): 1, 0 libinput Natural Scrolling Enabled (336): 0 libinput Natural Scrolling Enabled Default (337): 0 libinput Scroll Methods Available (338): 1, 1, 0 libinput Scroll Method Enabled (339): 1, 0, 0 libinput Scroll Method Enabled Default (340): 1, 0, 0 libinput Click Methods Available (341): 1, 1 libinput Click Method Enabled (342): 1, 0 libinput Click Method Enabled Default (343): 1, 0 libinput Middle Emulation Enabled (344): 0 libinput Middle Emulation Enabled Default (345): 0 libinput Accel Speed (346): 0.000000 libinput Accel Speed Default (347): 0.000000 libinput Accel Profiles Available (348): 1, 1 libinput Accel Profile Enabled (349): 1, 0 libinput Accel Profile Enabled Default (350): 1, 0 libinput Left Handed Enabled (351): 0 libinput Left Handed Enabled Default (352): 0 libinput Send Events Modes Available (313): 1, 0 libinput Send Events Mode Enabled (314): 0, 0 libinput Send Events Mode Enabled Default (315): 0, 0 Device Node (316): "/dev/input/event23" Device Product ID (317): 2821, 34050 libinput Drag Lock Buttons (353): <no items> libinput Horizontal Scroll Enabled (354): 1 Running the same command for the built-in touchpad gives similar results. Running kcmshell5 touchpad give the following: kcm_touchpad: Using X11 backend qml: Touchpad configuration of device '1 : ETPS/2 Elantech Touchpad' opened file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/FormLayout.qml:281:9: QML QQuickItem* (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "preferredWidth" SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-30-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7300HQ CPU @ 2.50GHz Memory: 15,5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 with Max-Q Design/PCIe/SSE2
Is this still happening to anyone in Plasma 6? Either on X11 or Wayland?
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!