https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #42 from Sebastian Kügler <se...@kde.org> --- Let me try to clear it up then. :) Currently, we don't change the resolution if the user hasn't configured this exact combination of screens previously. That means that if you log into a fresh session, we don't do anything on login wrt screen setup. We expect the system to be set up. With the current state, we now detect if the current resolution goes away, and we react to that by modesetting the new preferred resolution. So if you log in to a fresh vm, the login manager (or X startup) has to take care of that, to avoid unnecessary mode changes. The move from projector problem, I'm not sure I understand. We only save/restore a config for a given combination of outputs connected, the edid or model + serial of all connected outputs are hashed, and used as key to find the right config. We do not apply configs to unknown hardware. The initial setup for a given projector would be the same, as that is done using heuristics, and after once changed from the ui, the config is remembered only for that combo of outputs. I like the idea of making the preferred mode more prominent, or logical in the UI, I'll give that some more consideration. Currently working on bits and pieces for an improved KCM, so that kind of input is well-timed. :) -- You are receiving this mail because: You are watching all bug changes.
