https://bugs.kde.org/show_bug.cgi?id=366346
--- Comment #22 from Hai Zaar <haiz...@gmail.com> --- Great. I'll watch this bug for updates and test the fix properly. Many thanks for making Plasma better. On 9 August 2016 at 04:15, Sebastian Kügler via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=366346 > > Sebastian Kügler <se...@kde.org> changed: > > What |Removed |Added > ------------------------------------------------------------ > ---------------- > Version|5.7.2 |git > Keywords| |multiscreen > > --- Comment #21 from Sebastian Kügler <se...@kde.org> --- > Thanks a lot for the detailed information, it's very useful. > Interestingly, the > clue is in the log lines that are missing in your kscreen.log. :) > > The kscreen daemon (kded module) loads a list of outputs on startup and > starts > watching these for the Output::isConnectedChanged signal. > > What's happening when you plug in the dock after the session was started > (and > these outputs initialized) is that new output "connectors" appear -- these > are > initially disconnected. Then a configChanged signal arrives, and kscreen > saves > the config -- with disabled outputs. This means the configuration from this > point won't work anymore until you manually enable the output again. > > You can check which outputs are known at all, and which are connected > easily > with "kscreen-doctor -o" (kscreen-doctor is a small debugging/testing tool > I've > been working on lately.) > > I can reproduce this behaviour on my laptop when plugging in a Lenovo > Onelink+ > docking station. Completely new outputs appear when the docking station is > plugged in. > > The fix is pretty simple: we hook up Config::outputAdded as well, and make > apply a known configuration (this was exactly what was omitted in case the > docking station appears after startup). > > I've posted this fix for review on phabricator: > https://phabricator.kde.org/D2374 . > > Once this (or a variation of it) is merged, it would be cool if you could > give > it another try and see if the change fixes the problem for you. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
