Bug 469187 - Visual artefacts in a lot of KDE default menus when using fractional scaling on wayland
Summary: Visual artefacts in a lot of KDE default menus when using fractional scaling ...
Status: RESOLVED DUPLICATE of bug 465158
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 5.27.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-30 10:35 UTC by sebi.loew
Modified: 2023-05-02 16:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Happens in a lot of default menus, see description above (2.82 MB, image/png)
2023-04-30 10:35 UTC, sebi.loew
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sebi.loew 2023-04-30 10:35:00 UTC
Created attachment 158561 [details]
Happens in a lot of default menus, see description above

SUMMARY
I have a WQHD monitor and use 150% scaling. There are a lot of visual artefacts in KDE context-menus or the apps itself, if I move my mouse. It doesn't happen with 100% scaling. 
It's hard to catch on a picture, because it happens while moving the mouse and it isn't visable when using Spectacle, but you can see it on the attached foto.
I'm on fresh installed Fedora KDE, but it was the same with Kubuntu with KDE 5.25. The scaling factor doesn't change anything, it's the same with other factors. Changing any display- or compositor settings also doesn't help.
It doesn't happen with other apps like firefox.

I use KDE, because I really like it and it does by far the best job with scaling (which is essential for me to read anything), so it would be much appreciated if this bug wasn't there.


STEPS TO REPRODUCE
1. Use fractional scaling on a WQHD monitor.


SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.4
Wayland Season


ADDITIONAL INFORMATION
I'm using a AMD RX 6700 XT GPU.
Comment 1 Nate Graham 2023-05-02 16:37:22 UTC

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