`libinput` upgrade causes mouse sensitivity to go unreasonably high

Issues & Assistance
1

After upgrading my system and rebooting I noticed that my pointer was incredibly fast. Nothing in the settings has changed. After checking the upgrade logs I noted that xf86-input-libinput was upgraded from 1.2.1-1 to 1.3.0-1. Commit history mentioned adding a new mouse acceleration profile, so I tried manually setting the flat profile with xinput set-prop 8 298 0 1 0. The default after logging in is 1 0 0. This reverted the behavior, but that fix does not persist across reboots. Changing the acceleration profile in the KDE system settings does not do anything, the pointer speed doesn't change, nor is prop 298 updated. Is this something I can fix on my own or do I need to wait for someone upstream?

garuda-inxi just in case:

System:
  Kernel: 6.2.10-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=0f5fc487-f62a-4492-aada-77ed9b8795c8 rw rootflags=subvol=@
    splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1 loglevel=3 ibt=off
  Desktop: KDE Plasma v: 5.27.4 tk: Qt v: 5.15.8 info: latte-dock
    wm: kwin_x11 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: 970A-G/3.1 serial: <filter>
    UEFI: American Megatrends v: P1.20 date: 01/12/2016
Battery:
  ID-1: hidpp_battery_0 charge: 21% condition: N/A volts: 3.7 min: N/A
    model: Logitech G502 LIGHTSPEED Wireless Gaming Mouse type: N/A
    serial: <filter> status: discharging
CPU:
  Info: model: AMD FX-8370 socket: AM3 bits: 64 type: MT MCP arch: Piledriver
    level: v2 built: 2012-13 process: GF 32nm family: 0x15 (21) model-id: 2
    stepping: 0 microcode: 0x6000852
  Topology: cpus: 1x cores: 8 smt: enabled cache: L1: 384 KiB
    desc: d-8x16 KiB; i-4x64 KiB L2: 8 MiB desc: 4x2 MiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 4200 min/max: 1400/4200 boost: enabled
    base/boost: 4200/4200 scaling: driver: acpi-cpufreq governor: performance
    volts: 1.4 V ext-clock: 200 MHz cores: 1: 4200 2: 4200 3: 4200 4: 4200
    5: 4200 6: 4200 7: 4200 8: 4200 bogomips: 67196
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] vendor: Gigabyte driver: nvidia
    v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
    status: current (as of 2023-03) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s
    lanes: 16 link-max: gen: 2 speed: 5 GT/s bus-ID: 01:00.0
    chip-ID: 10de:2182 class-ID: 0300
  Device-2: Chicony HP 720p HD Monitor Webcam type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 2-4.1:5 chip-ID: 04f2:b3eb
    class-ID: 0102
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 97 s-size: 503x292mm (19.80x11.50")
    s-diag: 582mm (22.9")
  Monitor-1: DP-2 res: 1920x1080 hz: 60 dpi: 98
    size: 497x292mm (19.57x11.5") diag: 576mm (22.69") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 530.41.03 renderer: NVIDIA GeForce GTX 1660
    Ti/PCIe/SSE2 direct-render: Yes
Audio:
  Device-1: AMD SBx00 Azalia vendor: ASRock driver: snd_hda_intel
    bus-ID: 2-4.1:5 v: kernel chip-ID: 04f2:b3eb bus-ID: 00:14.2
    chip-ID: 1002:4383 class-ID: 0102 class-ID: 0403
  Device-2: NVIDIA TU116 High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:1aeb class-ID: 0403
  Device-3: Chicony HP 720p HD Monitor Webcam type: USB
    driver: snd-usb-audio,uvcvideo
  API: ALSA v: k6.2.10-zen1-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 0.3.68 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 link-max: gen: 2 speed: 5 GT/s
    bus-ID: 05:00.0 chip-ID: 8086:2725 class-ID: 0280
  IF: wlp5s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: d000 bus-ID: 07:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp7s0 state: down mac: <filter>
  IF-ID-1: wg0 state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth:
  Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 5-2:2
    chip-ID: 8087:0032 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 1.46 TiB used: 185.75 GiB (12.4%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: A-Data model: SX7000NP
    size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: CB1.1.1 temp: 31.9 C scheme: GPT
  SMART: yes health: PASSED on: 331d 10h cycles: 2,373
    read-units: 21,274,075 [10.8 TB] written-units: 14,242,399 [7.29 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT480BX500SSD1
    family: Micron Client SSDs size: 447.13 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.2 speed: 6.0 Gb/s type: SSD serial: <filter>
    rev: R022 temp: 39 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 266d 7h cycles: 2230
    written: 26.28 TiB Old-Age: UDMA CRC errors: 2092
    alert: Bad cable/connection?
  ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD1003FZEX-00K3CA0 family: Black size: 931.51 GiB block-size:
    physical: 4096 B logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: HDD
    rpm: 7200 serial: <filter> rev: 1A01 temp: 30 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 126d 11h cycles: 4244
Partition:
  ID-1: / raw-size: 236.57 GiB size: 236.57 GiB (100.00%)
    used: 185.75 GiB (78.5%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  ID-2: /boot/efi raw-size: 302 MiB size: 301.3 MiB (99.79%)
    used: 584 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 236.57 GiB size: 236.57 GiB (100.00%)
    used: 185.75 GiB (78.5%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  ID-4: /var/log raw-size: 236.57 GiB size: 236.57 GiB (100.00%)
    used: 185.75 GiB (78.5%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
  ID-5: /var/tmp raw-size: 236.57 GiB size: 236.57 GiB (100.00%)
    used: 185.75 GiB (78.5%) fs: btrfs block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 7.42 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3
  ID-2: swap-2 type: zram size: 23.44 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 27.4 C mobo: N/A gpu: nvidia temp: 44 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
  Processes: 268 Uptime: 25m wakeups: 2 Memory: 23.44 GiB
  used: 4.67 GiB (19.9%) Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: 1944
  pm: pacman pkgs: 1940 libs: 509 tools: pamac,paru,yay pm: flatpak pkgs: 4
  Shell: garuda-inxi (sudo) default: Bash v: 5.1.16 running-in: yakuake
  inxi: 3.3.26
Garuda (2.6.16-1):
  System install date:     2021-06-15
  Last full system update: 2023-04-11
  Is partially upgraded:   No
  Relevant software:       timeshift NetworkManager mkinitcpio nvidia-dkms
  Windows dual boot:       Yes
  Failed units:
2

Maybe you could check the bugs.kde.org for something similar.
If changing a setting in Plasma’s own panel doesn’t do anything, the first place I would go for is bugs.kde.org.
Googling might also come up with results as sometimes old issues may rehappen, although I have no idea if this one even happened.

3

How interesting... 468217 – xf86-input-libinput 1.3.0 DPI and mouse acceleration issue on KDE Plasma X11

5 Likes
4

Making the Changes Persistent

The method explained above changes settings for active session only. When you reboot the system, these changes will be gone. To make them persistent, two approaches can be used.

The first method requires you to add these commands to startup applications. …

3 Likes
5

Good to know it's already been reported. Guess I'll just stick to manual workarounds until someone at KDE fixes it. Or I get tired and create a config file.

1 Like
6
  1. Downgrade x86-input-libinput
  2. Place a HoldPkg IgnorePkg x86-input-libinput in /etc/pacman.conf
    :question: :question: :question:

EDIT: Corrected. Thanks! :slight_smile:

1 Like
7

I think it's IgnorePkg?

4 Likes
8

Yes, I am sure he meant IgnorePkg. HoldPkg would not be useful in this case.

HoldPkg = package …

If a user tries to –remove a package that’s listed in HoldPkg, pacman will ask for confirmation before proceeding. Shell-style glob patterns are allowed.

IgnorePkg = package …

Instructs pacman to ignore any upgrades for this package when performing a –sysupgrade. Shell-style glob patterns are allowed.

I think it is a good suggestion though: downgrade the package and add it to IgnorePkg. Check on it again in a couple weeks.

...
IgnorePkg = xf86-input-libinput
...
3 Likes
9

@adamski234 The bug is now in RESOLVED FIXED and will be part of 5.27.5.

Mouse acceleration profiles now work properly when using Libinput 1.3 or later (Ilia Kats, Plasma 5.27.5. Link)

I will close this.

4 Likes
10

Fixed by KDE dev. YEAH! :smiley: