Bug 449827 - Wayland: Context menu invisible on external monitors
Summary: Wayland: Context menu invisible on external monitors
Status: RESOLVED DUPLICATE of bug 432264
Alias: None
Product: kwin
Classification: Plasma
Component: multi-screen (show other bugs)
Version: 5.24.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-09 08:54 UTC by Roman Fürst
Modified: 2022-02-09 09:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Screenshot with partially invisible context menu (226.16 KB, image/png)
2022-02-09 08:54 UTC, Roman Fürst 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Fürst 2022-02-09 08:54:58 UTC 
Created attachment 146481 [details]
Screenshot with partially invisible context menu

SUMMARY
The context menu becomes invisible in wayland sessions on external monitors. One has to hover each entry of the menu to see it again. Seperators keep invisible. See attached screenshot for an example.


STEPS TO REPRODUCE
1. Right click on desktop on an external monitor -> Context menu appears as expected
2. Hover mouse pointer over one of the entries -> All other entries disappear
3. Hover mouse pointer over one of the just disappeared entries -> Entry becomes visible again

OBSERVED RESULT
Context menu becomes invisible

EXPECTED RESULT
Context menu should always be visible

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.24.0
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Graphics Platform: Wayland

ADDITIONAL INFORMATION
This happens on external monitors (connected over USB-C) only. The context menu looks perfectly fine on the laptop internal screen.
Comment 1 Vlad Zahorodnii 2022-02-09 09:01:04 UTC 
That's a known Qt bug. It caused by using two monitors with different scale factors.
Comment 2 Vlad Zahorodnii 2022-02-09 09:01:25 UTC 
It's*
Comment 3 Vlad Zahorodnii 2022-02-09 09:02:06 UTC 

*** This bug has been marked as a duplicate of bug 432264 ***
Comment 4 Roman Fürst 2022-02-09 09:18:39 UTC 
Dang, didn't found that issue. Thanks for the super quick response!