https://bugs.kde.org/show_bug.cgi?id=360926
Bug ID: 360926
Summary: Waking up notebook after undocking from a
multi-monitor setup creates an impossible kscreen
configuration
Product: KScreen
Version: 5.5.5
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: common
Assignee: se...@kde.org
Reporter: art...@gmail.com
I have a 3-monitor setup (2 external monitors through a dock, one of them set
as primary display + laptop's own display). After suspending to RAM in such a
set up and waking up with no dock attached I am faced with a black screen and
the mouse confined to moving along the vertical axis at x=0.
I had a hunch that this is about kscreen, took a backup of
~/.local/share/kscreen and wiped it. Killed X11. Logged in. Same thing -- black
screen and the mouse confined to moving along the vertical axis at x=0.
I checked the new kscreen config and it was exactly the same as the
laptop-monitor-only 1-monitor config kscreen created after waking up (see
attachment). Of interest is that it is exactly the same as the laptop monitor
part of the 3-screen multi-monitor config I suspended with and it has the
following config:
{
"enabled": true,
...
"pos": {
"x": 3840,
"y": 0
},
"primary": false
}
That doesn't look like a very healthy config for a 1-monitor set-up.
So, I wiped ~/.config, ~/.local/share, rebooted and started with a brand new
Plasma config, where kscreen actually creates a usable config with the
following:
{
"enabled": true,
...
"pos": {
"x": 0,
"y": 0
},
"primary": true
}
Reproducible: Sometimes
NB. Somewhat similar to https://bugs.kde.org/show_bug.cgi?id=359542 , but the
screen does turn on.
--
You are receiving this mail because:
You are watching all bug changes.
