KDE Random scroll wheel speed

[larienna]

The gui has no option to set the scroll wheel speed. So I modified:

Code: Select all

~/.config/kdeglobals

and set

Code: Select all

WheelScrollLines=5

Now in some applications like Dolphin, the speed is noticeable. In other applications like Okular, when I display a PDF, the scrolling is slow.

So it seems not all applications use that parameter for controlling wheel speed.

I tried to search of the subject, but could not find anything. One user did it by configuring xinput, but xinput does not seem to be installed on my computer.

Any other suggestions?

[blackbird]

On Debian 12 with Wayland there is an option "scrolling speed" for mouse. This works for me, also in Okular.
For X11 this option is not available in the KDE options. So switching to Wayland could be an option. But maybe you have a reason not to use Wayland.

Can't you install xinput on your computer to test if it works?

[larienna]

I am not really familiar with Wayland. It the first time I use KDE. I wanted to give it a try considering I have a more powerful computer. So it's installed with what ever defaults Debian came up with. Apparently X11 is used by default:

Code: Select all

$ echo "$XDG_SESSION_TYPE"
x11

I tried to read a bit about the advantages and disadvantages of Wayland, I don't think it's worth the trouble installing, just for a mouse scroll speed.

I guess I could try Xinput. I'll have to read more about it too.

[larienna]

I installed xinput, and I tried setting the value fast (10) and slow(50). It did not change anything in all the apps I tested. Okular remains slow.

Code: Select all

xinput --set-prop 10 "libinput Scrolling Pixel Distance" 10

It was not clear which ID was really my mouse. I am using a Logitech M525, so I used this ID, but the first 5 items seems to refer to the same device:

Code: Select all

 $ xinput --list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech M525                           	id=10	[slave  pointer  (2)]
⎜   ↳ Logitech Wireless Keyboard PID:4023     	id=11	[slave  pointer  (2)]
⎜   ↳ Logitech Wireless Mouse                 	id=12	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ HD Pro Webcam C920                      	id=9	[slave  keyboard (3)]
    ↳ Logitech Wireless Keyboard PID:4023     	id=13	[slave  keyboard (3)]
    ↳ Logitech Wireless Mouse                 	id=14	[slave  keyboard (3)]

[blackbird]

I tried to read a bit about the advantages and disadvantages of Wayland, I don't think it's worth the trouble installing, just for a mouse scroll speed.

On my installation both X11 and Wayland were installed automatically. At the login screen it can be switched between X11 and Wayland for each login. It could be that the KDE Plasma don't runs stable with Wayland and NVidia graphic cards. At least earlier that was a problem. If you have such a card, maybe that's why your system gives you X11 as default session.

For xinit you could check with

Code: Select all

xinit list-props 10

what settings are available for the M525. If you have luck one is for faster scolling speed. I tried it in a virtual machine and found no option for the virtual mouse.

[None1975]

Wayland is a constantly and very rapidly developing technology. I think (and this is my opinion) that using wayland on Debian 12 is not the best idea. For experiments with wayland, it is better to use a distribution that provides the latest wayland libraries. For example, Arch or Artix...

[blackbird]

Wayland is a constantly and very rapidly developing technology. I think (and this is my opinion) that using wayland on Debian 12 is not the best idea. For experiments with wayland, it is better to use a distribution that provides the latest wayland libraries. For example, Arch or Artix...

As far as I remember Wayland was the default setting at at the display manager after I installed Debian 12 with KDE. Or am I wrong and I switched later?
At least for my Laptop with Intel CPU+iGPU the combination already works without problems. But I know there are some applications which don't support Wayland.

[larienna]

I took a look at the properties again, and it does not seems there are better properties to adjust scrolling:

Code: Select all

$ xinput list-props 10
Device 'Logitech M525':
	Device Enabled (163):	1
	Coordinate Transformation Matrix (165):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Natural Scrolling Enabled (299):	0
	libinput Natural Scrolling Enabled Default (300):	0
	libinput Scroll Methods Available (301):	0, 0, 1
	libinput Scroll Method Enabled (302):	0, 0, 0
	libinput Scroll Method Enabled Default (303):	0, 0, 0
	libinput Button Scrolling Button (304):	2
	libinput Button Scrolling Button Default (305):	2
	libinput Button Scrolling Button Lock Enabled (306):	0
	libinput Button Scrolling Button Lock Enabled Default (307):	0
	libinput Middle Emulation Enabled (308):	0
	libinput Middle Emulation Enabled Default (309):	0
	libinput Accel Speed (310):	0.200000
	libinput Accel Speed Default (311):	0.000000
	libinput Accel Profiles Available (312):	1, 1
	libinput Accel Profile Enabled (313):	1, 0
	libinput Accel Profile Enabled Default (314):	1, 0
	libinput Left Handed Enabled (315):	1
	libinput Left Handed Enabled Default (316):	0
	libinput Send Events Modes Available (284):	1, 0
	libinput Send Events Mode Enabled (285):	0, 0
	libinput Send Events Mode Enabled Default (286):	0, 0
	Device Node (287):	"/dev/input/event4"
	Device Product ID (288):	1133, 16403
	libinput Drag Lock Buttons (317):	<no items>
	libinput Horizontal Scroll Enabled (318):	1
	libinput Scrolling Pixel Distance (319):	15
	libinput Scrolling Pixel Distance Default (320):	15
	libinput High Resolution Wheel Scroll Enabled (321):	1

Another problem, is that even if it worked, it resets to the default value. So I would need to change the property somewhere in a startup script. I am not very familiar with that.

[None1975]

At least for my Laptop with Intel CPU+iGPU the combination already works without problems.

I remember well one fact - when I tried the Debian 12 KDE wayland session, when the computer was automatically locked (desktop), the whole KDE session crashed and automatically restored. Xorg session works without problem. Neither Arch linux nor Artix linux have this problem with wayland session...

[blackbird]

I took a look at the properties again, and it does not seems there are better properties to adjust scrolling:
[...]
Another problem, is that even if it worked, it resets to the default value. So I would need to change the property somewhere in a startup script. I am not very familiar with that.

It seems it need some luck that scroll speed settings work. You could try Solaar which allows to change the mouse settings for Logitech mouses, it's available as package solaar in Debian. I tried it with a M220 and it had not settings for the scroll wheel.

I remember well one fact - when I tried the Debian 12 KDE wayland session, when the computer was automatically locked (desktop), the whole KDE session crashed and automatically restored. Xorg session works without problem. Neither Arch linux nor Artix linux have this problem with wayland session...

Something similar happened to me when I tried it on Ubuntu 22.04 with a Nvidia GPU. Both KDE Plasma and the proprietary GPU driver were not ready for Wayland. I thought it's better now, but it seems not for all systems.

[larienna]

I remember well one fact - when I tried the Debian 12 KDE wayland session, when the computer was automatically locked (desktop), the whole KDE session crashed and automatically restored. Xorg session works without problem. Neither Arch linux nor Artix linux have this problem with wayland session...

Surprisingly, something similar happened today. I resume my computer, and type my password, then ended with with a back screen with a mouse. I was not using Wayland. This was the biggest bug I had so far when resuming from sleep, otherwise sometimes minor glitches happens, like the keyboard not working, or login screen not appearing.

I switched in command line mode, but was not really sure how to restore this. I tried to make the computer sleep to wake it up again, but ended up shutting it down.