Mouse sensitivity radically different after update

After updating just now and rebooting, my mouse sensitivity feels very different. Before updating, sensitivity was at the 4th increment in the pointer speed slider, but now the 4th increment is way too fast, the 2nd increment is slightly too fast and the 1st increment is slightly too slow. Both set to “flat” before and after. Why did it change?
My mouse has 4 DPI levels on the mouse itself and they are color-coded so I know I did not accidentally change it, it’s the same color before and after. What’s going on?

What got updated? Are you on wayland or Xorg? Are you using ibinput?

You might want to read this Arch wiki article: https://wiki.archlinux.org/title/Mouse_acceleration

Is it possible for you to set the mouse acceleration to a satisfying value now?

I’m on Xorg, using whatever EOS sets up by default. Lots of things got updated so I didn’t pay attention, is there a way to see what got updated in my most recent update?
Will check out that article.

 grep -i upgraded /var/log/pacman.log

should give you the upgraded packages with time stamp from the pacman log.

If the article helps you to set a satisfactory mouse accleration that would be good.

1 Like

The output of that

[2023-04-09T16:39:53-0300] [ALPM] upgraded adobe-source-code-pro-fonts (2.038ro+1.058it+1.018var-1 -> 2.040u+1.060i+1.024vf-1)
[2023-04-09T16:39:53-0300] [ALPM] upgraded alsa-card-profiles (1:0.3.67-1 -> 1:0.3.68-1)
[2023-04-09T16:39:53-0300] [ALPM] upgraded systemd-libs (253.2-1 -> 253.3-1)
[2023-04-09T16:39:53-0300] [ALPM] upgraded wayland (1.21.0-2 -> 1.22.0-1)
[2023-04-09T16:39:53-0300] [ALPM] upgraded libnghttp2 (1.52.0-1 -> 1.52.0-2)
[2023-04-09T16:39:53-0300] [ALPM] upgraded coreutils (9.2-2 -> 9.2-3)
[2023-04-09T16:39:53-0300] [ALPM] upgraded egl-wayland (2:1.1.11-3 -> 2:1.1.11-4)
[2023-04-09T16:39:53-0300] [ALPM] upgraded hwdata (0.368-1 -> 0.369-1)
[2023-04-09T16:39:53-0300] [ALPM] upgraded systemd (253.2-1 -> 253.3-1)
[2023-04-09T16:39:54-0300] [ALPM] upgraded xf86-input-libinput (1.2.1-1 -> 1.3.0-1)
[2023-04-09T16:39:54-0300] [ALPM] upgraded mesa (23.0.1-1 -> 23.0.2-2)
[2023-04-09T16:39:54-0300] [ALPM] upgraded bluedevil (1:5.27.3-1 -> 1:5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded kdecoration (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded breeze (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded breeze-gtk (5.27.3-1 -> 5.27.4-2)
[2023-04-09T16:39:55-0300] [ALPM] upgraded eos-translations (23-17 -> 23-18)
[2023-04-09T16:39:55-0300] [ALPM] upgraded libpipewire (1:0.3.67-1 -> 1:0.3.68-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded pipewire (1:0.3.67-1 -> 1:0.3.68-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded pipewire-audio (1:0.3.67-1 -> 1:0.3.68-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded pipewire-jack (1:0.3.67-1 -> 1:0.3.68-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded fluidsynth (2.3.1-2 -> 2.3.2-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded fzf (0.38.0-1 -> 0.39.0-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded gst-plugin-pipewire (1:0.3.67-1 -> 1:0.3.68-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded imagemagick (7.1.1.5-1 -> 7.1.1.6-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded kactivitymanagerd (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded kde-cli-tools (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded kde-gtk-config (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded libmfx (23.1.3-2 -> 23.1.6-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded libksysguard (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded ksystemstats (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded milou (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded layer-shell-qt (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded libkscreen (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded kscreenlocker (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded kwin (5.27.3-2 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded plasma-integration (5.27.3-2 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded kpipewire (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:55-0300] [ALPM] upgraded oxygen-sounds (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:56-0300] [ALPM] upgraded plasma-workspace (5.27.3-1 -> 5.27.4.1-1)
[2023-04-09T16:39:56-0300] [ALPM] upgraded khotkeys (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:56-0300] [ALPM] upgraded systemsettings (5.27.3-1 -> 5.27.4.1-1)
[2023-04-09T16:39:56-0300] [ALPM] upgraded kinfocenter (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:56-0300] [ALPM] upgraded kmenuedit (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:56-0300] [ALPM] upgraded kscreen (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:56-0300] [ALPM] upgraded kwallet-pam (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:56-0300] [ALPM] upgraded lib32-mesa (23.0.1-1 -> 23.0.2-2)
[2023-04-09T16:39:57-0300] [ALPM] upgraded linux (6.2.9.arch1-1 -> 6.2.10.arch1-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded linux-headers (6.2.9.arch1-1 -> 6.2.10.arch1-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded man-pages (6.03-1 -> 6.04-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded mlt (7.14.0-2 -> 7.14.0-5)
[2023-04-09T16:39:59-0300] [ALPM] upgraded nvidia-installer-common (23-4 -> 23-5)
[2023-04-09T16:39:59-0300] [ALPM] upgraded nvidia-inst (23-3 -> 23-4)
[2023-04-09T16:39:59-0300] [ALPM] upgraded pacman-contrib (1.8.2-1 -> 1.9.0-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded parallel (20230222-1 -> 20230322-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded pipewire-alsa (1:0.3.67-1 -> 1:0.3.68-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded pipewire-pulse (1:0.3.67-1 -> 1:0.3.68-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded polkit-kde-agent (5.27.3-1 -> 5.27.4.1-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded powerdevil (5.27.3-1 -> 5.27.4.1-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded plasma-desktop (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded plasma-disks (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded plasma-nm (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded plasma-pa (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded plasma-systemmonitor (5.27.3-1 -> 5.27.4-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded rubberband (3.1.2-1 -> 3.2.1-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded sddm-kcm (5.27.3-1 -> 5.27.4.1-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded systemd-sysvcompat (253.2-1 -> 253.3-1)
[2023-04-09T16:39:59-0300] [ALPM] upgraded yay (11.3.2-1 -> 12.0.3-1)

That might have caused your issue.

To avoid that problem with future updates you could create a config file as recommended under section 1.2 in the link from the arch wiki. You just have to find a good value for the mouse acceleration that’s fitting for you.

Same issue here, mouse sensitivity is completely different after the update. Quite annoying. The reason it’s annoying, is that there’s been zero change for more than a year, at the very least. Now, I need to figure out how to get that exact sensitivity again, and my previous muscle memory is going to make things worse for a while.

The mouse acceleration setting is flat, which should mean that there’s zero acceleration. It’s the mouse raw sensitivity that has changed, for some reason.

From here: https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html

It says: The **flat** profile is simply a constant factor applied to all device deltas, regardless of the speed of motion (see [The flat pointer acceleration profile](https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html#ptraccel-profile-flat)).

So it’s a fixed value, but not necessarily zero.

I guess if you want to have the same feel as prior the update you would have to find a value for acceleration speed (between -1 and 1) that reflects your muscle memory best.

See the detailed explanation - https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html#the-flat-pointer-acceleration-profile.

In a flat profile, the acceleration factor is constant regardless of the velocity of the pointer and each delta (dx, dy) results in an accelerated delta (dx * factor, dy * factor). This provides 1:1 movement between the device and the pointer on-screen.

This is practically the same meaning as no acceleration. The pointer moves the same distance on screen for the same distance on the mouse pad, regardless of whether I’m moving my mouse at a snail’s pace or in a rapid movement.

What has changed with the update, is the distance the pointer moves. Without me changing the pointer speed or the acceleration profile for the mouse in system settings. I just hope it doesn’t change again.

@drinktheocean There’s a possible solution here to get your sensitivity as it was. Install the previous version by running
pacman -U https://archive.org/download/archlinux_pkg_xf86-input-libinput/xf86-input-libinput-1.2.1-1-x86_64.pkg.tar.zst and then restarting Plasma or the system.

You should get your old sensitivity back. Measure how much your mouse moves for a fixed distance on the screen.

Run your package update command, it’ll want to install the updated version again. Then you can try and configure the settings to match the above recorded distance and get the exact sensitivity configured with the latest version.

But shouldn’t you be able to set the AccelSpeed-value in a respective xorg-conf-file to a value that’s not zero, even though you are using a flat profile?

I also just read in the Arch wiki that KDE settings apparently can overwrite the settings from an Xorg conf.

Apparently the respective Plasma configuarations are under ~/.config/kcmiputrc

(Not using Plasma myself)

Yeah, going by xinput --list-props <device-id>, the libinput Accel Speed is set to -0.4 (4th bar in KDE System Settings). The libinput Accel Speed is set to 0.0. The whole output is below (this is with the older package installed).

 14:50:40  ~                                                                                                                                                                                                                                                                                         took 12s  21.7G RAM 
❯ xinput --list-props 23
Device 'Logitech G604 ':
	Device Enabled (156):	1
	Coordinate Transformation Matrix (158):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Natural Scrolling Enabled (284):	0
	libinput Natural Scrolling Enabled Default (285):	0
	libinput Scroll Methods Available (286):	0, 0, 1
	libinput Scroll Method Enabled (287):	0, 0, 0
	libinput Scroll Method Enabled Default (288):	0, 0, 0
	libinput Button Scrolling Button (289):	2
	libinput Button Scrolling Button Default (290):	2
	libinput Button Scrolling Button Lock Enabled (291):	0
	libinput Button Scrolling Button Lock Enabled Default (292):	0
	libinput Middle Emulation Enabled (293):	0
	libinput Middle Emulation Enabled Default (294):	0
	libinput Rotation Angle (267):	0.000000
	libinput Rotation Angle Default (268):	0.000000
	libinput Accel Speed (295):	-0.400000
	libinput Accel Speed Default (296):	0.000000
	libinput Accel Profiles Available (297):	1, 1
	libinput Accel Profile Enabled (298):	0, 1
	libinput Accel Profile Enabled Default (299):	1, 0
	libinput Left Handed Enabled (302):	0
	libinput Left Handed Enabled Default (303):	0
	libinput Send Events Modes Available (269):	1, 0
	libinput Send Events Mode Enabled (270):	0, 0
	libinput Send Events Mode Enabled Default (271):	0, 0
	Device Node (272):	"/dev/input/event24"
	Device Product ID (273):	1133, 16517
	libinput Drag Lock Buttons (304):	<no items>
	libinput Horizontal Scroll Enabled (305):	1
	libinput Scrolling Pixel Distance (306):	15
	libinput Scrolling Pixel Distance Default (307):	15
	libinput High Resolution Wheel Scroll Enabled (308):	1

Seems like it’s a bug in the interaction between KDE and the latest version of xf86-input-libinput? Turns out there’s some unintended acceleration. I’m a bit puzzled, cause for me, I couldn’t see any acceleration. :sweat:

I looked at the code changes, could be due to KDE not working as expected with the new custom acceleration profile feature. https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/compare/xf86-input-libinput-1.2.1...xf86-input-libinput-1.3.0?from_project_id=577&straight=false

https://bugs.kde.org/show_bug.cgi?id=468217

Okay, so as a workaround is it possible to set is with an Xorg config file?

I assume at some point it will get fixed by a KDE update then

Just wanted to update, with the latest updates to KDE apps, this is now fixed. It’s safe to update to the latest version of xf86-input-libinput, without having your sensitivity changed unexpectedly.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.