Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

491

Please share if you have figured this out. I've just changed updated to the new Debian release and what I'm finding is - mouse scroll wheel speed is now unusable fast - gnome does not have an adjustment in settings, tweaks - much of the guidance you find on line applies to X but not to Wayland - The Wayland, compositor, and client developers have been in a multiyear food fight over who's supposed to do something about this - but nobody appears to actually do something about this. - You'd think that a usable mouse would be something that people would consider important these days. - My mouse worked better in Linux 30 years ago than it does today.

I'm thinking udev/hwdb but I can't figure out how to set a value for POINTER_SCROLL_WHEEL which is the problem event.

inb4 KDE or Sway or different mouse, please. I'll eventually consider these, but you'd think this would be treatable.

Please share if you have figured this out. I've just changed updated to the new Debian release and what I'm finding is - mouse scroll wheel speed is now unusable fast - gnome does not have an adjustment in settings, tweaks - much of the guidance you find on line applies to X but not to Wayland - The Wayland, compositor, and client developers have been in a multiyear food fight over who's supposed to do something about this - but nobody appears to actually do something about this. - You'd think that a usable mouse would be something that people would consider important these days. - My mouse worked better in Linux 30 years ago than it does today. I'm thinking udev/hwdb but I can't figure out how to set a value for POINTER_SCROLL_WHEEL which is the problem event. inb4 KDE or Sway or different mouse, please. I'll eventually consider these, but you'd think this would be treatable.
[–] • 1 pt (edited )

Is this only in specific programs or system wide? I looked into it a little and it seems like Wayland allows each app to set stuff like this on its own. Someone suggested this if you use firefox.. If I find anything else interesting ill edit my post.

Are you using Firefox? In Firefox you can change the scroll rate:

In the address bar type: about:config Click on ‘Accept risk and continue’ button (or simular words)

In the Search bar, type:

mousewheel.min_line_scroll_amount

Double click on the entry and change the value to anything 5 - 60 . 5 = Slow , 60 = Fast . I prefer 60

[Edit] It looks like wayland uses libinput too. https://wayland.freedesktop.org/libinput/doc/latest/wheel-api.html

Where to configure: (Note, log out/log back in or reboot will be needed after creating the udev vile to load it). https://wayland.freedesktop.org/libinput/doc/latest/faqs.html#how-do-i-configure-my-device-on-wayland

This post has suggestions for Fedora, you will need to figure out the proper debian packages to install rather than using DNF though. https://archive.is/wip/R1QI1

[–] • 1 pt (edited )

Thanks - the Fedora bit is new information for me. The API document wasn't helpful for me. The libinput thing may be a new approach.

Is this only in specific programs or system wide?

It's complicated. Firefox is tolerable but not ideal. There are other applications which both lack a setting that I'm aware of and the system wide default is unusable. So I'd like to temper this system wide so that the scroll function of the mouse is useful generally - and then maybe I'd need to speed up Firefox. For other apps touching the scroll wheel takes you from max zoom to min zoom in without exception. I believe that maybe the scroll-wheel click angle is maybe 120 degrees instead of 15.

Doing this through systemd-hwdb looks promising, but every time systemd-anything looks promising it just turns into bewilderment and dissatisfaction. This is where I'm at now.

I know the device is /dev/input/event17. I know the bus, vendor, device from udevadm info: - DEVPATH=/devices/virtual/misc/uhid/0005:045E:0932.0006/input/input47/event17 - Bus = 0005 (bluetooth), Vendor = 045E (Micro$oft), Device = 0932 (arc mouse)

Now I can identify the device for hwdb:

evdev:input:b0005v045Ep0932* MOUSE_WHEEL_CLICK_ANGLE=15

This gives me the message

/etc/udev/hwdb.d/70-arc-mouse.hwdb:3: Property expected, ignoring record with no properties.

... but I read that the format for the hwdb file is the evdev identifier followed by lines of key=value. That part doesn't align with the error message that "property is expected" - MOUSE_WHEEL_CLICK_ANGLE looks like a property to me.

[–] • 0 pt

To hell with it. xD I have an old mouse in my desk drawer that works right.

[–] • 0 pt

wayland, something nobody wanted and is WORSE than X11

systemd, something NOBODY wanted and is worse than any other kind of init

have you tried latest eclipse cdt ? a gigantic pile of shit, the latest buzzword is LLVM, that is ANOTHER layer of idiocracy over a compiler

my motto ?

you generation LOVE to reinvent the wheel as an hexagon

not to mention RUST, really, if you cannot handle c or c++ you are NOT fit for purpose

python ? a language written to avoid typing {}

[–] • 1 pt

you [sic] generation LOVE to reinvent the wheel as an hexagon

Planned development of additional sides this will better approximate the wheel.

Sadly scroll speed is yet unplanned except for a few applications.

[–] • 0 pt

You realize Wayland is a protocol, like X11, right? Blame the idiots who programmed the implementation in each desktop environment.

[–] • 0 pt

we do NOT need ANOTHER protocol, we ALREADY have a protocol

if the children do not understand it, they need to study it

NOT reinvent the wheel as an HEXAGON

[–] • 0 pt

I agree with you, but I think they had good intentions. It just ended up sucking.