I’ve been having issues where the touchpad and possibly the touchscreen get in conflict with each other and it goes into a state where the laptop isn’t usable without a restart. I have tried reseating the keyboard, but this doesn’t seem to be a permanent fix.
I don’t really know how to diagnose this further. I’m currently running fedora on mine.
Does the cursor jump around a lot and the trackpad gradually becomes unusable? If so, a simple sleep/resume should do the trick and fix it.
When it occurs, it seems to persist after a sleep.
Also i’ll hit one of these two issues when it occurs:
Quite strange. Hope your issue gets fixed soon
I don’t know if your symptoms match mine but sometimes the touchscreen seems to be sending a lot of inputs which effectively pins my cursor to one specific position on the screen. I figured out that if I disable the touchscreen with xinput the touchpad works again. (use xinput list to identify your touchscreen and xinput disable <id>)
Edit: It seems fine to enable the touchscreen again afterwards.
Seems to be the same thing
I have experienced the same issue. However I found disabling touch screen via KDE as viable option until I need to use touchscreen (rarely).
Are you using KDE or Gnome? I’m daily driving mine with KDE and I’ve had few instances where it got into some weird state where touchpad tap-to-click didn’t work but only physical click worked (I discovered I could sometimes fix it by toggling “disable touchpad when typing”) or I could not move, close or minimize windows using a mouse cursor. Sometimes I can fix it temporarily by switching to tablet mode and back. But the most reliable way of fixing that is logging out and logging in again. Maybe you could try doing that instead of rebooting and then you can be sure it’s not a hardware problem.
But now thinking about it it hadn’t happened for quite a lot of time sooo… I don’t know.
Win 11 here and I’m seeing the same thing.
I have had odd touchpad issues for a couple of months, so today I did a fresh install of Win 11. Downloaded the driver pack and the issue was present within 30 min of the fresh install.
Cursor vanishes, touchpad is non responsive unless I ctrl-alt-delete, then the touchpad will work again for 5-20 min.
I disabled the touchscreen and that appears to have fixed the problem but, of course, the touchscreen doesn’t work.
I have a trackpad issue too; I’m using KDE.
I wrote a script that restarts the trackpad’s I2C controller; I use it when it crashes, and it fixes the problem about half the time…
#!/usr/bin/env bash
# Reset the I2C controller used exclusively by the Framework touchpad.
set -euo pipefail
readonly DEVICE="0000:00:19.0"
readonly PCI_DRIVER="/sys/bus/pci/drivers/intel-lpss"
readonly I2C_DEVICE="i2c-PIXA3854:00"
if (( EUID != 0 )); then
exec sudo -- "$0" "$@"
fi
if [[ ! -d "/sys/bus/pci/devices/$DEVICE" || ! -d "$PCI_DRIVER" ]]; then
printf 'Controleur I2C du trackpad introuvable.\n' >&2
exit 1
fi
if [[ ! -L "/sys/bus/pci/devices/$DEVICE/driver" ]]; then
printf 'Le controleur I2C n est pas lie a son pilote.\n' >&2
exit 1
fi
# Always rebind the controller if the script is interrupted after unbinding it.
rebind_needed=1
cleanup() {
if (( rebind_needed )); then
printf '%s\n' "$DEVICE" > "$PCI_DRIVER/bind" 2>/dev/null || true
fi
}
trap cleanup EXIT
printf 'Reinitialisation du controleur I2C du trackpad...\n'
printf '%s\n' "$DEVICE" > "$PCI_DRIVER/unbind"
sleep 2
printf '%s\n' "$DEVICE" > "$PCI_DRIVER/bind"
rebind_needed=0
trap - EXIT
sleep 3
if [[ -e "/sys/bus/i2c/devices/$I2C_DEVICE" ]]; then
printf '%s\n' "$I2C_DEVICE" > /sys/bus/i2c/drivers_probe || true
fi
sleep 1
if grep -q 'PIXA3854:00 093A:0239 Touchpad' /proc/bus/input/devices; then
printf 'Trackpad detecte.\n'
else
printf 'Le controleur a ete relance, mais le trackpad reste indisponible.\n' >&2
exit 2
fi
My cursor problems disappeared when i moved my framework from my bed(soft surface) to my desk (hard surface)
Yes, I also noticed that it was linked to the position or pressure on the laptop, or the way the bottom casing is bent.