I am running Fedora 44 in my Framework Laptop and, pretty much at the same time I upgraded from 43, an UEFI 3.16 update (from 3.09) came through LVFS. After this I am noticing that the trackpad is finally usable on Linux, with a palm rejection behaviour that meets the usual behaviour with other laptops I had in the past.
I’m curious if the UEFI update upgraded anything related to the trackpad, or if this improvement came as part of the kernel upgrade.
Anyway, for Framework staff: thank you for any related work in this regard
For the readers: If you’re reading this as a user I’d like to know if you also noticed a proper trackpad behaviour, or if it is just me!
Versions below!
Framework 13 3rd Gen, Intel i7-1360p
Fedora 44 Workstation with Kernel 6.19.14-300.fc44.x86_64 (Fedora-provided)
It’s been an absolute struggle using my Framework on the go for writing in Vim, and the lack of palm rejection. I was originally planning on holding out for at least a month from upgrading from Fedora 43, waiting for bugs to be ironed out, but this just may push me to upgrade sooner..
Ooh boy if this is a real fix, I hope it ends up in the Framework 12 too - I’ve gotten to the point where I mapped the airplane mode button to enable/disable the trackpad so it will stop misclicking as I type
The worst part about this problem is that it is simultaneously difficult to click where I intend to click with the trackpad. Often I am trying to tap-click on buttons and have to push down hard enough to mechanically click.
So I am getting tap-clicks when I don’t mean to tap-click and not getting tap-clicks when I do mean to tap-click.
I am using CachyOS, not Fedora; it seems Ubuntu has this issue too from other posts.
I dug into the possibility of it being that the keyboard is not set as “internal” in libinput but it is in fact set as “internal” and also DWT (disable while typing) is enabled.
So everything looks as it should, but it just does not work.
Maybe I should just disconnect the trackpad cable for now and use an external mouse–it is that frustrating.
Does anyone have any insight as to what caused this issue and how to fix it?
You don’t have to disconnect a trackpad cable for this, all DE have at least a couple of toggles, one to disable while typing and a second one to disable when an external mouse is connected.
On top of that, you can disable it with a keyboard shortcut. In Gnome you will have to combine it with the following script, and in KDE you have the settings pane down below.
#!/bin/sh
# Detect whether notify-send is installed and set an environment variable
NOTIFY_SELECT_PRESENT=false
which notify-send > /dev/null
if [[ $? -eq 0 ]]; then
NOTIFY_SELECT_PRESENT=true
fi
notify() {
if [[ $NOTIFY_SELECT_PRESENT ]]; then
notify-send --category=pop-up --app-name="Touchpad Toggle" Information "The touchpad has been ${1}"
fi
}
state=$(gsettings get org.gnome.desktop.peripherals.touchpad send-events)
if [ "$state" == "'enabled'" ];then
state='disabled'
else
state='enabled'
fi
gsettings set org.gnome.desktop.peripherals.touchpad send-events ${state}
notify ${state}
It’s also possible that the detection is refined from the side of the desktop environments, I find typing on KDE way more reliable than on Gnome, but it may be my own bias. I am not a good typer anyway.
I use Niri, not exactly a DE (just a window manager). But perhaps I can adapt the script you provided to Niri since I think it can use gnome or KDE-related packages.
