Regarding the version: I don't know exactly: I've installed it (yesterday 8 May 2013) using the Gentoo live ebuild (the only ebuild available), which normally builds from git head. The only identifying info I could find is that I have /usr/lib64/libkscreen.so.0.0.92 installed. I may be able to determine the exact commit with instructions. My setup: Laptop with dock, internal screen is 1366x786, external screen is 1080x1920 (so 90° rotated 1920x1080); only one of both is used at any time. When I unplug the external monitor, the internal one activates correctly. When I reconnext the external one, it is activated, but at resolution 1080x786 (I think) at the top of the display, so the bottom 1100-something pixels are black (well, on one occasion there was garbage there) and I can't go there with the mouse; the limited viewport works without problems. So I have (external 1080x1920) - disconnect -> (internal 1366x786) - reconnect -> (external 1080x786), whereas the last should be (external 1080x1920), of course. Reproducible: Always Steps to Reproduce: 1. disconnect external display 2. reconnect external display Actual Results: incorrect resolution on external display Expected Results: correct resolution on external display
Let's fix this. 1-Execute kdebugdialog 2-enable ëverything with "kded" and "ksrandr" 3-kquitapp kded4 4-kded4 (in a terminal) Paste here the output of that process. Thanks !
Created attachment 79880 [details] edited kded4 error log
(In reply to comment #1) > > 1-Execute kdebugdialog Ok. > 2-enable ëverything with "kded" and "ksrandr" Ok. > 3-kquitapp kded4 `kquitapp kded` instead > 4-kded4 (in a terminal) `kded4 2> kded-output.txt` instead Started with external actve/internal inactive; disconnected external (internal became active with correct resolution); reconnected external (became active with correct(!) resolution). The problem did not occur! (Close bug as 'problemmagicallydisappeared'? I'll reopen/comment again if the problem resurfaces and I can catch it with the procedure you've described.) > Paste here the output of that process. See attachment (edited out unrelated log lines)
Ok, closing as fixed per your comment. Please reopen and attach output of "kscreen-console bug" if this problem should appear again with latest version. Thanks