Bug 468131

Summary:	1px wide border at the sides of xwayland maximized windows
Product:	[Plasma] kwin	Reporter:	dofficialgman
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	5.27.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description dofficialgman 2023-04-03 22:07:03 UTC

SUMMARY
When using the wayland session with xwayland fullscreen windows, it can happen that there is one pixel at the bottom of the window where the desktop/hidden taskbar shows through. In addition, when spawning a xwayland program, it can happen that the title bar and window itself are separated by one pixel that shows desktop/below windows through. Even more occasionally, it can happen that the right side of a window has a 1 pixel border where the desktop can be seen through


STEPS TO REPRODUCE
1. Open a minimum of two application that uses xwayland
2. Fullscreen both applications
3. Minimize the applications
4. Restore the applictions by clicking on them in the taskbar or alt-tabbing to them

OBSERVED RESULT
Observe the 1 pixel border at the bottom of the screen (and/or right side of a window) that shows the taskbar through it.

EXPECTED RESULT
The window is fullscreen with no 1 pixel border.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Video that shows the 1 pixel border: https://www.mediafire.com/file/oznsz7s4ccenw3t/PXL_20230328_214452939.mp4/file

Comment 1 Nate Graham 2023-04-04 17:41:11 UTC

When you say "fullscreen" do you mean "maximized?" Because these are actually different states. Does it happen with both states, or only one?

What scale factors are you using?

Comment 2 dofficialgman 2023-04-06 01:28:17 UTC

I mean maximized. there is no issue with fullscreen.
the problem is only apparent on non-integer scaling factors (100%, 200%, etc work fine) with maximized windows.

for example, I use 150% scaling factor on a native 3840x2160 monitor where the issue is present.

Comment 3 Nate Graham 2023-04-06 15:23:21 UTC

Thanks.

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

Comment 4 dofficialgman 2023-04-06 16:02:50 UTC

My apologies for submitting a duplicate report. I did search for reports but could not find anything open. I must have been using the wrong keywords at the time.

Comment 5 Nate Graham 2023-04-06 16:06:36 UTC

Don't worry about it. :)