Bug 451061 - Menu items become invisible until hovering them on a scaled multi screen setup on wayland
Summary: Menu items become invisible until hovering them on a scaled multi screen setu...
Status: RESOLVED DUPLICATE of bug 432264
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: master
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL: https://youtu.be/qtAlEZGW3_o
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2022-03-03 00:18 UTC by Andrew Shark
Modified: 2022-04-06 19:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Shark 2022-03-03 00:18:51 UTC
In wayland session (x11 is normal), if the screen has scaling (if no scaling, then it is normal), the menu lines are disappearing (shown as black rectangles) when you start moving mouse, until you hover a cursor over lines.

Steps to reproduce:
1. Apply screen scaling, for example, make it 200%.
2. Click volume applet, then click some menu (cheeseburger icon) of any audio device or application
3. The menu will open.
4. Start moving mouse over menu elements

Observed result:
After step 3, the menu elements are visible (they appear on dark background, but I think that is separate bug with transparrency/blur, probably unrelated to current bug).
At step 4, when you start moving mouse to the menu window, you will notice that menu lines are now invisible (shown as black rectangles).
But they become visible again and stay visible after you hover over them. And the special lines like separators are not able to become visible.

Expected result:
At step 4 the menu lines should not become invisible.

See attached video demonstation.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Graphics Platform: Wayland
Graphics Processor: AMD Radeon RX 580 Series
Comment 1 Nate Graham 2022-03-22 00:18:14 UTC
Cannot reproduce with Breeze theme on current git master. I don't see an attachment; did it get lost in transit?
Comment 2 Andrew Shark 2022-03-22 00:41:20 UTC
The video is not attached, but in URL on YouTube.
Comment 3 Nate Graham 2022-03-24 00:41:14 UTC
But what's the URL? Oh! I see you added it to the URL field lol
Comment 4 Nate Graham 2022-03-24 00:44:26 UTC
Thank you for the video. Strange issue.

Does it only affect the Audio Volume applet, or other applets too? What about the Desktop context menu, or the context menu for Task Manager tasks or apps in Kickoff?
Comment 5 Andrew Shark 2022-03-24 00:49:57 UTC
Yeah, sorry if that was not obvious. Isn't that field meant to be used for that? If no, I can attach video directly to bugzilla next time.

In other places there is also a problem. Should I upload another video to YouTube or here in bugzilla?
Comment 6 Nate Graham 2022-03-24 01:22:03 UTC
No worries! If the video is very long and it won't fit here, uploading it to YouTube is fine. But mention the URL in a comment as it's easy to get missed if it's in the URL field. :)
Comment 7 Andrew Shark 2022-03-24 01:54:34 UTC
I have made another video: https://www.youtube.com/watch?v=B1o-mAgp6W8
It is sufficient to have just two full hd monitors. Decreasing the value of right monitor scaling sometimes makes menu to appear normally. And increasing it sometimes makes menu to appear misbehavely. But there is no exact point of switching from normal to misbehaved and vice versa. It is always at different values.

I checked that with the context menu at the desktop. Also it affected the items in kickoff start menu, but in video it started behaving normal even while the desktop context menu is misbehaving.
Comment 8 Nate Graham 2022-03-31 18:52:13 UTC
I found a way to reproduce this 100%: when I plug in a 1080p screen to my laptop with an internal 4K screen and right-click on the desktop on my laptop, this happens.
Comment 9 Nate Graham 2022-03-31 18:52:21 UTC
*** Bug 451235 has been marked as a duplicate of this bug. ***
Comment 10 Nate Graham 2022-04-06 19:35:56 UTC
Ah, we already had Bug 432264 for this.

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