https://bugs.kde.org/show_bug.cgi?id=517499
--- Comment #24 from Branislav Klocok <[email protected]> --- This happened again today on KWin and Plasma 6.8.2, on the same machine as in comment 22. The recorder shows the same sequence as before. I undocked with the lid open at 08:40, leaving the internal display alone at priority 1, and docked again at 09:57. Both outputs came up at priority 1, and KWin wrote the tie into kwinoutputconfig.json. I understand 6.8.2 was tagged before !10264 was merged, so this is not a report against that change. I did read it, though, and have a question. As far as I can see, it rejects a saved priority below zero, above a million, or missing, and then regenerates the setup. The setup KWin saved here has both outputs at priority 1. Each value is valid on its own, so I would expect that setup to load unchanged. Is the duplicate case meant to be handled somewhere else, for example in !9829, or should I expect the tie to persist after !10264? The saved config from this morning is attached. -- You are receiving this mail because: You are watching all bug changes.
