A few years ago during GSoC I wrote a new KCM for touchpads/mouses/whatever libinput handles: https://github.com/amezin/pointing-devices-kcm http://amezin.github.io/kde/gsoc/2015/08/12/gsoc-update.html It's still not integrated into Plasma. But people are using it (see comments in https://aur.archlinux.org/packages/kcm-pointing-devices-git/) and even reporting that it works better than old touchpad kcm. Could somebody try to integrate it? It seems that KWin on Wayland has a bit different D-Bus interface than I expected, but otherwise it should just work. I'm not using Plasma anymore so can't even test it
Today we already have equivalent Libinput support for mice on X11 on Wayland, and Touchpads on Wayland, but our X11 touchpad KCM is still really old and crusty and doesn't expose Libinput-specific features. That's the only missing piece, and it's quite sorely needed. At this point I unfortunately don't see this work getting merged because we've diverged so much. :( But help getting proper Libinput touchpad support on X11 would be much appreciated. I'm not sure of the history here (it was before my time), but it's a shame this never went in. Who was your mentor? Can you fill in some of the blanks regarding why this never got merged?
(In reply to Nate Graham from comment #1) > I'm not sure of the history here (it was before my time), but it's a shame > this never went in. Who was your mentor? Can you fill in some of the blanks > regarding why this never got merged? Is it really relevant? This works even if it looks old. It's way better than that useless default kcm touchpad with tons of options that only works with old synaptic driver. Please, merge it. It doesn't change nothing for me because I already have it thanks to AUR, but other people using libinput without Wayland needs it on other distributions.
(In reply to Nate Graham from comment #1) > Today we already have equivalent Libinput support for mice on X11 on > Wayland, and Touchpads on Wayland, (...) But is it really works? Arch Linux (kernel 4.20.3 /screens below from linux-zen, but it's not relevant/, KF5 5.53, Plasma 5.14.90): - for "Mouse" - "No pointer device found" see: https://i.imgur.com/4AGgoSh.png Yes, it's laptop without mouse connected, but on X11, mouse is founded and I can do something with it) - for "Touchpad" - all options are greyed - see: https://i.imgur.com/nbj3Ari.png and touchpad is not configurable at all on Wayland with libinput
Sorry, KF5 is 5.54 and take a look at: https://bugs.kde.org/show_bug.cgi?id=395351 and my comment: https://bugs.kde.org/show_bug.cgi?id=395351#c22 So Touchpad settings from systemsettings doesn't works at all, but from kcmshell5 touchpad - works very good.
Pawel, that's not related to this request.
I'm really sad about current situation on Plasma regarding mouse configuration while using libinput. This is what current Plasma KCM provides: https://i.imgur.com/EO2GR1N.png And this is how pointing-devices-kcm looks like https://i.imgur.com/9gmxTkq.png But even that while looks nicer does provide a lot less configuration options than was possible with evdev. For example I can't configure mouse scrolling speed :(
(In reply to Dāvis from comment #6) > But even that while looks nicer does provide a lot less configuration > options than was possible with evdev. For example I can't configure mouse > scrolling speed :( That's a (legitimate) gripe about Libinput, not our configuration UI for it.
(In reply to Nate Graham from comment #7) > (In reply to Dāvis from comment #6) > > But even that while looks nicer does provide a lot less configuration > > options than was possible with evdev. For example I can't configure mouse > > scrolling speed :( > That's a (legitimate) gripe about Libinput, not our configuration UI for it. Yeah I read about it: https://gitlab.freedesktop.org/libinput/libinput/issues/185 It needs to be implemented in Qt and Plasma needs to have configuration options.
Indeed. I've filed these bugs to track that: - No way to configure Libinput touchpad scroll speed: https://bugs.kde.org/show_bug.cgi?id=403843 - No way to configure Libinput mouse scroll speed: https://bugs.kde.org/show_bug.cgi?id=403842
Current status of this bug report is WAITINGFORINFO. What info are you waiting for? Can you explain me that? This are my touchpad settings on Plasma: https://imgur.com/a/edLyDVJ Tons of useless options, most of all greyed out and others half-working (acceleration that supports only positive values rather than 1- to 1 range). It's build for synaptics, but do you know it's deprecated from years? Pointing devices KCM works, it only needs to be well implemented to apply settings at startup. In my current status, I have to apply touchpad configurations with xinput from a script executed at Plasma startup. It's quite a shame for a DE like Plasma. It's years you can't do a touchpad KCM for X11, maybe you don't have time or people to do it, I understand, but if there's something that just works, what are you waiting for? Someone to write another touchpad KCM starting from zero? It's pointless. It's more reasonable that you just merge pointing devices and apply settings at startup and the problem is solved.
(In reply to Giusy Digital from comment #10) > Current status of this bug report is WAITINGFORINFO. What info are you > waiting for? Can you explain me that? I'm waiting for the reported (Alexander Mezin) to shed some light on the history here, regarding why his work never got merged.
Okay, let's wait. Meanwhile, while we're waiting, I'd like to tell you my opinion. Maybe the reason it's the same of wasting time on writing a new volume manager plasma-pa exclusively for Pulseaudio when you already have a working volume manager KMix suitable for both alsa and Pulseaudio. So I think you will waste other time waiting to write from zero a new touchpad KCM for X11 rather than adapt an already usable KCM which only issue is not applying its config at startup. I think Plasma is a good DE, but I can't understand some of choices you developers made. Fortunately system configurations can be applied even without the help of user interface, but if I use a DE and I'm forced to use the shell or write config in a text file, you made something wrong.
Thanks for sharing your opinion. Though you may be frustrated with this situation (as I am too), please keep it polite. See https://community.kde.org/Get_Involved/Bug_Reporting#Bug_tracker_etiquette I feel your pain myself. I have a similar startup script and am annoyed that our existing X11 touchpad KCM is not very good for Libinput. And I believe that improving our Libinput touchpad input device handling on X11 is a top-five-issues strategic necessity. I think we are in agreement there. If this KCM was never landed, I would like to know the reason why, before we say, "screw it, we need it, no matter the issues!" Did it have unresolved critical bugs? Was its code an unmaintainable mess? Did the GSoC mentor lose interest and forget? There must have been some reason, and that reason is important.
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!
Alexander, can you answer my questions?
Work continues on the existing KCMs, and we just landed libinput touchpad click method today. That, plus the the absence of further information from Alexander or anyone else regarding why this work was never merged, makes me think that it is unlikely to happen. :(
Support for configuring Libinput-using touchpads on X11 has been merged for Plasma 5.16. So there is no longer any need for this.