Bug 411668

Summary:	Different mouse pointer speed on wayland with the same settings
Product:	[Applications] systemsettings	Reporter:	Matej Mrenica <matejm98mthw>
Component:	kcm_mouse	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED FIXED
Severity:	major	CC:	filipfila.kde, matejm98mthw, nate, unassigned-bugs
Priority:	NOR
Version:	5.16.5
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Matej Mrenica 2019-09-07 10:05:41 UTC

STEPS TO REPRODUCE
1. In Xorg session set mouse pointer speed to a value of, for example, 2 (second slider position)
2. Relogin into a wayland session

OBSERVED RESULT
Mouse pointer speed is different, and even setting it to the same value as in Xorg session results in different pointer speed than on Xorg

EXPECTED RESULT
Same pointer speed in both Xorg and Wayland session out-of-the-box.
Setting the speed to a certain value changes it in both sessions.
A certain value means the same speed in both Xorg and Wayland sessions.

BONUS
Also make SDDM respect these settings.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.16.5 and master
KDE Frameworks Version: 5.61 and master
Qt Version: 5.13.0 and 5.12.X

ADDITIONAL INFORMATION
Using libinput, tested on Arch Linux Stable and KDE Neon unstable

Comment 1 Nate Graham 2019-09-12 15:34:33 UTC

KWin handles input directly on Wayland. Moving there for now.

Comment 2 Vlad Zahorodnii 2020-04-16 10:41:30 UTC

Do you have a HiDPI monitor?

Comment 3 Vlad Zahorodnii 2020-04-16 10:48:42 UTC

Changing the status of the bug report to NEEDSINFO WAITINGFORINFO.

Comment 4 Bug Janitor Service 2020-05-01 04:33:09 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Matej Mrenica 2020-05-01 11:30:26 UTC

The issue as described doesn't happen anymore.

There are two other issues present though:
1. Changing cursor speed doesn't change cursor speed in Wayland and vice versa.
2. SDDM doesn't respect cursor speed settings.

Should I create separate reports for them?

Comment 6 Nate Graham 2020-05-01 13:07:32 UTC

Yes please. Not sure #2 is fixable though. If it is, Filip will know! :)

Comment 7 Matej Mrenica 2020-05-01 14:09:08 UTC

(In reply to Nate Graham from comment #6)
> Yes please. Not sure #2 is fixable though. If it is, Filip will know! :)

https://bugs.kde.org/show_bug.cgi?id=420857 and https://github.com/sddm/sddm/issues/1252

Comment 8 Filip Fila 2020-05-01 14:37:13 UTC

(In reply to Nate Graham from comment #6)
> Yes please. Not sure #2 is fixable though. If it is, Filip will know! :)

I don't see any pointer speed property we can set in SDDM's config file. I also tried to see if it would read our kcminputrc file and it can't.

It's probably a similar situation as with fonts: it's following some Qt default setting and modifying plus exposing the option would require an SDDM patch.

We'd then add that to list of things synced in sddm-kcm.