Bug 407749 - Cursor size changes when hovering over kwin control
Summary: Cursor size changes when hovering over kwin control
Status: RESOLVED DUPLICATE of bug 413783
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_cursortheme (show other bugs)
Version: 5.14.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-20 08:30 UTC by Ralf Jung
Modified: 2019-11-14 21:24 UTC (History)
5 users (show)

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


Attachments
Screenshot with big cursor (84.55 KB, image/png)
2019-05-20 09:34 UTC, Ralf Jung
Details
Screenshot with small cursor (212.96 KB, image/png)
2019-05-20 09:34 UTC, Ralf Jung
Details
Screenshot with small cursor (62.91 KB, image/png)
2019-05-20 09:35 UTC, Ralf Jung
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Jung 2019-05-20 08:30:17 UTC
SUMMARY

The cursor changes whenever it hovers a KWin control (including title bar context menus, the menus that appear when left-clicking a window icon, and moving the cursor over the alt-tab menu): it approximately doubles in size.  Looks like somehow KWin thinks it needs a high-dpi cursor theme when it does not?


STEPS TO REPRODUCE
1. Right-click a title bar, and hover the menu that appears.

OBSERVED RESULT

The cursor doubles in size.


EXPECTED RESULT

The cursor should stay the same as it is for the rest of the system.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION

My internal laptop screen has a resolution of 4K, but I am using it with 1920x1080 (I change between internal and external screens a lot, and with KDE seemingly not supporting dynamic zoom factor changes, that's my only option).  Also, my laptop is one of these weird "reverse prime" machines where the external HDMI port is connected to the NVidia chip, but the internal screen is connected to the Intel chip.  I am using SDDM, and added the following to /usr/share/sddm/scripts/Xsetup :

xrandr --setprovideroutputsource 1 0
xrandr --auto

So SDDM starts on my 4K internal screen, then the external screen gets added (which SDDM does not handle very well, but that's SDDM's problem), then I log in and whenever KDE applies the stored screen configuration the resolution changes from 4K to 1080p. In the midst of this, it seems like KWin gets confused about the cursor theme.
Comment 1 Vlad Zahorodnii 2019-05-20 08:39:07 UTC
Hmm, if you use resolution dependent cursor size, then I would expect the cursor to decrease in its size when you hover window decorations, etc. Unless you force some specific cursor size, e.g. 48.

Can post screenshots? (with normal size and doubled in size)
Comment 2 Ralf Jung 2019-05-20 09:34:12 UTC
Created attachment 120196 [details]
Screenshot with big cursor
Comment 3 Ralf Jung 2019-05-20 09:34:28 UTC
Created attachment 120197 [details]
Screenshot with small cursor
Comment 4 Ralf Jung 2019-05-20 09:35:23 UTC
Created attachment 120198 [details]
Screenshot with small cursor
Comment 5 Ralf Jung 2019-05-20 09:36:51 UTC
> Hmm, if you use resolution dependent cursor size, then I would expect the cursor to decrease in its size when you hover window decorations, etc. Unless you force some specific cursor size, e.g. 48.

"Size" is set to "resolution dependent". But thanks for pointing to that setting, that should make a good work-around.
Comment 6 Vlad Zahorodnii 2019-05-20 12:36:31 UTC
foobar
Comment 7 Nate Graham 2019-05-21 19:34:02 UTC
IMO we need to just remove this "Resolution Independent" setting. It just causes problems like these, of which we have many bug reports.
Comment 8 Nate Graham 2019-10-27 17:16:12 UTC
*** Bug 385920 has been marked as a duplicate of this bug. ***
Comment 9 Nate Graham 2019-10-27 17:16:21 UTC
*** Bug 389178 has been marked as a duplicate of this bug. ***
Comment 10 Nate Graham 2019-11-04 18:22:25 UTC
*** Bug 413783 has been marked as a duplicate of this bug. ***
Comment 11 Nate Graham 2019-11-14 21:24:57 UTC

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