Bug 459146 - Pointer twice too big on KDE apps using Wayland and 200% scaling
Summary: Pointer twice too big on KDE apps using Wayland and 200% scaling
Status: RESOLVED DUPLICATE of bug 448555
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.25.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-15 09:54 UTC by frederic.parrenin@univ-grenoble-alpes.fr
Modified: 2023-01-17 16:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description frederic.parrenin@univ-grenoble-alpes.fr 2022-09-15 09:54:41 UTC 
STEPS TO REPRODUCE
Use the Wayland session on KDE, with a 4k screen with 200% scaling
(this is with the breeze theme)

OBSERVED RESULT
The pointer size is correct for some apps (firefox/wayland, thunderbird/wayland, chrome/wayland, zoom), but it is twice too big on some other apps (PlasmaShell, KDE apps, master-pdf, LibreOffice/kf5).
Strange also that in some other apps, the pointer seems too big, but only by ~50% (TeamViewer, OnlyOffice).

EXPECTED RESULT
The pointer size should be the same everywhere.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Bookworm
(available in About System)
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.4
Comment 1 Vlad Zahorodnii 2022-09-15 11:34:28 UTC 
Looks fine on my machine, what cursor size do you have?
Comment 2 frederic.parrenin@univ-grenoble-alpes.fr 2022-09-15 13:04:16 UTC 
36 px.
Comment 3 Vlad Zahorodnii 2022-09-15 13:39:48 UTC 

*** This bug has been marked as a duplicate of bug 459161 ***
Comment 4 Vlad Zahorodnii 2022-09-15 13:41:44 UTC 
As a workaround, use 24px cursor size.
Comment 5 Nate Graham 2023-01-17 16:33:21 UTC 
Not quite a duplicate of Bug 459161; rather a sub-task of it given that it's an umbrella bug.

*** This bug has been marked as a duplicate of bug 448555 ***