is set, my expectation is that the touchpad gets disabled when I start typing and that it gets re-enable within 1-2 seconds after typing.
Actual behaviour
Sometimes, after typing, the touchpad does not get re-enabled. I cannot use it anymore. I have seen this on a variety of Thinkpad devices. Touchpad there is dead, the red trackpoint however still works. (our users at school get the impression, that the whole notebook has crashed/frozen, until they find the trackpoint being still operative).
Steps to reproduce the behaviour
Use a Thinkpad device (not sure about other devices) and use it for some time. The exact combination of clicks etc. I cannot really tell.
Our workaround then is to set disable-while-typing to false. Then the touchpad stays alive throughout the desktop session.
MATE general version
1.20 (will test with 1.22 once we have that in Debian)
Expected behaviour
When the following override
is set, my expectation is that the touchpad gets disabled when I start typing and that it gets re-enable within 1-2 seconds after typing.
Actual behaviour
Sometimes, after typing, the touchpad does not get re-enabled. I cannot use it anymore. I have seen this on a variety of Thinkpad devices. Touchpad there is dead, the red trackpoint however still works. (our users at school get the impression, that the whole notebook has crashed/frozen, until they find the trackpoint being still operative).
Steps to reproduce the behaviour
Use a Thinkpad device (not sure about other devices) and use it for some time. The exact combination of clicks etc. I cannot really tell.
Our workaround then is to set disable-while-typing to false. Then the touchpad stays alive throughout the desktop session.
MATE general version
1.20 (will test with 1.22 once we have that in Debian)
Package version
1.20.4-1~bpo9+1
Linux Distribution
Debian
Link to downstream report of your Distribution