I need to disable the clicking on touchpad as my touchpad is a bit broken and get stuck specifically on the left side. Unfortunately I am unable to find the one-line command.

The typical method of changing trackpad behavior is to edit /etc/X11/xorg.conf.d/-synaptics.conf. I'm running Fedora 25 running GNOME 3.22 and which uses Wayland by default, not X, so there is no -synaptics.conf file in there, just this:

$ ls /etc/X11/xorg.conf.d/
00-keyboard.conf

So how do you change the trackpad behavior in this situation?

I'm currently using the i3 window manager, so I need to setup my mouse from the command line. I could previously use xset m 2/1 0 to get the mouse speed I wanted using xev. But moving to libinput driver, xset m no longer works. If I try xinput set-prop "Logitech ERGO M575" "libinput Accel Speed" 1 This just isn't fast enough and libinput won't take a number higher than 1. A couple of other posts mention chance deceleration, but my mouse doesn't have that property. All I have is the following:

xinput list-props "Logitech ERGO M575"
Device 'Logitech ERGO M575':
	Device Enabled (175):	1
	Coordinate Transformation Matrix (177):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Natural Scrolling Enabled (304):	0
	libinput Natural Scrolling Enabled Default (305):	0
	libinput Scroll Methods Available (306):	0, 0, 1
	libinput Scroll Method Enabled (307):	0, 0, 1
	libinput Scroll Method Enabled Default (308):	0, 0, 0
	libinput Button Scrolling Button (309):	8
	libinput Button Scrolling Button Default (310):	2
	libinput Button Scrolling Button Lock Enabled (311):	0
	libinput Button Scrolling Button Lock Enabled Default (312):	0
	libinput Middle Emulation Enabled (313):	0
	libinput Middle Emulation Enabled Default (314):	0
	libinput Rotation Angle (287):	0.000000
	libinput Rotation Angle Default (288):	0.000000
	libinput Accel Speed (315):	1.000000
	libinput Accel Speed Default (316):	0.000000
	libinput Accel Profiles Available (317):	1, 1, 1
	libinput Accel Profile Enabled (318):	1, 0, 0
	libinput Accel Profile Enabled Default (319):	1, 0, 0
	libinput Accel Custom Fallback Points (320):	
	libinput Accel Custom Fallback Step (321):	0.000000
	libinput Accel Custom Motion Points (322):	1.000000, 0.000000
	libinput Accel Custom Motion Step (323):	2.000000
	libinput Accel Custom Scroll Points (324):	
	libinput Accel Custom Scroll Step (325):	0.000000
	libinput Left Handed Enabled (326):	0
	libinput Left Handed Enabled Default (327):	0
	libinput Send Events Modes Available (289):	1, 0
	libinput Send Events Mode Enabled (290):	0, 0
	libinput Send Events Mode Enabled Default (291):	0, 0
	Device Node (292):	"/dev/input/event7"
	Device Product ID (293):	1133, 16534
	libinput Drag Lock Buttons (328):	
	libinput Horizontal Scroll Enabled (329):	1
	libinput Scrolling Pixel Distance (330):	15
	libinput Scrolling Pixel Distance Default (331):	15
	libinput High Resolution Wheel Scroll Enabled (332):	1

I found [a blog post about using custom motion points](https://who-t.blogspot.com/2023/01/libinput-and-custom-pointer.html) but if I try to use those settings and change the Step to 2, the mouse is just really random and janky. I don't understand from this post how to simply change the acceleration to 2x. [This post indicates](https://askubuntu.com/questions/1267142/how-to-set-change-i3wm-mouse-speed-not-acceleration) I can use the "Coordinate Transformation Matrix". I tried changing the default so the last number was 0 and still no speed change. Why is libinput limited from 0,1? This very basic thing I could do with xev seems complication and/or impossible on libinput!

I have a Lenovo Duet 3 with PostmarketOS 24.12 aarch64, GNOME 47 and openRC. The tablet has a power button which suspends the tablet to RAM when pressed, but when the tablet is suspended it is also the only button to wake it up, if we ignore the detachable keyboard. The issue is that the press of the button during the sleep results in the keypress event being propagated to the system as soon as the tablet wakes up, which then goes to sleep again right after. This is the output of evtest right after I pressed the power button in order to suspend and then wake up right after:

~ $ evtest
No device specified, trying to scan all of /dev/input/event*
Not running as root, no devices may be available.
Available devices:
/dev/input/event0:	cros_ec_buttons
/dev/input/event1:	Whiskers Tablet Mode Switch
/dev/input/event10:	keyd virtual pointer
/dev/input/event2:	hid-over-i2c 0603:604A
/dev/input/event3:	hid-over-i2c 0603:604A Stylus
/dev/input/event5:	hid-over-i2c 0603:604A UNKNOWN
/dev/input/event7:	sc7180-rt5682-max98357a-1mic Headset Jack
/dev/input/event8:	sc7180-rt5682-max98357a-1mic HDMI Jack
/dev/input/event9:	keyd virtual keyboard
Select the device event number [0-10]: 
0
Input driver version is 1.0.1
Input device ID: bus 0x6 vendor 0x0 product 0x0 version 0x1
Input device name: "cros_ec_buttons"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
  Event type 5 (EV_SW)
    Event code 0 (SW_LID) state 0
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value    250
    Repeat code 1 (REP_PERIOD)
      Value     33
Properties:
Testing ... (interrupt to exit)


Event: time 1738621056.283673, type 1 (EV_KEY), code 116 (KEY_POWER), value 1
Event: time 1738621056.283673, -------------- SYN_REPORT ------------
Event: time 1738621056.416707, type 1 (EV_KEY), code 116 (KEY_POWER), value 0
Event: time 1738621056.416707, -------------- SYN_REPORT ------------
Event: time 1738621063.098269, type 1 (EV_KEY), code 116 (KEY_POWER), value 1
Event: time 1738621063.098269, -------------- SYN_REPORT ------------
Event: time 1738621063.197878, type 1 (EV_KEY), code 116 (KEY_POWER), value 0
Event: time 1738621063.197878, -------------- SYN_REPORT ------------

I have two Logitech trackballs, a Wireless TrackMan FX and a Marble Mouse. Both report the same set of buttons in evtest: BTN_LEFT, BTN_RIGHT, BTN_MIDDLE, BTN_SIDE and BTN_EXTRA even though they only have four physical buttons each. The TrackMan FX sends the exact events I want: left, right, middle and side. However, the Marble Mouse sends BTN_EXTRA instead of BTN_MIDDLE, so I'd like to remap that. [This answer](https://unix.stackexchange.com/a/587975/187221) seems to cover exactly what I want and hwdb looks like the right place to do it. Alas, it only works halfway and I have no idea why; I suspect it has to do with the two different input events generated by a single click. evtest reports a working middle click from the FX like this (leaving out irrelevant time stamps for clarity):

type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1

The unmodified click from the MarbleMouse:

type 4 (EV_MSC), code 4 (MSC_SCAN), value 90005
type 1 (EV_KEY), code 276 (BTN_EXTRA), value 1

So my 99-marblebutton.hwdb file does this:

evdev:input:b0003v046DpC408*
 ID_INPUT_KEY=1
 KEYBOARD_KEY_90005=btn_middle

And the resulting input event is modified thus:

type 4 (EV_MSC), code 4 (MSC_SCAN), value 90005
type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 1

So I do get a BTN_MIDDLE event but the associated MSC_SCAN still has the wrong value, and that seems to make a difference as the middle click isn't recognized anywhere. In fact it doesn't even seem to be considered a valid input event at all: using libinput debug-events I can see the unmodified event:

event7   POINTER_BUTTON          +97.374s      BTN_EXTRA (276) pressed, seat count: 1

With the hwdb config in place, nothing is reported when I press the same button, and consequently wev doesn't see the events either. Other things I've tried include remapping in swaywm which sort of works, but only in some applications:

set $MOUSE "1133:50184:Logitech_USB_Trackball"
bindsym --input-device=$MOUSE --whole-window BTN_EXTRA seat - cursor press BTN_MIDDLE
bindsym --input-device=$MOUSE --whole-window --release BTN_EXTRA seat - cursor release BTN_MIDDLE

[interception-tools](https://gitlab.com/interception/linux/tools) allow me to write a filter that can "fix" both the EV_KEY and the EV_MSC event, but the effect is similar to hwdb: the events show up fine in evtest but libinput doesn't even see them. Solaar doesn't seem to support either of my devices, and I'm too thick to get input-remapper to do anything useful.

I need to disable the touchpad of my laptop. I am using Gnome **on Wayland**. - libinput should provide this functionality, but apparently it doesn't. - xinput doesn't work because I'm on Wayland. - I think Gnome offered some switch to do so in the input settings, but it isn't there anymore (Gnome shell 3.34 — maybe this is an Xorg exclusive feature?). Is it really asked too much if I want do disable an input device? ------ **Edit: xinput is NOT a solution!** Its man page has a whole section on Wayland (emphasis mine): > **XWAYLAND** > > Xwayland is an X server that uses a Wayland Compositor as backend. Xwayland acts as translation layer between the X protocol and the Wayland protocol but does not have direct access to the hardware. The X Input Extension devices created by Xwayland ("xwayland-pointer", "xwayland-keyboard", etc.) map to the Wayland protocol devices, not to physical devices. These X Input Extension devices are **only visible to other X clients** connected to the same Xwayland process. Changing properties on Xwayland devices **only affects the behavior of those clients**. For example, **disabling an Xwayland device with xinput does not disable the device in Wayland-native applications**. Other changes may not have any effect at all. In most instances, using xinput with an Xwayland device is **indicative of a bug in a shell script** and xinput will print a warning. Use the Wayland Compositor's native device configuration methods instead. **TL;DR**: If I disable the touchpad using xinput, it will still continue working as before, but XWayland applications won't see the cursor move anymore.

I have a bad quality mouse (Razer Basilisk V3 X Hyperspeed) that cost way too much money for me to replace it with an even more expensive higher quality mouse, and I'd like to try to fix its issues in the software. It has many issues: - the faster I scroll, the more likely the mouse is to send two scroll events, one in the correct direction, one in the reverse direction. This means that scrolling really fast cause the scroll container to just shake and remain approximately at the same vertical scroll level. This doesn't happen on Windows (but I don't use Windows). - since very recently, the primary click is doubled more than half of the times, this has made the mouse pretty much unusable - when dragging, the mouse sometimes sends a spurious release event, cancelling the drag mid-way. This is impossible to really debounce, but maybe the software can delay all releases by a few millisecond to check if there's a press just after? libinput supposedly debounces fast events according to some previous answers on this Q&A, but my issues prove that it doesn't on my computer. How can I configure the debounce delay? I'm running Linux Mint Cinnamon with Xorg and libinput 1.25.0.

I want to disable the paste action associated with the 3 finger tapping because it is not a behavior helpful for me and also somehow dangerous. Most of the post (for ex. this one ) report either to: - add TappingButtonMap to xorg.conf ( this option allows only to invert button not to disable them). - set ButtonMapping property by CLI -> xinput set-prop $ID ButtonMapping 1 2 3 ...` ( this actually changes the physical button ) Both solutions are not sufficient for my purpose. - I think it is not possible with libinput to disable one single tapping, am I right? - Is there any Plasma setting that can help to accomplish this ?

I use a 10-button mouse (Logitech M705). Under X11, I was able to configure one of the extra buttons to behave as a second middle-click by modifying files in etc/X11/xorg.conf.d. Under Wayland, this no longer works. My research shows that I need to do something with libinput. I thought this would be a common problem but can't find an answer anywhere. Can someone explain how to remap mouse buttons or explain why it can't be done?

https://wayland.freedesktop.org/libinput/doc/latest/api/index.html Following the simple example program in their website i made the following , but the loop never executes , meaning no events where in the queue. Am i missing something ? Since this is the example in the website i expected it to work , or atleast enter the loop.

#include 
#include 
#include 
#include 
#include 
#include 
#include 

static int open_restricted(const char *path, int flags, void *user_data) {
  int fd = open(path, flags);
  return fd < 0 ? -errno : fd;
}

static void close_restricted(int fd, void *user_data) { close(fd); }

const static struct libinput_interface interface = {
    .open_restricted = open_restricted,
    .close_restricted = close_restricted,
};

int main(void) {
  struct libinput *li;
  struct libinput_event *event;
  struct udev *udev_ctx = udev_new();
  assert(udev_ctx && "udev was null");

  li = libinput_udev_create_context(&interface, NULL, udev_ctx);
  assert(li != NULL && "li was null");
  libinput_udev_assign_seat(li, "seat0");
  libinput_dispatch(li);

  printf("Hello");

  while ((event = libinput_get_event(li)) != NULL) {

    printf("loop");
    // handle the event here

    libinput_event_destroy(event);
    libinput_dispatch(li);
  }

  libinput_unref(li);

  return 0;
}

system info:

- system: "x86_64-linux"
 - host os: Linux 6.6.31, NixOS, 24.05 (Uakari), 24.05.20240521.5710852
 - multi-user?: no
 - sandbox: yes
 - version: nix-env (Nix) 2.18.2
 - channels(root): "nixos-23.05"
 - nixpkgs: not found
--------

❯ libinput --version
1.25.0
--------

❯ systemctl --version
systemd 255 (255.6)
+PAM +AUDIT -SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unified

Build with :

gcc -o test main.cpp pkg-config --cflags --libs libinput  pkg-config --cflags --libs libudev

I'm using KDE desktop environment, and I have recently switched from Xorg to Wayland. The compositor is KWin.
I'm concerned about configuring my mouse and keyboard properly, because obviously it can't be now done with xorg.conf as it was before.
I wasn't able to find any documentation related to configuring KWin when using it w/o Xorg. There are advantages for me in using Wayland, but I'm really confused about it's design. I can't understand which programs now take care of my hardware, when there's no Xorg server. For example, the graphics backend: it uses DRM automatically, but where can it be configured?
As another example, this was my keyboard configuration, where I had keyboard layout set, and few other options:

Section "InputClass"
    Identifier     "Keyboard0"
    Driver         "evdev"
    Option         "Protocol" "auto"
    Option "XkbLayout" "us,tr"
    Option "XkbOptions" "grp:alt_shift_toggle,terminate:ctrl_alt_bksp"
    Option "GrabDevice" "false"
EndSection

Without Xorg, where do I configure my input drivers so the Wayland compositor will use the correct settings?
Another part of config which I also need, is related to blacklisting virtual mice from being added to the session (I use them for different purpose):

Section "InputClass"
    Identifier     "ignore virtual mouse"
    MatchProduct     "melon69-virtual-mouse"
    MatchIsPointer      "on"
    Option "Ignore" "on"
EndSection

Is it possible to configure a Wayland compositor for the same behavior (blacklisting input devices), or I have to go by removing user permissions on the device nodes?
Thanks for your help!

Touchpad seems configured, cat /proc/bus/input/devices: I: Bus=0011 Vendor=0002 Product=000a Version=0063 N: Name="TPPS/2 Elan TrackPoint" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse0 event4 B: PROP=21 B: EV=7 B: KEY=70000 0 0 0 0 B: REL=3 cat /usr/share/X11/xorg.conf.d/40-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" EndSection xinput list: ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ TPPS/2 Elan TrackPoint id=12 [slave pointer (2)] but the **touchpad isn't functioning**. (Both trackpoint and USB mouse work.) System details, lshw includes: vendor: LENOVO version: ThinkPad X1 Carbon Gen 12 *-core *-cpu description: CPU product: Intel(R) Core(TM) Ultra 7 165U version: 6.170.4 *-input:0 product: AT Translated Set 2 keyboard physical id: 1 logical name: input0 logical name: /dev/input/event0 logical name: input0::capslock logical name: input0::numlock logical name: input0::scrolllock capabilities: i8042 *-input:5 product: sof-hda-dsp HDMI/DP,pcm=5 physical id: 6 logical name: input14 logical name: /dev/input/event13 *-input:7 product: TPPS/2 Elan TrackPoint physical id: 9 logical name: input3 logical name: /dev/input/event4 logical name: /dev/input/mouse0 capabilities: i8042 And lspci 00:00.0 Host bridge: Intel Corporation Device 7d02 (rev 04) 00:02.0 VGA compatible controller: Intel Corporation Meteor Lake-P [Intel Graphics] (rev 08) 00:04.0 Signal processing controller: Intel Corporation Device 7d03 (rev 04) 00:06.0 PCI bridge: Intel Corporation Device 7e4d (rev 20) 00:06.1 PCI bridge: Intel Corporation Device 7eca (rev 10) 00:07.0 PCI bridge: Intel Corporation Meteor Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 02) 00:07.2 PCI bridge: Intel Corporation Meteor Lake-P Thunderbolt 4 PCI Express Root Port #2 (rev 02) 00:08.0 System peripheral: Intel Corporation Device 7e4c (rev 20) 00:0a.0 Signal processing controller: Intel Corporation Device 7d0d (rev 01) 00:0b.0 Processing accelerators: Intel Corporation Device 7d1d (rev 04) 00:0d.0 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 USB Controller (rev 02) 00:0d.2 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 NHI #0 (rev 02) 00:0d.3 USB controller: Intel Corporation Meteor Lake-P Thunderbolt 4 NHI #1 (rev 02) 00:14.0 USB controller: Intel Corporation Meteor Lake-P USB 3.2 Gen 2x1 xHCI Host Controller (rev 20) 00:14.2 RAM memory: Intel Corporation Device 7e7f (rev 20) 00:14.3 Network controller: Intel Corporation Device 7e40 (rev 20) 00:15.0 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO I2C Controller #0 (rev 20) 00:16.0 Communication controller: Intel Corporation Device 7e70 (rev 20) 00:16.3 Serial controller: Intel Corporation Device 7e73 (rev 20) 00:1c.0 PCI bridge: Intel Corporation Device 7e38 (rev 20) 00:1f.0 ISA bridge: Intel Corporation Device 7e03 (rev 20) 00:1f.3 Audio device: Intel Corporation Meteor Lake-P HD Audio Controller (rev 20) 00:1f.4 SMBus: Intel Corporation Meteor Lake-P SMBus Controller (rev 20) 00:1f.5 Serial bus controller: Intel Corporation Meteor Lake-P SPI Controller (rev 20) 04:00.0 Non-Volatile memory controller: Shenzhen Unionmemory Information System Ltd. Device 6a04 (rev 03)

I'd like to perform some actions when the user requests a keyboard layout change (via ibus/setxkbmap/wayland/gnome/plasma/…), notably in order to disable KMonad (otherwise the user-defined layout might conflict with KMonad's layout… I'm just afraid that killing KMonad would reset the layout but this is another question). Is there an efficient and portable way to detect if a keyboard change occurred, or, even better, to hook right before the keyboard change occured? I was planning to use:

$ setxkbmap -query
rules:      evdev
model:      pc86
layout:     fr
variant:    bepo_afnor
options:    ctrl:swapcaps

It seems to work for both Ibus & setxkbmap, but first this is unlikely to work with Wayland (but I need to check), and, most importantly, I don't to run this command every second as it would consume CPU resources for no reasons. Is there a more portable & efficient solution?

I am running a [userspace driver for a /dev/uinput device](https://github.com/rfc2822/GfxTablet) in a Wayland desktop session. The instructions suggest running xinput list to confirm that the device is detected. Of course, xinput is an X.org application. What is the equivalent command for Wayland? (A GNOME GUI equivalent is acceptable.)

Week ago stylus have been added somehow between devices (I do not have own stylus for few months) and spam me with events every time laptop starts:

$ sudo libinput debug-events | grep event5
-event5   DEVICE_ADDED            ELAN9009:00 04F3:2E36             seat0 default group5  cap:t  size 300x184mm ntouches 10 calib
-event5   TOUCH_DOWN              +69.894s	0 (0) 85.20/92.85 (255.67/170.92mm)
 event5   TOUCH_FRAME             +69.894s	
-event5   TOUCH_UP                +69.909s	0 (0)
 event5   TOUCH_FRAME             +69.909s	
-event5   TOUCH_DOWN              +96.373s	0 (0) 85.23/92.89 (255.75/171.00mm)
 event5   TOUCH_FRAME             +96.373s	
 event5   TOUCH_UP                +96.387s	0 (0)
 event5   TOUCH_FRAME             +96.387s	
-event5   TOUCH_DOWN              +115.360s	0 (0) 85.20/93.12 (255.67/171.42mm)
 event5   TOUCH_FRAME             +115.360s	
-event5   TOUCH_UP                +115.374s	0 (0)
 event5   TOUCH_FRAME             +115.374s	
-event5   TOUCH_DOWN              +129.771s	0 (0) 85.23/92.98 (255.75/171.17mm)
 event5   TOUCH_FRAME             +129.771s	
 event5   TOUCH_UP                +129.786s	0 (0)
 event5   TOUCH_FRAME             +129.786s	
-event5   TOUCH_DOWN              +138.171s	0 (0) 85.23/92.76 (255.75/170.75mm)

So every laptop restart is device added. Quick solution was every laptop start call:

$ xinput disable "ELAN9009:00 04F3:2E36
$ xinput disable "ELAN9009:00 04F3:2E36 Stylus

$ xinput # when are devices disabled
...
∼ ELAN9009:00 04F3:2E36                   	id=9	[floating slave]
∼ ELAN9009:00 04F3:2E36 Stylus            	id=10	[floating slave]
...

$ cat /proc/bus/input/devices

I: Bus=0018 Vendor=04f3 Product=2e36 Version=0100
N: Name="ELAN9009:00 04F3:2E36"
P: Phys=i2c-ELAN9009:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-ELAN9009:00/0018:04F3:2E36.0001/input/input19
U: Uniq=
H: Handlers=mouse0 event5 
B: PROP=2
B: EV=1b
B: KEY=400 0 0 0 0 0
B: ABS=3273800000000003
B: MSC=20

And now I try figure out what happened and how permanently remove this unreal device. Any idea?

Where is, and how do I change the xorg conf file? I want to change the default scrolling speed of my touchpad. I can use xinput --set-prop "YOUR TOUCHPAD" "libinput Scrolling Pixel Distance" YOUR_SPEED to change it for this session, but I would like to make it permanent. I've read here https://man.archlinux.org/man/libinput.4#Option~24 , that I can change the Option "ScrollPixelDistance" "int" but I don't know how to do this or where to find the xorg config file.

I use a Lenovo Thinkpad X1 (Gen 6) laptop. Currently, I'm on Fedora. In the GRUB menu, the internal keyboard works as expected. While using the OS, the keyboard is mainly unresponsive, but sometimes gets enabled and directly after that disabled. This is what it looks like observed with libinput debug-events:

-event16  SWITCH_TOGGLE           +13.842s	switch tablet-mode state 0
-event15  SWITCH_TOGGLE           +13.843s	switch tablet-mode state 0
-event16  SWITCH_TOGGLE           +13.892s	switch tablet-mode state 1
-event15  SWITCH_TOGGLE           +13.892s	switch tablet-mode state 1

evtest shows what device those events are attached to:

/dev/input/event15:	ThinkPad Extra Buttons
/dev/input/event16:	Intel HID switches

libinput is on version 1.24.0. This problem occurs (at least) with the following distros: - OpenSUSE Tumbleweed - Vanilla OS Orchid - Arch - Fedora It would be best if I could make the tablet mode appear only when the laptop is "flipped", but completely disabling the tablet mode (or that the tablet mode disables the keyboard) is enough. --- I tried to disable it with:

export LIBINPUT_IGNORE_DEVICE="17 20"

I also tried disabling both events at the same time with:

evtest --grab /dev/input/event15
evtest --grab /dev/input/event16

Although libinput debug-events stopped reporting the tablet mode switching, it still occurred.

I turned off the touchscreen as described here and here on my Lenovo ThinkPad with Debian and Wayland/libinput .

echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="5144", ATTR{authorized}="0"' > /etc/udev/rules.d/80-touchscreen.rules

Now I need to use the ThinkPad Pen Pro, which is a stylus for the screen/monitor's inbuilt tablet function. The pen is affected by the udev rule. Cancelling the rule makes the pen work but also reactivates touch. The devices have idVendor and idProduct in common . But are touchscreen and stylus not operating independently, and so shouldn't it be possible to disable the one without the other? (Note, xinput disable does not work for some reason, and I don't know what model number goes into xsetwacom --set 'model' Touch off because xsetwacom --list devices returns nothing, so I cannot test it that way.) At least someone reported touch not working while pen and tablet did function . *Can someone help specify a working udev rule *, there are a few ? I tried the following but both became deactivated.

SUBSYSTEM=="usb", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="5144", ATTR{name}=="Wacom Pen and multitouch sensor Pen", ATTR{authorized}="1"
SUBSYSTEM=="usb", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="5144", ATTR{name}=="Wacom Pen and multitouch sensor Finger", ATTR{authorized}="0"

$ cat /proc/bus/input/devices
I: Bus=0003 Vendor=056a Product=5144 Version=0111
N: Name="Wacom Pen and multitouch sensor Finger"
P: Phys=usb-0000:00:14.0-10/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:056A:5144.0005/input/input32
U: Uniq=
H: Handlers=mouse2 event21 
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 0
B: ABS=260800000000003

I: Bus=0003 Vendor=056a Product=5144 Version=0111
N: Name="Wacom Pen and multitouch sensor Pen"
P: Phys=usb-0000:00:14.0-10/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:056A:5144.0006/input/input34
U: Uniq=
H: Handlers=mouse3 event25 
B: PROP=2
B: EV=1b
B: KEY=1e03 0 0 0 0 0
B: ABS=1000d000003
B: MSC=1

$ lsusb
Bus 001 Device 007: ID 056a:5144 Wacom Co., Ltd Pen and multitouch sensor

$ inputx --list devices
⎡ Virtual core pointer                        	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ xwayland-pointer:18                     	id=6	[slave  pointer  (2)]
⎜   ↳ xwayland-relative-pointer:18            	id=7	[slave  pointer  (2)]
⎜   ↳ xwayland-stylus:18                      	id=10	[slave  pointer  (2)]
⎜   ↳ xwayland-eraser:18                      	id=11	[slave  pointer  (2)]
⎜   ↳ xwayland-cursor:18                      	id=12	[slave  pointer  (2)]
⎜   ↳ xwayland-touch:18                       	id=9	[slave  pointer  (2)]

$ xsetwacom --list devices


$ libwacom-list-local-devices 
# Device node: /dev/input/event25
[Device]
Name=ISDv4 5144
ModelName=
DeviceMatch=usb:056a:5144;
Class=ISDV4
Width=12
Height=7
IntegratedIn=Display;System;
Styli=0x1;0x11;0x19;0x21;0x31;0x39;0x49;0x71;0x221;0x231;0x271;0x421;0x431;0x621;0x631;0x8051;0x805b;0x806b;0x807b;0x826b;0x846b;

[Features]
Reversible=false
Stylus=true
Ring=false
Ring2=false
Touch=true
TouchSwitch=false
# StatusLEDs=
NumStrips=0
Buttons=0

---------------------------------------------------------------

# Device node: /dev/input/event21
[Device]
Name=ISDv4 5144
ModelName=
DeviceMatch=usb:056a:5144;
Class=ISDV4
Width=12
Height=7
IntegratedIn=Display;System;
Styli=0x1;0x11;0x19;0x21;0x31;0x39;0x49;0x71;0x221;0x231;0x271;0x421;0x431;0x621;0x631;0x8051;0x805b;0x806b;0x807b;0x826b;0x846b;

[Features]
Reversible=false
Stylus=true
Ring=false
Ring2=false
Touch=true
TouchSwitch=false
# StatusLEDs=
NumStrips=0
Buttons=0

$ udevadm info /sys/class/input/input32/
P: /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:056A:5144.0005/input/input32
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:056A:5144.0005/input/input32
E: PRODUCT=3/56a/5144/111
E: NAME="Wacom Pen and multitouch sensor Finger"
E: PHYS="usb-0000:00:14.0-10/input0"
E: UNIQ=""
E: PROP=2
E: EV=b
E: KEY=400 0 0 0 0 0
E: ABS=260800000000003
E: MODALIAS=input:b0003v056Ap5144e0111-e0,1,3,k14A,ra0,1,2F,35,36,39,mlsfw
E: SUBSYSTEM=input
E: USEC_INITIALIZED=6838074
E: ID_INPUT=1
E: ID_INPUT_TOUCHSCREEN=1
E: ID_BUS=usb
E: ID_MODEL=Pen_and_multitouch_sensor
E: ID_MODEL_ENC=Pen\x20and\x20multitouch\x20sensor
E: ID_MODEL_ID=5144
E: ID_SERIAL=Wacom_Co._Ltd._Pen_and_multitouch_sensor
E: ID_VENDOR=Wacom_Co._Ltd.
E: ID_VENDOR_ENC=Wacom\x20Co.\x2cLtd.
E: ID_VENDOR_ID=056a
E: ID_REVISION=0003
E: ID_TYPE=hid
E: ID_USB_MODEL=Pen_and_multitouch_sensor
E: ID_USB_MODEL_ENC=Pen\x20and\x20multitouch\x20sensor
E: ID_USB_MODEL_ID=5144
E: ID_USB_SERIAL=Wacom_Co._Ltd._Pen_and_multitouch_sensor
E: ID_USB_VENDOR=Wacom_Co._Ltd.
E: ID_USB_VENDOR_ENC=Wacom\x20Co.\x2cLtd.
E: ID_USB_VENDOR_ID=056a
E: ID_USB_REVISION=0003
E: ID_USB_TYPE=hid
E: ID_USB_INTERFACES=:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usbhid
E: ID_PATH=pci-0000:00:14.0-usb-0:10:1.0
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_10_1_0
E: ID_FOR_SEAT=input-pci-0000_00_14_0-usb-0_10_1_0
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:

$ udevadm info /sys/class/input/input34
P: /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:056A:5144.0006/input/input34
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:056A:5144.0006/input/input34
E: PRODUCT=3/56a/5144/111
E: NAME="Wacom Pen and multitouch sensor Pen"
E: PHYS="usb-0000:00:14.0-10/input1"
E: UNIQ=""
E: PROP=2
E: EV=1b
E: KEY=1e03 0 0 0 0 0
E: ABS=1000d000003
E: MSC=1
E: MODALIAS=input:b0003v056Ap5144e0111-e0,1,3,4,k140,141,149,14A,14B,14C,ra0,1,18,1A,1B,28,m0,lsfw
E: SUBSYSTEM=input
E: USEC_INITIALIZED=6961475
E: ID_INPUT=1
E: ID_INPUT_TABLET=1
E: ID_BUS=usb
E: ID_MODEL=Pen_and_multitouch_sensor
E: ID_MODEL_ENC=Pen\x20and\x20multitouch\x20sensor
E: ID_MODEL_ID=5144
E: ID_SERIAL=Wacom_Co._Ltd._Pen_and_multitouch_sensor
E: ID_VENDOR=Wacom_Co._Ltd.
E: ID_VENDOR_ENC=Wacom\x20Co.\x2cLtd.
E: ID_VENDOR_ID=056a
E: ID_REVISION=0003
E: ID_TYPE=hid
E: ID_USB_MODEL=Pen_and_multitouch_sensor
E: ID_USB_MODEL_ENC=Pen\x20and\x20multitouch\x20sensor
E: ID_USB_MODEL_ID=5144
E: ID_USB_SERIAL=Wacom_Co._Ltd._Pen_and_multitouch_sensor
E: ID_USB_VENDOR=Wacom_Co._Ltd.
E: ID_USB_VENDOR_ENC=Wacom\x20Co.\x2cLtd.
E: ID_USB_VENDOR_ID=056a
E: ID_USB_REVISION=0003
E: ID_USB_TYPE=hid
E: ID_USB_INTERFACES=:030000:
E: ID_USB_INTERFACE_NUM=01
E: ID_USB_DRIVER=usbhid
E: ID_PATH=pci-0000:00:14.0-usb-0:10:1.1
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_10_1_1
E: ID_FOR_SEAT=input-pci-0000_00_14_0-usb-0_10_1_1
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:

$ sudo udevadm info -a -p /sys/class/input/input32


$ sudo udevadm info -a -p /sys/class/input/input34

I don't know if im using libinput or synaptics cause i use both at the same time. **Xorg synaptic config**

cat /etc/X11/xorg.conf.d/70-synaptics.conf 
# Example xorg.conf.d snippet that assigns the touchpad driver
# to all touchpads. See xorg.conf.d(5) for more information on
# InputClass.
# DO NOT EDIT THIS FILE, your distribution will likely overwrite
# it when updating. Copy (and rename) this file into
# /etc/X11/xorg.conf.d first.
# Additional options may be added in the form of
#   Option "OptionName" "value"
#
Section "InputClass"
        Identifier "touchpad catchall"
        Driver "synaptics"
	MatchDevicePath "/dev/input/event*"
        MatchIsTouchpad "on"
        # OWN SHIT
        Option "PalmDetect" "1"
        Option "PalmMinWidth" "3"
        Option "PalmMinZ" "50"
        Option "VertScrollDelta" "30"
        Option "HorizScrollDelta" "500"

# This option is recommend on all Linux systems using evdev, but cannot be
# enabled by default. See the following link for details:
# http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html 
#       MatchDevicePath "/dev/input/event*"
EndSection

Section "InputClass"
        Identifier "touchpad ignore duplicates"
        MatchIsTouchpad "on"
        MatchOS "Linux"
        MatchDevicePath "/dev/input/mouse*"
        Option "Ignore" "on"
        # OWN SHIT
        Option "PalmDetect" "1"
        Option "PalmMinWidth" "4"
        Option "PalmMinZ" "50"
        Option "VertScrollDelta" "30"
        Option "HorizScrollDelta" "500"
EndSection

# This option enables the bottom right corner to be a right button on clickpads
# and the right and middle top areas to be right / middle buttons on clickpads
# with a top button area.
# This option is only interpreted by clickpads.
Section "InputClass"
        Identifier "Default clickpad buttons"
        MatchDriver "synaptics"
        Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
        Option "SecondarySoftButtonAreas" "58% 0 0 15% 42% 58% 0 15%"
EndSection

# This option disables software buttons on Apple touchpads.
# This option is only interpreted by clickpads.
Section "InputClass"
        Identifier "Disable clickpad buttons on Apple touchpads"
        MatchProduct "Apple|bcm5974"
        MatchDriver "synaptics"
        Option "SoftButtonAreas" "0 0 0 0 0 0 0 0"
EndSection

**Altough i set the scroll speed with this script**:

#!bin/bash
# MOUSE SCRIPT
# xinput, permanent, run at startup
# touchpad scroll speed config

# >> TOUCHPAD
# Scroll speed
xinput set-prop "Synaptics TM3276-022" "Synaptics Scrolling Distance" 300, 100

# >> TRACKPOINT
# Scroll speed
xinput set-prop "TPPS/2 IBM TrackPoint" "libinput Scrolling Pixel Distance" 50

**And i set the trackpoint speed with this script**

#!bin/bash
# Trackpoint speed controll config
xinput --set-prop "TPPS/2 IBM TrackPoint" "libinput Accel Profile Enab
led" 1, 0

xinput --set-prop "TPPS/2 IBM TrackPoint" "libinput Accel Speed" 0.40

**Any idea which config to use or which is the config the system uses?**

Using Manjaro 23.0, I found a way to decrease the speed of my USB SteelSeries mouse but I struggle to make it persistent. After some time being not in use, or a system reboot, the xinput settings reset to the "default". The mouse gets a new "Id" evertime at least anytime I reboot. This problem should be solved with the xorg.conf code I found below. Otherwise I have to find the mouse Id via xinput manually. These are the xinput settings I would like the mouse to run on the my new xorg.conf: $ id="10"; speed=0.23; xinput set-prop $id "Coordinate Transformation Matrix" $speed, 0, 0, 0, $speed 0, 0, 0, 1 Via https://unix.stackexchange.com/questions/620642/keep-xinput-settings-after-mouse-wakeup I found out how to do this but not how to translate my settings from xinput to X11. Unfortunately the name of most (if not all) options of libinput differs between xinput and xorg.conf. Here is the xorg.conf code I want to use: Section "InputClass" Identifier "My Mouse" MatchProduct "SteelSeries SteelSeries Rival 300 Gaming Mouse" Option "TransformationMatrix" "????" EndSection Is there maybe a command I could use to transform my xinput cli setting that would achieve the goal?