Bug 412004

Summary:	Cursor becomes giant when hovering over shell components with Wayland fractional scaling
Product:	[Plasma] kwin	Reporter:	Brian <brianaberts>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bernie, erin-kde, meven29, nate, sb56637, subdiff
Priority:	NOR	Keywords:	wayland
Version:	git master
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Brian 2019-09-18 01:42:58 UTC

SUMMARY

I've found a big issue with the Wayland fractional scaling, in which when you hover over the plasma desktop or taskbar the cursor becomes humongous (about 3x larger), this is despite what you set in the cursor size setting. Dolphin as well is affected, however Firefox in Xwayland, and other applications running with X seem to not be affected, nor is Kwin's window controls.

I have been using Xrandr fractional scaling without such an issue.

STEPS TO REPRODUCE
1. Set system scale (1080p 14in @ 1.2 scale)
2. Hover over the panel or desktop, dolphin, or other applications which use Wayland such as system settings or discover (I assume all Wayland applications are affected).
3: Notice the cursor inflates to a giant size
5: Hover over firefox, spotify, discord, or kwin's titlebar and note that the cursor appears to shrink back to a normal size.
6: The cursor looks fine in a screenshot even if it's a screenshot of the big or small rendered one.

OBSERVED RESULT

Cursor becomes huge and seems about 3x larger, making it quite unwieldy


EXPECTED RESULT

Cursor stays the same no matter what you hover over, at the correct scale.


SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.16.80
KDE Frameworks Version: 5.63.0
Qt Version: 5.12.3
Kernel Version: 5.2.15-xanmod11
OS Type: 64-bit
Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
Memory: 5.8 GiB of RAM

Comment 1 Bernie Innocenti 2019-09-23 09:11:51 UTC

Confirmed. I have a giant cursor in the desktop and other plasma windows even with the scaling factor set to 1.0.

xdpyinfo says:
  ...
  dimensions:    3440x1440 pixels (820x350 millimeters)
  resolution:    107x105 dots per inch

I don't know the equivalent way to get DPI in Wayland.

Comment 2 Brian 2019-09-24 08:52:43 UTC

(In reply to bernie from comment #1)
> Confirmed. I have a giant cursor in the desktop and other plasma windows
> even with the scaling factor set to 1.0.
> 

You should be able to fix the big cursor issue when using 1.0 scale by going into the cursor settings and logging back into the Wayland session. This behavior is caused by a different bug i think.

Comment 3 Brian 2019-09-24 08:56:40 UTC

(To clarify: Change the cursor size from auto to a set size such as 24) ... I say i think it's a different bug because when i use 1.2 fractional scale (didn't test other scales), even changing it from auto to a set size the bug will persist.

Comment 4 Vlad Zahorodnii 2019-09-24 15:01:47 UTC

Hmm, looks like dolphin, desktop shell, and other clients provide huge cursor surfaces.

Comment 5 S 2019-09-25 12:23:40 UTC

I'm also seeing this, but I'm not running the Wayland session (as far as I know?). SDDM says "Desktop Session: Plasma", and has no other options apart from Openbox. This is with openSUSE Leap 15.1 and all the updated KF5 / KDE / Qt / Plasma repos. Currently at Plasma 5.16.5, KF5 5.61.0, Qt 5.13.1.

Comment 6 Brian 2019-09-25 13:20:48 UTC

(In reply to S from comment #5)
> I'm also seeing this, but I'm not running the Wayland session (as far as I
> know?). SDDM says "Desktop Session: Plasma", and has no other options apart
> from Openbox. This is with openSUSE Leap 15.1 and all the updated KF5 / KDE
> / Qt / Plasma repos. Currently at Plasma 5.16.5, KF5 5.61.0, Qt 5.13.1.

Open the kicker menu and search "Wayland". You should see a application with that name and the description "Information about the Wayland compositor". If when you open that application it is populated with information, then you are on a Wayland session.

Comment 7 Nate Graham 2020-02-25 19:30:15 UTC


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