https://bugs.kde.org/show_bug.cgi?id=480171
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #46 from [email protected] --- Additional data point on Plasma 6.6.6 / KWin 6.6.6, Wayland, Mesa 26.1.5. Diagnosed and drafted by Claude. Output DP-3: 3840x2160, scale 170% (204/120). Exact logical size is 2258.824 x 1270.588; KWin's maximize area for this output is the full 1270.588 logical px = 2160 device px. A maximized native-Wayland window like Dolphin or kitty ends up with frameGeometry height 1270 logical = 2159 device px, i.e. device row 2159 is never painted and keeps showing whatever is next in the stacking order. The reason I noticed this is that Firefox in the same circumstances picks 1271.176 logical (= 2161 device px) and overshoots instead, so it shows no gap at all. The artifact is therefore dependent on how each client rounds the configure size, which is why it is visible with kitty and Dolphin but not Firefox on an identical screen and scale. Workaround: pick a scale where resolution/scale is an exact integer on both axes, to within 1/120. A scale factor ~5/3 gives 2304x1296 and 1536x960 respectively, and both artifacts disappear. Note that a scale must be specified precisely enough to land on the intended 1/120 step -- entering 1.67 here resolved to 1.675 (201/120), which does not help; 1.66667 resolves to 200/120, which fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
