Version: unspecified (using KDE 4.7.0) OS: Linux I enable secodn graphics port with TV on it to switch from my tft 1280x1024 to enhanced resolution : tft + tv = 3200x1080. This all works fine. When I disable the tv posrt and use tft only again , maximized windows leave a 10 % bottom margin where windows refuse to cover in amximized state. I have to relog to fix it. xrandr: xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1280 x 1024, current 1280 x 1024, maximum 3200 x 1080 default connected 1280x1024+0+0 0mm x 0mm 1280x1024 50.0* 3200x1080 51.0 52.0 50.0 Reproducible: Always Steps to Reproduce: switch from 1280x1024 to 3200x1080 with "xrandr -s 1" and back with "xrandr -s 0" Actual Results: wrong maximum screen size for windows , desktop itself is rendered correctly Expected Results: correct maximum screen size for windows
This is somehow weird - why should the maximum area *shrink* below the minor height? (i'd understand if it staid at 1080) a) 10% of 1024px are 102px - really that much? How many pixels precisely? (use eg. kruler) b) do you have a panel at the bottom? b1) what if you restart just plasma "kquitapp plasma-desktop; sleep 1; plasma-desktop"? c) if b1) doesn't work, does actually "kwin --replace&"?
(In reply to comment #1) > This is somehow weird - why should the maximum area *shrink* below the minor > height? (i'd understand if it staid at 1080) > > a) 10% of 1024px are 102px - really that much? How many pixels precisely? (use > eg. kruler) > b) do you have a panel at the bottom? > b1) what if you restart just plasma "kquitapp plasma-desktop; sleep 1; > plasma-desktop"? > > c) if b1) doesn't work, does actually "kwin --replace&"? b)1 solves the margin error, video of toggle / untoggle second monitor and plasma error : http://tuxfusion.de/out.ogv , (bit long sry)
ok, please try "xprop | grep -i strut" on the bottom panel (after the failed area update. you'll get a cross pointer to click the window in question.)
(In reply to comment #3) > ok, please try "xprop | grep -i strut" on the bottom panel (after the failed > area update. you'll get a cross pointer to click the window in question.) xprop | grep -i strut _NET_WM_STRUT(CARDINAL) = 0, 0, 0, 83 _NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 83, 0, 0, 0, 0, 0, 0, 0, 1279 _KDE_NET_WM_FRAME_STRUT(CARDINAL) = 0, 0, 0, 0
(In reply to comment #4) > (In reply to comment #3) > > ok, please try "xprop | grep -i strut" on the bottom panel (after the failed > > area update. you'll get a cross pointer to click the window in question.) > > > xprop | grep -i strut > _NET_WM_STRUT(CARDINAL) = 0, 0, 0, 83 > _NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 83, 0, 0, 0, 0, 0, 0, 0, 1279 > _KDE_NET_WM_FRAME_STRUT(CARDINAL) = 0, 0, 0, 0 This is from a clean ~/.config/kde4 btw. The panel is created by KDE "standard" function with alteration except starters.
w/o counting in your video i'm fairly sure the area kept free in the bottom is precisely 83px high?! ;-) -> plasma bug, doesn't or does wrongly update the panel struts on screen updates.
(In reply to comment #6) > w/o counting in your video i'm fairly sure the area kept free in the bottom is > precisely 83px high?! ;-) > > -> plasma bug, doesn't or does wrongly update the panel struts on screen > updates. It doesn't accour in 4.7.1 for me anymore ! Fixed with many other little annyoing bugs. Love you guys!
According to the last reports on the likely dupe #190371 this bug is still open. The reporter was also kind enough to provide a patch. -> reopeninig, please have a look at the patch and fix code or bug resolution
*** Bug 190371 has been marked as a duplicate of this bug. ***
Created attachment 71508 [details] patch from bug 190371 Adding patch from bug 190371. Was this ever applied?
Setting status correctly. Please provide a version if this bug is still valid.
*** Bug 286013 has been marked as a duplicate of this bug. ***
Hello! Plasma 4 was replaced by Plasma 5 four years ago by the KDE community. In that time we have made great strides in stability and functionality. We are closing all Plasma 4 bugs as most of them are no longer applicable to the new frameworks Plasma 5 is built upon. If you could, please re-test with the latest version of Plasma 5, and submit a new bug to "plasmashell" if you continue to have an issue. Thank you!