Bug 454691 - On a 4K monitor, the context menus load incorrectly on Wayland
Summary: On a 4K monitor, the context menus load incorrectly on Wayland
Status: RESOLVED DUPLICATE of bug 432264
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.24.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-01 09:21 UTC by Marcos Gutiérrez Alonso
Modified: 2022-06-01 18:25 UTC (History)
1 user (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 Marcos Gutiérrez Alonso 2022-06-01 09:21:20 UTC
SUMMARY
In a 4K monitor, the resolution of the context menus is not correct. When I hover over an item, all other items "crash" (dissappear) and the one I hovered renders at the correct resolution.

It's hard to explain so here's a video demonstration: https://youtu.be/drwGeXqMgFA

This happens to EVERY right-click context menu on Wayland: in the plasma panel, in the desktop, in the application launcher... everywhere.

This does NOT happen on my secondary 1080p monitor.

STEPS TO REPRODUCE
1. Enable 4K resolution in wayland
2. Right-click anywhere to bring up a context menu
3. Hover over an element and watch the elements become invisible

OBSERVED RESULT
1080p resolution on context menus when they load.

EXPECTED RESULT
They appear with the appropriate resolution.

SOFTWARE/OS VERSIONS
OS: Arch Linux x86_64
Kernel: 5.18.1-zen1-1-zen
Resolution: 3840x2160
DE: Plasma 5.24.5
WM: kwin
Theme: [Plasma], Breeze [GTK2/3]
Icons: [Plasma], breeze-dark [GTK2/3]
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION
- I'm using the amd gpu drivers.
- This text rendering issue (without transparencies) happens in other places too, such as the "About this system" in the system settings.
Comment 1 Nate Graham 2022-06-01 18:25:02 UTC

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