#Ubuntu disable mouse acceleration install
#Ubuntu disable mouse acceleration drivers
#Ubuntu disable mouse acceleration update
#Ubuntu disable mouse acceleration driver
#Ubuntu disable mouse acceleration software

(Cue rant about wishing Wayland and Pipewire would die in a fire.)Īt the very least always have a term open running dmesg -Hw or tail -f /var/log/syslog and see if something is happening when you notice the input drop. If you are in Wayland switch to an X session and see if the issue goes away. Or you could try a less piggish DE like XFCE.Īnother thing is also what ARE you running? X or Wayland? There is a chance given Gnome and mainline Ubuntu that you’re in Wayland which would be a potential issue. This might be useful to see if it’s a dpi/input issue or dropped frames. There was an application to show fps even on desktop use.

#Ubuntu disable mouse acceleration driver

While it’s not hangs that are the issue (my nv driver kinda hangs my whole system too frequently when I have heavy separate 3D workloads across my GPU’s) Gnome is a pig and its compositor may be to blame. Libinput Accel Profile Enabled Default (302):đ, 0Ġ, 1 value should mean disabled under libinput Accel Profile Enabled Libinput Accel Profile Enabled (301):Đ, 1 Libinput Accel Profiles Available (300):đ, 1 However doing list props shows as the acceleration disabled for both: xinput list-props 'Logitech Gaming Mouse G600' | grep Accel I think that might be related to keyboard USB hub? Since same brand as keyboard. I think the one in tweaks extension should be the current used setting replacing the xorg setting which is already disabled.Īs for showing multiple devices, I think mine is just one device? I checked lsusb.Īnd “xinput list” shows a different brand mouse(?) along logitech.

#Ubuntu disable mouse acceleration drivers

The two drivers use different options which I guess is why your file doesn’t work anymore.” by user ropid Today the one used by default is “libinput”. “In the past, Xorg used an input driver named “evdev”. That also didnt fix it, still random slow downs even with only one DPI I don’t think /nf is used anymore. So I tried one more thing while in the software, I deleted ALL DPI levels except one main one on all onboard mouse profiles. I found however a “G Shift” setting which is like the sniper button, but it wasnt set to anything after all.

#Ubuntu disable mouse acceleration software

So I checked the mouse software and there was no mouse acceleration option for on-board mouse profiles.

#Ubuntu disable mouse acceleration install

So to test this I would need to format the computer using an old iso like 20.04.1 and don’t install any updates but I would like to avoid that.ĭoes anyone have any ideas what could be the issue? Or any settings/logs to check? USB power saving? Different mouse acceleration setting? However a recent install of 20.04.3 iso has this issue from the start.

#Ubuntu disable mouse acceleration update

If I remember right, I didn’t have this issue when I first installed 20.04 and it might have been an update that did something. Mouse acceleration is set to flat (off) using tweaks. It only happens on Ubuntu while windows is fine. I tried checking logs just after the slowdown happens but nothing seems out of the ordinary. I tried 3 different mouses (redragon, razer, logitech), swapped the usb cable, tried different usb ports and it’s still the same. I’m using Ubuntu 20.04 LTS, x299 mobo with 10980xe, L1 KVM and a Logitech gaming mouse. I definitely need to slide it further when it feels slow hence it feels like DPI dropped randomly. I even tried to eyeball it by checking how long it takes to go from left edge of screen to right and the mouse distance traveled from edge of mouse pad. The mouse keeps randomly slowing down, it feels like the DPI drops by half for like 5-10 seconds and then it’s back to normal. I could be wrong, and maybe this is a hardware bug, but that's how I see it.I have a weird mouse issue that is driving me nuts. But I imagine this has more to do with hardware (both the mouse and the display) than anything else. Personally, changing the setting between the maximum and minimum barely has any noticeable difference to me. That is, since your measurement is less fine, the movement on the screen is correspondingly jumpy, which might make it seem faster. But since these two actions correspond to the same movement of the mouse, the cursor will need to 'jump' a little bit to fill in the 'gaps' in data. Now it might only take 100 readings during the same 1 cm (because it's less sensitive to movement). Now suppose we set the sensitivity very low. Each of those readings corresponds to a piece of data determining where the mouse moves. If the mouse sensitivity is very high, it might take 1000 readings during that 1 cm. During that time, the mouse takes a series of readings about it's location which then determine where the mouse should move on the screen. I think this makes sense, but it's just unintuitive.