Bug 462906

Summary: Gap at the bottom of the screen when some applications are maximized - while using wayland and application menu bar.
Product: [Plasma] kwin Reporter: castleup
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version: 5.26.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: screenshot

Description castleup 2022-12-11 14:04:08 UTC
SUMMARY
***
This issue simply revolves around a gap that appears bellow most applications when they're maximized within a wayland session that only has an application menu bar.

Apps I've found prone to this issue are firefox, emacs, steam, yuzu emulator, all wine apps, brave, chromium, discord and
probably others I have not tested.

Apps that are inmune to this issue that I've found are: dolphin, KDE system settings, alacritty, spotify and keepassXC
***


STEPS TO REPRODUCE
1. Enter a wayland session
2. Remove the bottom panel and add an application menu bar at the top.
3. Open firefox, or any of the aforementioned apps and maximize them.

EXPECTED RESULT

A gap appears at the bottom of the screen.


SOFTWARE/OS VERSIONS
Linux: Arch Linux, linux-zen 6.0.9
KDE Plasma Version: KDE 5.26.3

Note: When I drag the app to the left or right, giving it a half of the screen; there is no gap at the bottom, and I can stretch through the other half of the screen to make it look properly maximized. Thus the issue is only with the maximize functionality, not kwin or the wayland session.
Comment 1 castleup 2022-12-11 14:07:29 UTC
Created attachment 154497 [details]
screenshot
Comment 2 Nate Graham 2023-01-03 22:19:29 UTC
Are you by any chance using a scale factor other than 100%, 200%, or 300%?
Comment 3 castleup 2023-01-20 19:19:22 UTC
(In reply to Nate Graham from comment #2)
> Are you by any chance using a scale factor other than 100%, 200%, or 300%?

Sorry for the late response. No, using 200%
Comment 4 Nate Graham 2023-01-20 21:53:48 UTC
Are you using Firefox in XWayland mode or Native Wayland mode? You can find this out by visiting "about:support" and going to the "Window Protocol" table row.

If you're using Firefox in XWayland mode and it goes away when using native Wayland mode, then this is Bug 459373.
Comment 5 castleup 2023-01-20 22:16:01 UTC
(In reply to Nate Graham from comment #4)
> Are you using Firefox in XWayland mode or Native Wayland mode? You can find
> this out by visiting "about:support" and going to the "Window Protocol"
> table row.
> 
> If you're using Firefox in XWayland mode and it goes away when using native
> Wayland mode, then this is Bug 459373.

I was. The issue was resolved once I started it in native Wayland. 
Thank you.
Comment 6 Nate Graham 2023-01-20 22:18:31 UTC
Cool, looks like it's Bug 459373.

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