QnA: how did non-functional palm rejection get through?

For context:
On linux, libinput handles palm rejection. There is a mechanism, that will disregard taps on the touchpad while you are typing something. This not working been discussed on the forum before.

Because: this mechanism only works for internal keyboards.

And the fancy new framework16 keyboard is being treated as an external usb device, hence not blocking the touch pad.

The result is: you get mad within 20 minutes of trying to type a bloddy thing.

The issue has now been resolved in libinput., so as it rolls out, the issue will resolve itself in a bit.

However I ask myself: how has this not been caught waaay earlier? It’s not like the framework 16 released yesterday.

1 Like

Somewhere on the forum there is listed a configuration change (not in the BIOS) to make the OS think the keyboard is an internal one instead of external. The OS only thinks it is external because it is USB.

Yes, I have stumbled across that myself too. I just think this should have been realized and resolved by framework before the fw16 got released.

What we really need is a thread where accomplished Linux folk list all these little one liners that tweak the setup, so the Linux Plebs among us have a reference we can turn to without needing to search using doubtful terms we don’t understand. I wouldn’t even know how to search for the one I referenced, I just know I have seen it go past in thread reading.

The problem is libinput does releases very sporadically. I did sneak it into Ubuntu 24.04 ahead of release even without a libinput release. I think @Arthur_Bols did the same for Fedora.

Bug #2058604 “Framework 16 disable touchpad when typing doesn’t …” : Bugs : libinput package : Ubuntu (launchpad.net)