Bug 474229 - Broken context menus on desktop and panel when using fractional scaling
Summary: Broken context menus on desktop and panel when using fractional scaling
Status: RESOLVED DUPLICATE of bug 432264
Alias: None
Product: kwin
Classification: Plasma
Component: multi-screen (show other bugs)
Version: 5.27.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-06 15:42 UTC by indx
Modified: 2023-09-06 16:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
l0rmin: Wayland+
l0rmin: X11-
l0rmin: Mesa+

Attachments
Broken context menu (35.17 KB, image/png)
2023-09-06 15:42 UTC, indx 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description indx 2023-09-06 15:42:24 UTC 
Created attachment 161447 [details]
Broken context menu

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Connect a second monitor to your laptop
2. Log in with a wayland session
3. Set fractional scaling of a built-in monitor to 150%
4. Log out and log in again.
5. Try to open a context menu on desktop and move cursor to a dropdown section (Create new, icons, add panel)
6. Menu will be transparent except that dropdown menu

OBSERVED RESULT
Context menu is transparent. Mostly this bug appears on desktop context menus and power menu in app menu. Rarely also affects panel's context menu

EXPECTED RESULT
Context menu is looking normal and not transparent.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Leap 15.5
(available in About System)
KDE Plasma Version: 5.7.24
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
This bug can be reproduced in this distros: openSUSE Leap, Tumbleweed, Kubuntu, Alt Linux.
Comment 1 Nicolas Fella 2023-09-06 16:02:05 UTC 

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