I am using KDE Plasma 6.3.5 Wayland on Arch Linux x86_64.
I tried to ask chatgpt for help and done everything it wanted but mouse acceleration is still enabled, in short chatgpt told me to: create libinput override [sudo nano /etc/libinput/local-overrides.hwdb] and in there paste these: [# Disable mouse acceleration for Attack Shark X3
libinput:name:Attack Shark X3
LIBINPUT_ATTR_ACCEL_PROFILE=flat
LIBINPUT_ATTR_ACCEL_SPEED=0.0]
after that didnt work it asked me to do these: use flat profile via kwinrc hack (Plasma compositor rule) [nano ~/.config/kwinrc]
add this to the end:
[Input]
PointerAccelerationProfile=flat
PointerAcceleration=0.0
Save and restart KWin:
qdbus org.kde.KWin /KWin reconfigure
All of these didnt work and I gave up.
In sudo libinput list-devices it showed this all of the time:
Device: Beken USB Gaming Mouse
Kernel: /dev/input/event6
Id: usb:1d57:fa61
Group: 7
Seat: seat0, default
Capabilities: pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap button map: n/a
Tap drag lock: n/a
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: button
Scroll button: BTN_MIDDLE
Scroll button lock: disabled
Click methods: none
Clickfinger button map: n/a
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: flat *adaptive custom
Rotation: 0.0
Area rectangle: n/a
I couldnt find any tutorials online for this. Please someone help me.
Additional infos:
mouse: Attackshark x3 (in libinput: Beken USB Gaming Mouse)
kernel: Linux 6.14.7-arch2-1
WM: KWin (Wayland)
Just disable it using systemsettings. Make sure you have the correct mouse selected, even if you have only 1 mouse connected. Sometimes gaming mice and keyboards show up double.
as a temporary workaround for the acceleration issue, i set acceleration mode to Adaptive and set the pointer speed to the lowest possible, but before this i checked this file and everything was on:
PointerAcceleration=0,000
PointerAccelerationProfile=1
When this happens, the mouse itself presents itself as several different USB devices, as if you had a USB hub with mouse/keyboard/etc. connected. We can try to filter out some of the less relevant devices, but we’d have to rely on heuristics and might run into problems where sometimes the device we hide is actually something that the user wants to configure.
The medium-term plan is to sort the devices in the Mouse settings page by how recently they’ve been used. That should prevent much of the problem that the user configures the wrong device whose settings aren’t actually being used. Then look into ways that we could perhaps trim the list in a way that hopefully doesn’t throw out devices that should be configurable.