It looks like this has improved somewhat: It's no longer necessary to delete the contents of .local/share/kscreen at least.
The problem where the system does not appropriately act upon connection/disconnection of the monitor still shows itself in several very obvious ways though:
Scenario 1:
1. Connected to external (primary) 2560x1080 monitor, put laptop to sleep.
2. Disconnect monitor.
3. Wake laptop.
4. kscreenlocker_greet is unresponsive, and trying to draw a 2560x1080 unlock screen on the laptop's 1920x1080 screen.
5. The only way to get past this is to go to a terminal and kill the locker process (which will respawn with correct screen info). The correct screen setup will be used after you unlock the respawned locker.
Scenario 2:
1. With laptop not connected to monitor, sleep system.
2. Connect to external 2560x1080 monitor.
3. Wake laptop.
4. After unlocking screen, desktop resolution is still 1920x1080, filling only the left 3/4ths of the screen.
It looks like this has improved somewhat: It's no longer necessary to delete the contents of .local/ share/kscreen at least.
The problem where the system does not appropriately act upon connection/ disconnection of the monitor still shows itself in several very obvious ways though:
Scenario 1:
1. Connected to external (primary) 2560x1080 monitor, put laptop to sleep.
2. Disconnect monitor.
3. Wake laptop.
4. kscreenlocker_greet is unresponsive, and trying to draw a 2560x1080 unlock screen on the laptop's 1920x1080 screen.
5. The only way to get past this is to go to a terminal and kill the locker process (which will respawn with correct screen info). The correct screen setup will be used after you unlock the respawned locker.
Scenario 2:
1. With laptop not connected to monitor, sleep system.
2. Connect to external 2560x1080 monitor.
3. Wake laptop.
4. After unlocking screen, desktop resolution is still 1920x1080, filling only the left 3/4ths of the screen.