KWin: fullscreen not fullscreening (botton part stays "empty)

Hi! I’m using the following system:

Operating System: Arch Linux 
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 7 9800X3D 8-Core Processor
Memory: 60,5 GiB of RAM
Graphics Processor 1: NVIDIA GeForce RTX 4090
Graphics Processor 2: AMD Radeon Graphics
Manufacturer: ASUS

It has two monitors attached, a MSI MAG275Q (vertical) and an Alienware AW3423DWF). See screenshots for settings:
MSI


Alienware

My issue is that on the MSI monitor (left, vertical) windows in fullscreen do not extend all the way down. There is always a part where the background stays visible. That part is always the same size. I can manually grab windows and extend them all the way down, but they do not “stick” and instead just go back up.

Is there any way for me to solve this? Thank you!

Hi! Just to check, are you referring to a literal fullscreen mode where an application appears on top of the panel and everything else, or to maximizing the window? Could you perhaps grab a screenshot of a time when this is occurring to share here?

A few questions come to mind to just try narrowing down when this is occurring:

  • Does this occur for all different types of applications - native Wayland and XWayland, GTK and Qt, etc.?
  • Is the fullscreen/maximized window height on the left monitor equal to the height of the right monitor?
  • Does this occur with the left monitor oriented in landscape?
  • Does this occur with only the left monitor connected, in its portrait orientation?
  • Does this occur with display scaling set to 100%?

If it is maximized windows (not fullscreen) and the empty part is a strip above the panel: I had that after updating today but a reboot seems to have fixed it

Hi @johnandmegh thanks for taking the time. Please find the answers to your questions below:

It happens only with maximized the windows, regardless of me maximizing them manually (where I can also pull them all the way down but they will snap back) or via the auto maximize. In “real” full screen mode, the whole screen is covered. Sorry I should have phrased that differently, I will edit the topic. (EDIT: unfortunately I can’t edit my original post anymore) I’m never using actual full screen since I usually have a few windows open that combined cover the entire screen (sort of like a tiling window manager).

Here is a screenshot for you (maximized window, not full screen:

This happens for all different types of applications.

I can’t say exactly but the maximized windows end at about the bottom of the height of the right monitor, yes.

This only occurs in portrait mode, landscape maximizes fine.

This only occurs with only the left monitor connected in portrait orientation.

This does also occur with display scaling set to 100%, arguably even worse as the “gap”/unusable space then covers almost 50% of the screen.

Hi @rrpeak this has been going on for quite a while (even before the recent Plasma update) so I rebooted a few times in between with no luck.

Thanks for detailing things out like that! And just in case - does this issue continue if you create a new user account on your system, with all default themes and configurations and everything (other than monitor rotation!)?

If it does, then I’d think this is worthwhile to file in the KDE Bugtracking System - the Community Wiki guide to reporting issues is located here: Get Involved/Issue Reporting - KDE Community Wiki

Thanks for pointing that out! I created a new user and the issue is not present there, so it must me something I did wrong in some configuration.

1 Like

Glad there’s progress on a solution there!

For what it’s worth…if you’re still looking to potentially figure out the specific setting from your existing user that’s related to the issue happening, you could:

  • Change a specific display-related setting on your new profile to match your existing one
  • Logout and login
  • Check if the issue reproduces
  • Repeat the steps above until you find the culprit

…if you’re up for a potentially longer period of troubleshooting :slight_smile: