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.
Created attachment 98052 [details] Original 3-monitor config
Created attachment 98053 [details] Broken 1-monitor config kscreen created after wake up
Created attachment 98054 [details] Correct 1-monitor config kscreen created after a full config wipe and reboot
I've recently experienced the same behavior on my Lenovo T-450s and a docking station with Kubuntu 16.04 LTS (Plasma 5.5).
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!