I have laptop with a faulty keyboard which I disable to avoid accidental presses. > xinput disable "keyboard:AT Translated Set 2 keyboard" Here is what happens: 1) I type command using same faulty keyboard, due to "Disable while typing", touchpad gets disabled temporarily (while I am typing) 2) I finish typing command and press "Enter", the keyboard gets disabled as expected. 3) But the problem here is "touchpad" does not get re-enabled and remains disabled forever too. (because "Disable while typing" flag is still active) Ofcourse I can solve this by using another keyboard to disable the laptop keyboard. But reporting the bug because its error in code flow. i.e. when keyboard is disabled, "Disable while typing" should be disabled too. So that touchpad gets activated again.
is that with the libinput driver or the synaptics driver handling the touchpad? It's going to be a bug in that respective driver, not xinput which is just a tool to toggle properties but doesn't know anything about their contents or behaviours.
Ok its libinput. Changed the component (of this bug report) to Input/libinput. I hope thats correct. Rephrasing my bug report so that it can be better understood. When a keyboard is disabled, it means that typing on that keyboard has also stopped. So touchpad should be activated again, which is not happening and touchpad remains deactivated forever.
https://lists.freedesktop.org/archives/wayland-devel/2017-July/034449.html
commit 9e5d1df4bb2486a1134d3e97e3b889ac46f85f99 Author: Peter Hutterer <peter.hutterer@who-t.net> Date: Tue Jul 11 11:41:15 2017 +1000 touchpad: set keyboard to non-active when the keyboard is removed
fwiw, this will land in libinput 1.9 but also in libinput 1.8.1 when it's released in a week or two. Thanks for the report
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.