You are not logged in.
Hello everyone.
I complained about adopting libinput as default library for pointing devices, synaptics was better and more customizable.
Anyway I found a proper configuration for my touchpad setting acceleration speed option at -0.5 in a custom xorg config file. This option accepts values between -1 and +1, the default is 0 and it's too faster.
The problem is Plasma Desktop. When I start the system and get into sddm, I detect the right speed of the pointer, which means the option has been set properly.
But whenever I start any user Plasma session, the pointer is too fast and "xinput list-props" command reports that acceleration speed has been reset to 0.
So I tried to change it from system settings. The option is regulated by a controller on an horizontal bar. The controller is on the left side and its value is 0, so I cannot move it to the left and cannot set -0.5 value.
In substance, Plasma can only set values above 0 but I need -0.5. This is a bug because libinput can expect also values below 0.
I tried also to manually modify touchpadrc file in config home directory setting -0.5 value, but when I restart the session the option is reset to 0. If I set 0.5 or another value above 0, the option is set properly instead and I can see it from xinput command.
So, how can I prevent Plasma from changing xorg configuration at start?
Offline
Does it help if you disable the touchpad service? System Settings -> Start and Quit -> Background Services -> Remove the Touchpad checkbox ? And fwiw have you considered reporting a bug/feature request? From what I know libinput support has been/is being extended for plasma 5.9 but I don't know if the ability to set negative values has been added.
Offline
Does it help if you disable the touchpad service? System Settings -> Start and Quit -> Background Services -> Remove the Touchpad checkbox ?
No, the value is reset to 0 anyway.
And fwiw have you considered reporting a bug/feature request? From what I know libinput support has been/is being extended for plasma 5.9 but I don't know if the ability to set negative values has been added.
I wrote on their forum and I'm waiting for a reply.
Offline
https://bugs.kde.org/show_bug.cgi?id=357749 Here's a bug report, you might want to follow that
Offline
https://bugs.kde.org/show_bug.cgi?id=357749 Here's a bug report, you might want to follow that
Thanks.
Well, submitted one year ago and not fixed yet, it's absurd.
Offline
Welcome to KDE :-)
Here is a KCM for configuring mouse and touchpad that is far superior to the one currently in PLASMA. But I think the original author may have given up trying to get it into KDE after a bunch of design disagreements. But it works fairly well.
https://aur.archlinux.org/packages/kcm- … vices-git/
https://forum.kde.org/viewtopic.php?f=285&t=127056
Last edited by blahhumbug (2017-01-28 15:37:22)
Offline
Welcome to KDE :-)
Here is a KCM for configuring mouse and touchpad that is far superior to the one currently in PLASMA. But I think the original author may have given up trying to get it into KDE after a bunch of design disagreements. But it works fairly well.
https://aur.archlinux.org/packages/kcm- … vices-git/
https://forum.kde.org/viewtopic.php?f=285&t=127056
Mmh... last update is one year and a half ago, not sure it's a good idea, maybe things will break with further plasma updates.
I adopted a temporary solution adding an executable script with "xinput set-prop 11 285 -0.5" command in ~/.config/autostart-scripts.
It sets -0,5 value in acceleration speed option at the start of plasma session. I get the proper speed now, but the bug is not fixed yet.
Last edited by digitalone (2017-01-29 17:50:58)
Offline