Bug 507845

Summary: Desktop icons do not highlight or respond on Wayland when mouse approaches vertically through multi-line label
Product: [Plasma] plasmashell Reporter: diego.alfaro
Component: Desktop icons & Folder View widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: normal CC: hein
Priority: NOR    
Version First Reported In: 6.3.4   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screencast of the bug

Description diego.alfaro 2025-08-04 09:01:52 UTC
Created attachment 183775 [details]
Screencast of the bug

Steps to reproduce:
Log into Plasma 6.3.4 Wayland session.
Place a desktop icon with a long filename that wraps to 2 or more lines.
Move the mouse vertically from below, passing over the text label first before the icon itself.

Observe that:
The icon does not highlight.
The icon cannot be clicked until you move horizontally or away and back.
Reduce the label to 1 line → bug disappears.

Expected result:
Icons should highlight and respond to clicks regardless of approach direction, like in X11.

Actual result:
On Wayland, multi-line text labels create a “dead zone” where vertical hover does not trigger icon highlight or clicks.
Horizontal approach works normally.

Workarounds:
Use single-line labels.

System info:
Ubuntu 25.04 (Plucky Puffin)
Kernel: 6.14.0-27-generic
Plasma: 6.3.4
KWin: 6.3.4
XDG_SESSION_TYPE=wayland
GPU: Intel Arc (MTL)
Comment 1 Bug Janitor Service 2025-08-04 09:33:39 UTC
Thank you for the bug report!

However Plasma 6.3.4 no longer receives updates or maintenance from KDE; active versions are 6.4 or newer. Please upgrade to an active version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one.

If you need help with Plasma 6.3.4, please contact your distribution, who bears the responsibility of providing help for older releases that are no longer receiving updates from KDE.

If you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.