https://bugs.kde.org/show_bug.cgi?id=436648
--- Comment #2 from arne anka <kde-b...@ginguppin.de> --- Another workaround, so far apparently working. Did not yet restart, and since for some inexplicable reason Plasma thinks it a greate idea to regenerate configs on every reboot, I still expect trouble (feels like old Windows 95 and its registry ...) File .config/plasmashellrc has a section [ScreenConnectors] 0=eDP-1 1=HDMI-1 2=DP-2-2 and in .config/plasma-org.kde.plasma.desktop-appletsrc there's in most sections a key lastScreen=<value> where value may be 0, 1, 2, or even -1 where apparently those w/ value=1 refers to the screen setup I want to keep (when connected via HDMI), while value=2 refers to the "setup" plasma creates for the "new" monitor (when connected via DP). value=0 being the internal screen, and -1 .. no idea $ sed -i 's/lastScreen=2/lastScreen=3/g' .config/plasma-org.kde.plasma.desktop-appletsrc $ sed -i 's/lastScreen=1/lastScreen=2/g' .config/plasma-org.kde.plasma.desktop-appletsrc $ sed -i 's/lastScreen=3/lastScreen=1/g' .config/plasma-org.kde.plasma.desktop-appletsrc followed by $ kquitapp5 plasmashell && kstart5 plasmashell so far seems to have fixed things. I noticed that, despite the mapping in .config/plasmashellrc there's an inordinate number of places where instead of those numbers eDP-1 or HDMI-1 are used. Not sure what's the idea behind having two rivalling systems of enumerating screens, but it feels like it would break easily. Given the mapping, it shouldn't be to hard to present exactly that mapping in some user friendly sort and allow users to change it. -- You are receiving this mail because: You are watching all bug changes.
