In general we try not to override upstream defaults, but in this case there are no upstream defaults! So it's a reasonable request.

Personally I think it's premature to change the default since there is no particularly unified scroll speed across apps. Increasing the scroll speed globally to make one app's scrolling feel better will very likely make another app's scroll speed feel absurdly fast (and vice versa). For example scrolling in Firefox with MOX_USE_XINPUT2=1 set to make touchpad scrolling work is super fast and needs to be slower, not faster. Increasing the default would worsen this.

-1 for now, sorry.

Is there even upstream? :)

From my experience, scroll speed is similar in most apps and that should also be the goal if it is not the case right now.

I don't use a touchpad, so I cannot really comment on that. Also, is this really kcm_touchpad and not kcm_mouse (or both)?

With mice (I have two different) scrolling in Firefox feels too slow for me.

So, maybe if the defaults of touchpads and mice are independent, only the default for mice can be increased - after making sure nothing will get too fast?

Oh I see, you mean just for the mouse.

I can't disagree too much with increasing the default mouse speed. However what I'd *really* like is acceleration for scroll wheels, which would have to be implemented in Libinput: https://gitlab.freedesktop.org/libinput/libinput/-/issues/7

MacOS has this and it's *so much nicer* for navigating a long document or otherwise scrolling large distances. When I left the Mac world I discovered that people commonly bought and used these mice with wheels than can optionally spin freely to approximate the same thing using hardware, but it's totally unnecessary if you have acceleration in software.

Yes, I was mostly referring to mice, although I also had touchpads in mind / wasn't really aware of the distinction. Since touchpads seem to be problematic and I also don't have one, we can make this bug about mice only.

Having used the new scroll speed setting for some time I really like the faster scroll speed. So also having faster speed can have a huge impact! I also have a Logitech MX Master with this freely spinning thing, but still on Linux that was not really a nice experience and did not really fix the slow speed. Because you have to accelerate it all the time since the distance scrolled with each spin is maybe half the distance it goes on Windows.

I am also looking forward to having scroll acceleration in the future. I never had it, but guess it is a pretty nice thing to have.

The correct place for implementation is still a matter of discussion, afaik. There is this issue for Libinput and it might get eventually implemented there, but I think I remember a statement that this might have disadvantages (since libinput does not know the context of the scroll event). At least I think that was the reason for not implementing scroll speed and I don't see why scroll acceleration would be so much different. However, implementing it in Libinput might be still a good way. It is just not the only possible way :) Let's see how that issue moves forward.

From reading the comments there, I assume that input from the users of Libinput like KDE is probably appreciated in order to get to a nice working solution. So if you know some experts on the KDE side, maybe this issue can be continued as a collaborative effort and you can make sure that Libinput knows what you need :)

Adding Méven Car to CC, since he did the implementation of the setting.

Closing as this isn't really actionable for the reason I gave earlier: it's not obvious that there is in fact a better default scroll speed.