I'm running Fedora-22/KDE on my ThinkPad T510. Ctrl-Y turns off the touchpad on this laptop. But this only works until the next re-boot.
In System Settings=>Hardware=>Input Devices=>Touchpad there is an option "Enable/Disable Touchpad" which I assume is meant to toggle the touchpad on and off. On my machine it seems to have no effect. Have I misunderstood its purpose? Or does one have to install some other package for it to work?
As I recall, there was a straightforward option "Disable touchpad" in Fedora-21/KDE, which worked perfectly.
On Wed, Aug 19, 2015 at 8:07 PM, Timothy Murphy gayleard@eircom.net wrote:
I'm running Fedora-22/KDE on my ThinkPad T510. Ctrl-Y turns off the touchpad on this laptop. But this only works until the next re-boot.
In System Settings=>Hardware=>Input Devices=>Touchpad there is an option "Enable/Disable Touchpad" which I assume is meant to toggle the touchpad on and off. On my machine it seems to have no effect.
The options available are "Disable touchpad while typing" and in connection with it "Disable taps and scrolling only". You can also set the shortcut to enable/disable touchpad on the same tab. Apart from that, I don't think there is a global "disable touchpad altogether" option.
Have I misunderstood its purpose? Or does one have to install some other package for it to work?
Fedora 22 uses the newer libinput touchpad driver, you can uninstall it and install xorg-x11-drv-synaptics to configure as in Fedora 21.
As I recall, there was a straightforward option "Disable touchpad" in Fedora-21/KDE, which worked perfectly.
-- Timothy Murphy
Hope that helps.
On Wed, Aug 19, 2015 at 2:33 PM, Rajeesh K V rajeeshknambiar@gmail.com wrote:
Fedora 22 uses the newer libinput touchpad driver, you can uninstall it and install xorg-x11-drv-synaptics to configure as in Fedora 21.
Do we know why this transition was made from xorg-x11-drv-synaptics to libinput? I've read from a number of users frustration over the fact that libinput doesn't provide the level of configurability that xorg-x11-drv-synaptics provided, which effectively makes using a touchpad an exercise in frustration. In other words, this is a serious regression. As an example, the KDE Settings contains many parameters, almost all of which are grayed out when running with libinput.
-Adam Batkin
On Qua, 2015-08-19 at 15:02 -0400, Adam Batkin wrote:
On Wed, Aug 19, 2015 at 2:33 PM, Rajeesh K V rajeeshknambiar@gmail.com wrote:
Fedora 22 uses the newer libinput touchpad driver, you can uninstall it and install xorg-x11-drv-synaptics to configure as in Fedora 21.
Do we know why this transition was made from xorg-x11-drv-synaptics to libinput? I've read from a number of users frustration over the fact that libinput doesn't provide the level of configurability that xorg-x11-drv-synaptics provided, which effectively makes using a touchpad an exercise in frustration. In other words, this is a serious regression. As an example, the KDE Settings contains many parameters, almost all of which are grayed out when running with libinput.
we got some bugzilla reports
https://bugzilla.redhat.com/show_bug.cgi?id=1228691
https://bugzilla.redhat.com/show_bug.cgi?id=1225579
-Adam Batkin _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
You have to use libinput at the moment for Wayland, gnome and KDE are both transitioning to libinput. As far as configurability goes: its not meant to be as configurable. Synaptics exposed every possible control knob, despite the fact that some of them were completely untested / known to be broken. AFAIK, libinput is going the route of "Sane defaults, expose what we know works and what we actually support changing." Instead of "Change ALL THE THINGS!"
Yes there's still some teething problems but those are being worked out. Libinput's maintainer has been pretty good, I think anyway, about bug reports and communicating reasons / thought processes on his blog. On Aug 19, 2015 3:02 PM, "Adam Batkin" adam@batkin.net wrote:
On Wed, Aug 19, 2015 at 2:33 PM, Rajeesh K V rajeeshknambiar@gmail.com wrote:
Fedora 22 uses the newer libinput touchpad driver, you can uninstall it and install xorg-x11-drv-synaptics to configure as in Fedora 21.
Do we know why this transition was made from xorg-x11-drv-synaptics to libinput? I've read from a number of users frustration over the fact that libinput doesn't provide the level of configurability that xorg-x11-drv-synaptics provided, which effectively makes using a touchpad an exercise in frustration. In other words, this is a serious regression. As an example, the KDE Settings contains many parameters, almost all of which are grayed out when running with libinput.
-Adam Batkin _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
On Wed, Aug 19, 2015 at 3:51 PM, Eric Griffith egriffith92@gmail.com wrote:
You have to use libinput at the moment for Wayland, gnome and KDE are both transitioning to libinput. As far as configurability goes: its not meant to be as configurable. Synaptics exposed every possible control knob, despite the fact that some of them were completely untested / known to be broken. AFAIK, libinput is going the route of "Sane defaults, expose what we know works and what we actually support changing." Instead of "Change ALL THE THINGS!"
Yes there's still some teething problems but those are being worked out. Libinput's maintainer has been pretty good, I think anyway, about bug reports and communicating reasons / thought processes on his blog.
Is there a danger in exposing all of the parameters like xorg-x11-drv-synaptics? Who says that your "sane defaults" will work for me? There are so many different hardware combinations (and developers may not have access to many of them) that it will be impossible to set them all up properly (i.e. we can all file bugs, but most will likely never be fixed, and even if they are, we are left with unusable systems in the interim).
I'd wager that a good number of people on this (KDE) list are here because the Gnome folks thought that their "sane defaults" would work for everyone (hint: they don't). I'm tired of having to explain/justify why some hard-coded default doesn't work for me and should be configurable, only to have each one of my points (my *opinions*) being dismissed by others.
-Adam Batkin
There's a general thought that if you expose a control knob for it then people will assume that changing it is a supported action and if it doesn't work as expected then that's a bug to be fixed because all configurations are equal and should be equally supported. People used this mentality to come up with very strange synaptics config files that were not supported at all, but they would show up anyway screaming about support.
Post from the libinput maintainer ON libinput vs synaptics: https://lwn.net/Articles/612960/
It may not address all of your concerns but I hope it addresses the mentality issue. On Wed, Aug 19, 2015 at 3:51 PM, Eric Griffith egriffith92@gmail.com wrote:
You have to use libinput at the moment for Wayland, gnome and KDE are both transitioning to libinput. As far as configurability goes: its not meant
to
be as configurable. Synaptics exposed every possible control knob, despite the fact that some of them were completely untested / known to be broken. AFAIK, libinput is going the route of "Sane defaults, expose what we know works and what we actually support changing." Instead of "Change ALL THE THINGS!"
Yes there's still some teething problems but those are being worked out. Libinput's maintainer has been pretty good, I think anyway, about bug reports and communicating reasons / thought processes on his blog.
Is there a danger in exposing all of the parameters like xorg-x11-drv-synaptics? Who says that your "sane defaults" will work for me? There are so many different hardware combinations (and developers may not have access to many of them) that it will be impossible to set them all up properly (i.e. we can all file bugs, but most will likely never be fixed, and even if they are, we are left with unusable systems in the interim).
I'd wager that a good number of people on this (KDE) list are here because the Gnome folks thought that their "sane defaults" would work for everyone (hint: they don't). I'm tired of having to explain/justify why some hard-coded default doesn't work for me and should be configurable, only to have each one of my points (my *opinions*) being dismissed by others.
-Adam Batkin _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Eric Griffith wrote:
There's a general thought that if you expose a control knob for it then people will assume that changing it is a supported action and if it doesn't work as expected then that's a bug to be fixed because all configurations are equal and should be equally supported. People used this mentality to come up with very strange synaptics config files that were not supported at all, but they would show up anyway screaming about support.
I just want to turn the touchpad off - as I imagine do many ThinkPad owners who use the ThinkPad pointer as a alternative to the touchpad.
Surely that could not cause any of these philosophical difficulties?
Timothy Murphy wrote:
I just want to turn the touchpad off - as I imagine do many ThinkPad owners who use the ThinkPad pointer as a alternative to the touchpad.
That's actually the one option whose removal is not libinput's fault, but the new kcm_touchpad's, isn't it?
The keyboard shortcut which you can configure in the KCM or the system tray applet can be used to manually disable the touchpad entirely.
Kevin Kofler
On Wed, Aug 19, 2015 at 5:28 PM, Eric Griffith egriffith92@gmail.com wrote:
There's a general thought that if you expose a control knob for it then people will assume that changing it is a supported action and if it doesn't work as expected then that's a bug to be fixed because all configurations are equal and should be equally supported. People used this mentality to come up with very strange synaptics config files that were not supported at all, but they would show up anyway screaming about support.
Okay, so is the ability (or lack thereof) to adjust the scroll speed a bug in libinput or KCM? And what's the best way to get a bug like that fixed (since I know I'm not the only one that it affects, and it makes my touchpad effectively useless for scrolling)
Thanks,
-Adam Batkin
-
Adam Batkin -
Eric Griffith -
Kevin Kofler -
Rajeesh K V -
Rex Dieter -
Sérgio Basto -
Timothy Murphy