Bug 401629

Summary:	Changing DPI scaling and back doesn't restore the mouse cursor size
Product:	[Applications] systemsettings	Reporter:	Mark <markg85>
Component:	kcm_cursortheme	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	kde
Priority:	NOR
Version:	5.14.4
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Mark 2018-12-01 23:24:11 UTC

Hi,

I tried DPI scaling on a 4k monitor to 1.5, as that seemed to look nice to me.
The mouse scaling looks fine when set at that (or 2, also tried that).

But when reverting back to 1 the mouse scaling seems completely wrong! I did revert it back to a px setting in the settings panel (Workspace Theme -> Cursor Theme). That fixed it for the user session, also after logging in again so that seem to be persistent (good!).

Note: the "Cursur Theme"  page has a "Resolution dependent" option and a few px options. I can set it to a px and it will apply, but the next time i open that window it is again set at "resolution dependent". That on it's own is also a bug.

However, the SDDM theme is now still wrong and huge. To this moment, i haven't found a fix for that one yet.

Also, i never entered my password for the DPI change so i really wonder how DPI settings are now seemingly changed outside the scope of my user.

Please do let me know if you need some logs to debug this issue.

Comment 1 David Edmundson 2018-12-28 11:56:21 UTC

X or wayland?

Comment 2 Mark 2018-12-28 15:49:46 UTC

(In reply to David Edmundson from comment #1)
> X or wayland?

X

The issue is now gone though. I have two displays again with the same resolution (not a third with 4k) which "solves" it. But adding that 4K one again makes the other displays (1080p) huge. I guess the scaling is for all monitors, not per monitor.

Comment 3 David Edmundson 2018-12-28 18:57:54 UTC

>I guess the scaling is for all monitors, not per monitor.

That is correct under X.

Comment 4 David Edmundson 2019-01-23 14:41:43 UTC

There's not a lot we can do. 

We set the mouse cursor value to resolution independent, but it's the applications themselves that are calculating what do with that information.
Sorry.

The situation on wayland is much improved.