hoffmannrobert added a comment.
My goal is to make the screen configurations work reliably with notebooks,
not to support a new use case. The use case is: work with a notebook docked and
undocked, with and without external screen(s), lid open or closed.
The configurations work fine, if no notebook with a lid that can be opened or
closed is involved.
But several users report, that they switch on their notebook (in docking
station) in the morning, lid is closed, log in, and the external screens are
swapped left and right again. Or only the empty background of the second screen
is shown on the external monitor while the primary screen is on the closed
integrated notebook screen.
So they configure it again as needed, while the lid is closed. But there is
already a lidOpened-configuration lurking around, waiting for the lid to be
opened and to destroy the configuration previously made.
Where does the wrong lidOpened-configuration come from? I guess it's created
automatically when the lid is open and a button on the OSD ("Extend to right"
or so) is clicked. After closing the lid, this configuration is copied to
"lidOpened".
The situation described in the test plan is just a quick way to show what can
go wrong and if that is fixed.
REPOSITORY
R104 KScreen
REVISION DETAIL
https://phabricator.kde.org/D21082
To: hoffmannrobert, #plasma, romangg
Cc: ngraham, romangg, plasma-devel, jraleigh, GB_2, ragreen, Pitel, ZrenBot,
lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart
