Linux Touchpad Gestures Not Working Wayland: Proven Fix (2026)

Linux touchpad gestures not working wayland is a common frustration for users switching to Wayland. You expect three-finger swipes, pinch-to-zoom, and other multi-touch gestures to work seamlessly, but they are unresponsive or behave incorrectly.

When linux touchpad gestures not working wayland occurs, the issue typically stems from libinput configuration, desktop environment limitations, or missing drivers. This comprehensive guide provides proven methods to restore full touchpad gesture functionality on GNOME, KDE Plasma, and other Wayland compositors.

1. Root Cause

When linux touchpad gestures not working wayland occurs, several factors may be responsible. The most common cause is that libinput, the input handling library for Wayland, is not properly configured or installed. On Wayland, libinput is the standard driver for touchpads and touchscreens[reference:0]. Unlike X11, there is no centralized libinput configuration file for Wayland; configuration depends on your desktop environment’s support[reference:1].

Another major cause is desktop environment-specific limitations. On KDE Plasma Wayland, gestures are hardcoded and do not allow customization[reference:2][reference:3]. This blocks usage of tools like touchegg and libinput-gestures[reference:4]. On GNOME, there are known bugs where pinch gestures only work when the cursor is over the desktop or top bar, not over application windows[reference:5][reference:6]. GNOME 49 users may need to upgrade to GNOME 49.3 for gesture extensions to work properly[reference:7].

Missing or outdated drivers can also cause issues. While libinput is typically installed as a dependency of any Wayland graphical environment, the libinput-tools package containing diagnostic tools may not be installed[reference:8]. Additionally, some users may need the xorg-xinput package for runtime configuration[reference:9].

2. Verify Touchpad Detection with libinput

The first step to fix linux touchpad gestures not working wayland is to verify your touchpad is detected by libinput. This confirms the hardware is recognized at the system level.

# Install libinput-tools if not already installed
sudo apt install libinput-tools        # Ubuntu/Debian
sudo pacman -S libinput-tools          # Arch
sudo dnf install libinput-tools        # Fedora

# List input devices
libinput list-devices

Look for your touchpad in the output. The “Capabilities” line tells you what features the hardware supports[reference:10]. If your touchpad is listed, libinput is working. If not, the touchpad may be disabled in BIOS or require additional drivers[reference:11]. According to the Arch Linux Wiki, libinput should be installed as a dependency of any Wayland graphical environment[reference:12].

Outcome: Verifying touchpad detection confirms whether the issue is at the hardware/driver level or the desktop environment level.

3. Enable Tap-to-Click in Settings

Some gesture issues are related to tap-to-click settings. Ensuring this is enabled can resolve linux touchpad gestures not working wayland for basic gestures[reference:13].

Settings → Mouse & Touchpad → Tap to Click → Toggle ON

On GNOME, navigate to Settings > Mouse & Touchpad and verify that “Tap to Click” is enabled. On KDE Plasma, go to System Settings > Input Devices > Touchpad and enable “Tap to click”. While this setting primarily affects tapping, it can influence how the touchpad interprets multi-touch gestures[reference:14].

Outcome: Enabling tap-to-click may resolve basic gesture recognition issues.

4. Install/Update libinput and Drivers

Outdated libinput versions can cause linux touchpad gestures not working wayland. Updating to the latest version ensures you have the latest gesture support and bug fixes.

# Update system packages
sudo apt update && sudo apt upgrade   # Ubuntu/Debian
sudo pacman -Syu                      # Arch
sudo dnf update                       # Fedora

# Explicitly install/reinstall libinput
sudo apt install --reinstall libinput # Ubuntu/Debian
sudo pacman -S libinput               # Arch
sudo dnf reinstall libinput           # Fedora

According to the libinput documentation, the library provides advanced support for touch (multitouch and gesture) features of touchpads and touchscreens[reference:15]. The libinput-tools package contains diagnostic tools helpful for debugging[reference:16]. After updating, reboot and test your gestures.

Outcome: Updating libinput resolves gesture issues caused by outdated drivers.

5. GNOME: Install Gesture Customization Extension

For GNOME users, the linux touchpad gestures not working wayland issue is often resolved by installing a gesture customization extension. The Touchpad Gesture Customization extension modifies and extends existing touchpad gestures on GNOME Wayland[reference:17].

# Install from GNOME Extensions website
# Or manually:
git clone https://github.com/HieuTNg/touchpad-gesture-customization.git
cd touchpad-gesture-customization
npm install
npm run update
# Log out and log in, then enable via Extensions app

This extension supports swipe gestures for overview navigation, workspace switching, window manipulation, volume control, and brightness control[reference:18]. It also supports pinch gestures for showing desktop, opening/closing windows, and more[reference:19]. According to the developer, GNOME 49 users must upgrade to GNOME 49.3 or compile from source for the extension to work[reference:20].

Outcome: Installing the gesture customization extension restores full gesture functionality on GNOME Wayland.

6. GNOME: Fix Pinch Gesture Bug

There is a known bug in GNOME where pinch gestures only work when the cursor is over the desktop or top bar[reference:21][reference:22]. This can cause linux touchpad gestures not working wayland for pinch-to-zoom and other gestures.

Workaround: Move cursor to desktop or top bar before performing pinch gesture
Or: Install the Touchpad Gesture Customization extension (see Method 5)

This bug affects pinch gestures and 3/4-finger touch-and-hold gestures[reference:23]. The issue is tracked in GNOME/Mutter GitLab[reference:24]. Until a fix is released, users can work around the issue by ensuring the cursor is not over an application window when performing gestures, or by using the gesture customization extension which provides its own gesture handling.

Outcome: Working around the pinch gesture bug or using the extension resolves the issue for affected GNOME users.

7. KDE Plasma: Known Limitations and Workarounds

On KDE Plasma Wayland, linux touchpad gestures not working wayland is often due to hardcoded gestures. KWin Wayland gestures are hardcoded and do not allow for customization[reference:25][reference:26]. This blocks usage of tools like touchegg and libinput-gestures[reference:27].

KDE System Settings → Workspace Behavior → Touchpad Gestures → View available hardcoded gestures

KDE Plasma does have some built-in gestures, but they cannot be customized[reference:28]. Three-finger swipe gestures may stop working randomly; this is a known bug[reference:29]. Users report that four-finger swipes can break three-finger gestures[reference:30]. For additional customization, consider using the kwin-gestures project, which provides configuration for Wayland gestures[reference:31].

Outcome: Understanding KDE’s limitations helps users set realistic expectations and use available workarounds.

8. Use libinput-gestures for Custom Gestures

libinput-gestures is a utility that reads raw touch events and maps them to commands or keyboard shortcuts[reference:32]. It can provide a linux touchpad gestures not working wayland fix by adding custom gesture support.

# Install libinput-gestures
sudo apt install libinput-gestures     # Ubuntu/Debian (may need to add repository)
sudo pacman -S libinput-gestures       # Arch
sudo dnf install libinput-gestures     # Fedora

# Configure gestures
nano ~/.config/libinput-gestures.conf
# Add gesture mappings, e.g.:
# gesture swipe up 3 _internal ws_up
# gesture swipe down 3 _internal ws_down

# Start the daemon
libinput-gestures -d

On Wayland, libinput-gestures works somewhat incompletely (via XWayland)[reference:33][reference:34]. The default configuration file contains comments about Wayland-specific limitations[reference:35]. For Wayland, native actions via DBus may work better[reference:36]. The _internal command can be used for Wayland-native actions[reference:37].

Outcome: libinput-gestures provides custom gesture support on Wayland with some limitations.

9. Switch to X11 as Temporary Workaround

If linux touchpad gestures not working wayland persists and you need full gesture functionality, switching to X11 is a temporary workaround[reference:38].

Log out → Click gear icon on login screen → Select "GNOME on Xorg" or "Plasma (X11)" → Log in

Many users report that touchpad gestures work fine in X11 but not in Wayland[reference:39]. On X11, libinput-gestures works fully, and desktop environments provide more gesture customization options. However, X11 is older technology and may not support some Wayland features. Use this as a temporary solution while waiting for Wayland gesture support to improve.

Outcome: Switching to X11 restores full gesture functionality as a temporary workaround.

10. Advanced: Create udev Rules for libinput

For advanced users, creating udev rules can provide a permanent linux touchpad gestures not working wayland fix by configuring libinput at the system level[reference:40].

# Create a udev rule for your touchpad
sudo nano /etc/udev/rules.d/99-touchpad.rules

Add a rule like this (adjust for your touchpad):

ACTION=="add|change", SUBSYSTEM=="input", KERNEL=="event*", ATTRS{name}=="SynPS/2 Synaptics TouchPad", ENV{LIBINPUT_IGNORE_DEVICE}="0"

According to the Arch Linux Wiki, libinput configuration on Wayland can be done via udev rules[reference:41]. You can also use the libinput plugin system for more advanced configuration[reference:42]. After creating the rule, reload udev and restart:

sudo udevadm control --reload-rules
sudo udevadm trigger

Outcome: udev rules provide a permanent, system-wide configuration for libinput on Wayland.

11. Frequently Asked Questions

Why are touchpad gestures not working on Wayland?

Wayland gestures depend on libinput and desktop environment support. GNOME has known bugs with pinch gestures, and KDE has hardcoded gestures with limited customization. Missing drivers or outdated libinput can also cause issues[reference:43][reference:44][reference:45].

How do I check if my touchpad is detected on Wayland?

Run libinput list-devices and look for your touchpad in the output. The “Capabilities” line shows supported features[reference:46].

Does libinput-gestures work on Wayland?

libinput-gestures works somewhat incompletely on Wayland (via XWayland)[reference:47][reference:48]. For Wayland-native actions, use the _internal command or DBus actions[reference:49].

How do I fix GNOME gestures not working over apps?

This is a known GNOME bug. Move the cursor to the desktop or top bar before performing gestures, or install the Touchpad Gesture Customization extension[reference:50][reference:51].

Are KDE Wayland gestures customizable?

No, KWin Wayland gestures are hardcoded and do not allow for customization[reference:52][reference:53]. This blocks usage of touchegg and libinput-gestures[reference:54].

Can I use three-finger drag on Wayland?

Yes, there is a program called linux-3-finger-drag that provides three-finger drag support on Wayland, notably for KDE Plasma 6[reference:55].

Does GNOME 49 support gesture extensions?

GNOME 49 users must upgrade to GNOME 49.3 or compile the gesture customization extension from source for it to work[reference:56].

What is the libinput package for Wayland?

libinput is a library that handles input devices in Wayland compositors[reference:57]. It is typically installed as a dependency of any Wayland graphical environment[reference:58].

How do I reset touchpad gestures on Wayland?

Restart your desktop environment (Alt+F2, type ‘r’ on GNOME) or log out and log back in. You can also restart the libinput service if available.

Should I switch back to X11 for gestures?

If Wayland gestures are not working and you need full functionality, switching to X11 is a temporary workaround[reference:59]. Gestures work fine on X11 for most users[reference:60].

12. Conclusion

The linux touchpad gestures not working wayland issue is common but solvable with the right approach. From verifying touchpad detection with libinput to installing GNOME extensions and using libinput-gestures, this guide covers all effective methods. Start with the simplest solution — verifying touchpad detection — and escalate only if necessary. For more information, visit the libinput official documentation, the Arch Linux Wiki, or the GNOME Extensions website. With this proven guide, you can overcome the linux touchpad gestures not working wayland challenge and enjoy full multi-touch functionality.

For more Linux troubleshooting, explore our Linux Hub and guides on Linux sound not working fix, Linux Bluetooth audio stuttering fix, and PipeWire crackling latency fix. With the right approach, you can resolve the linux touchpad gestures not working wayland issue and keep your system running optimally.