I have a dual monitor setup, where the primary display has a greater resolution (1920×1200) than the secondary display (1680×1050). Both displays have panels of the same height fixed to the bottom of the screen edge. When an application creates a new, vertically maximized window on the secondary display, its height is exactly as tall as the vertical resolution of the first display less the height of the panel. But of course this is too high for the entire window to display properly on the secondary display, so the bottom of the window ends up being partially covered by the panel and partially off the screen altogether. This problem occurs only with newly created windows. If I manually vertically maximize such an oversized window (or any other window), then it snaps to the correct height (i.e., the height of the secondary display less the height of the panel). This problem is similar (but not quite the same) as that reported in Bug 348043. In that bug, the problem occurs when manually maximizing a window, whereas in this one, it occurs only when a (vertically) maximized window first appears. STEPS TO REPRODUCE 1. Start with a dual-monitor setup where the primary display has a greater vertical resolution than the secondary display, and both screens have panels. 2. Launch an application on the second display whose window is vertically maximized by default (e.g., okular) OBSERVED RESULT 3. The application window is too high (i.e., vertically maximized as if it were intended for placement on the primary display) EXPECTED RESULT 3. The application window should fit the height of the secondary display less the height of its panel SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0
I should add that this is on openSUSE Tumbleweed. In case it's needed, here is the output of xrandr -q: Screen 0: minimum 320 x 200, current 3600 x 1200, maximum 8192 x 8192 HDMI-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 546mm x 352mm 1920x1200 59.95*+ 1920x1080 60.00 1600x1200 60.00 1680x1050 59.88 1280x1024 60.02 1440x900 59.90 1280x960 60.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-1 connected 1680x1050+1920+0 (normal left inverted right x axis y axis) 474mm x 296mm 1680x1050 59.88*+ 1280x1024 75.02 60.02 1280x960 60.00 1152x864 75.00 1024x768 75.03 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 640x480 75.00 72.81 66.67 59.94 720x400 70.08
This bug was reported against an outdated version of KWin. We have made many changes since the. If the issue persists in newer versions can you reopen the bug report updating the version number.
Still reproducible with 5.27.6.
*** This bug has been marked as a duplicate of bug 461142 ***
(In reply to Nate Graham from comment #4) > *** This bug has been marked as a duplicate of bug 461142 *** Are you sure about this, Nate? That bug, and its other duplicates, all report that manually maximizing a window results in an incorrect window size. With my bug, manually maximizing a window works fine. It's only the window manager's initial placement of new windows that's broken. (In fact, the workaround to my bug is to manually maximize the window.)
Ah ok.
Still reproducible for me with KWin 6.0.3.1 when using X11. The problem is not reproducible when using Wayland (though I can't use Wayland for day-to-day work due to its various other bugs and missing features).