My laptop apparently turns off its in-built screen if I close the lid, and each time I close the lid, effectively have a laptop without any screens at all attached, and then open the lid back up again the panel at the bottom will cover the bottom parts of a maximized window. When I open the screen lid again it seems like the windows are shown slightly before the panel, and the panel will overlap slighly in the bottom parts of the window. At the same time the runner will also show itself offscreen. Reproducible: Always Steps to Reproduce: In my configuration the I have a laptop that automatically shuts the power to the in-built screen (or so it appears, I have disabled all power management) 1. Close lid 2. Open lid 3. Observe that the panel will overlap the bottom parts of the window and that the runner is off screen. Actual Results: Maximized windows, even new ones, will be covered by the panel. The runner is shown off screen. Expected Results: Maximized windows not expanding below the panel Runner shown on screen
Can I have: - a screenshot - output of xrandr -q - output of "xprop" and clicking on the panel - how do you know krunner is being shown if it's off the screen? then reset the status field to unconfirmed.
Created attachment 97029 [details] konsole showing correctly (notice the tab at the bottom) Screenshot of konsole showing correctly
Created attachment 97030 [details] konsole showing incorrectly (notice the tab at the bottom is below the panel)
Created attachment 97031 [details] xrandr -q when everything behaves correctly
Created attachment 97032 [details] xrandr -q when window is behind panel
Created attachment 97033 [details] xprop of panel when it behaves correctly
Created attachment 97034 [details] xprop of panel when it behaves incorrectly
See attachements for screenshots and outputs of the commands. I can not for certain say that the runner is running off screen but it is getting focus and working. I can "show" it with keyboard shortcut, type for instance dolphin and hit enter and dolphin will start. I also see that input focus moves from the current window to something invisible.
Copying and pasting the relevant bit: Good _NET_WM_STRUT(CARDINAL) = 0, 0, 0, 27 _NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 27, 0, 0, 0, 0, 0, 0, 0, 1365 Bad: _NET_WM_STRUT(CARDINAL) = 0, 0, 0, 4294966555 _NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 4294966555, 0, 0, 0, 0, 0, 0, 0, 1365 Docs: _NET_WM_STRUT, left, right, top, bottom, CARDINAL[4]/32 _NET_WM_STRUT_PARTIAL, left, right, top, bottom, left_start_y, left_end_y, right_start_y, right_end_y, top_start_x, top_end_x, bottom_start_x, bottom_end_x,CARDINAL[12]/32
I can confirm this behaviour on a Thinkpad T440p with an external Monitor connected (1920x1080, VGA). The panel sometimes overlaps fullscreen windows. OS: openSUSE Leap 42.1 Kernel: 4.3.0 X.org: 1.17.2 Mesa: 11.0.8 with Intel Haswell
Still present in plasma-workspace 5.5.4 (Fedora 23).
Is it still the case?
Still 100% reproducible on Fedora 27 with Plasma 5.12.2. Easier way to repro: 1) Open any window and maximize to full-screen (I tried Thunderbird and Terminator) 2) Plug external monitor 3) Wait for kscreen to adjust the display 4) Note how the bottom of the window disappears behind the panel 5) Unplug monitor 6) Window shrinks again
Its continues to be 100% reproducible with plasma 5.18.4.1. Moreover, it is possible to "correct" the problem if you switch the primary screen back and for.
Now that I think about it, I think I can nail a bit more when it happens. It only happens when the attached screen is configured to NOT be the primary screen and IS bigger that the primary one. In my case, when you plug the FullHD TV to my laptop. Nevertheless, the bug does not shows when I plug my work screen (that is configures as a primary) or when I plug a beamer (that are typlically smaller in resolution than the laptop screen).
Hello, this bug is also reproducible in Arch Linux (kernel 5.8.6-arch1-1) on Plasma version 5.19.5
This is fixed with various changes in Plasma 6.2, at least on Wayland. On X11 it's not easily fixable and a fix should not be expected anytime soon, if ever.