|
Description
dump
2015-12-28 18:34:11 UTC
First link is done via kwin/plasma screenshot utility: http://i.imgur.com/nmWEd92.png Second via scrot/xorg: http://i.imgur.com/oSaQHiD.png Which also hints at the issue (xorg desktop size is correct, whatever is used by the plasma framework to communicate it to the screenshot tool is incorrect) please post "xrandr -q" output befopre and after the problematic change as well as "xprop" on all involved panels (cursor turns into "+", then click the panel) - you may strip the icon informations (ASCII art) from xprop. Oh, and the output of "qdbus org.kde.KWin /KWin supportInformation" before and after. Created attachment 96338 [details]
xrandr -q output (problem is occuring)
Created attachment 96339 [details]
xprop of bottom panel (this is my only panel) when problem is occuring
Created attachment 96340 [details]
xprop of firefox maximized when problem is occuring (just in case its useful)
Created attachment 96341 [details]
qdbus kwin output (problem is occuring)
Created attachment 96342 [details]
xprop of bottom panel when problem is fixed (1920x1080 for all screens)
Created attachment 96343 [details]
xrandr -q outpu t when problem is fixed (1920x1080 for all screens)
Created attachment 96344 [details]
qdbus kwin output when problem is fixed (1920x1080 for all screens)
One of your screens is WUXGA (x1200), the other one FullHD (x1080) => The cannot be "unified", ever. What happens is that the plasma panel "feels" like it's on the smaller screen and adds a 172px strut (52 for the panel and 120 for the offset to the root window, which is the bounding rect of all screens, ie 1920x1200) There's no bug in KWin here. Your problems are: a) the screens have different geometries b) they're not bottom aligned c) the panel alignes to the smaller screen (what makes sense! otherwise it would be visible on only the bigger screen) The HDMI seems to support FullHD as well, so it might be desired and reasonable for kscreen to actually unify them (omitting the preferred resolution of the bigger screen) when restoring(?) the screen config. Note: i believe that i know what causes the issue. At some point in time it was only possible to unify outputs if they had the same resolution (1920x1080) in my case. Then when scaling options came up, it was possible to unify outputs with different resolution (1920x1200 + 1920x1080 in my case, where items would scale up to match). The scaling only works right when the screen would be connected at plasma/kwin startup it seems like. Right now, unless i wipe my configuration, since ive manually set both screens to 1920x1080 it seems to work ok so far (after a few disconect/reconnect). I dont seem to be able to reset that via the display configuration panel to the original/buggy setup unless i wipe all config/new profile (but i may be wrong, ill try playing with the scaling settings a bit more) The scaled version is much nicer though tho since all items are crisp on both screens (1920x1080 on a 1920x1200 screen is a different aspect ratio so looks a little blurred) Since I reinstalled I dont run into this issue so I was going to close the bug. But it turns out that I do run in a similar but slightly different situation (which is maybe is the same bug, in fact): Right now my 2 screens show as 1920x1080 in the display panel (and look to be at that resolution), and I did unify them. However if i close/open the display panel they show as non-unified (i can click on unify again and nothing happens). This time also, instead of having a space at the bottom of the screen, some of the window is not displayed when maximized (goes under the bottom panel that i have, on both screens). Note: I do not know if it's a kwin problem or something else for sure (or my fault somehow). Will attach details. Also, thanks for taking the time to look at this! Created attachment 96608 [details]
Quick video recording of first screen (eDP1) showing the unify "issue" and the maximize issue
Created attachment 96609 [details]
xrandr output (new)
Created attachment 96610 [details]
xprop output (new)
Created attachment 96611 [details]
qdbus output (new)
Note: now running 5.5.3 Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |
