Steps to reproduce: 1. Work as usual with external display connected via HDMI. 2. Hibernate laptop. 3. Disconnect HDMI cable. 4. Resume from hibernation. After that I get black screen, no mouse cursor. Can't get to tty unless I close the lid and resume from suspend, then CTRL+ALT+F[1-6] starts working. Temporary solution is to blindly login to desktop, launch terminal and xrandr to primary display using: xrandr --output HDMI1 --off --output LVDS1 --auto
Similar situation here, without an external display. After suspend/resume the laptop screen is black, no mouse cursor. CTRL+ALT+F[1-6] works but ALT+F7 does not recover the graphic display. The suggested workaround using xrandr works for me too. System: ASUS NV56 with Intel & Nvidia OS: Slackware64 current Kernel 4.9.7 Xorg: 1.19.1 mesa: 13.0.2 libxcb: 1.12 xf86-video-intel-git_20170103_028c946d Plasma: 5.8.5 Frameworks 5.30
I have solved my issue by reverting the following commit from kscreen: b4b504696b638691ad96c75560e6599c44bea88c It's probably not the right approach but it works for me :) and it might point the developer into the right direction. If I revert the following commit 367e55b7c172d54d068eb09f308e92368c294e9 from libkscreen as well the screen still comes back after resuming but then the .local/share/kscreen/kscree.log file is flooded with Current mode "" invalid, setting preferred mode "" messages.
Unfortunately it was a short-lived wonder. :( After a 24+ suspend to RAM the screen didn't recover and I had to zap X11. I did work, though, as reported in comment #2 but when suspending to RAM for short periods of time.
Almost similar situation - actually problem occurs both ways, but not always. Example: @home no external display attached, booted up, works. Suspend to RAM, next day @work plug to dock with 2 external displays, open lid and whole system freezes, only option is to do a hard shutdown. After booting up laptop + 2 displays works like a charm, no changes needed. Suspend to RAM. @home resume from RAM, mouse pointer is visible on far left, not moving. Blindly log in then xrandr --auto works. Lenovo T460s (but similar problem happened with HP Elitebook 8470p + dock + 1 external display). Plasma 5.8.5 Fedora 24 (4.9.9-100.fc24.x86_64)
I have worked around this issue by switching to the modesetting driver instead of Intel's driver.
SUSPEND was fine until 2017MAR04 after I installed updates (could be coincidence) 1- SUSPEND caused a reboot. Although it did not happen again. 2- SUSPEND went fine, but at wake up, computer started, but lost screen (all black) lost cursor, and system was not responding to keyboard. I had to reboot.
Is this bug still happening on newer Plasma versions?
Similar issue here, wake up from sleep(suspend) and external monitor connected via dock will not wake up. Laptop display is disabled at this point so no way of doing anything. Always have to unplug laptop from the dock to get laptop monitor to come up, then plug back in and external monitor starts working or I have to re-enable it in display settings. HP 840 G1 with HP docking station and ASUS monitor.
@7 Absolutely. `kscreen-doctor` (on text console) shows my `eDP1` is connected but disabled. Enabling it via `kscreen-doctor` gives no error message, but the screen stays black and the output of another `kscreen-doctor` call shows it still as disabled.
I have the same problem. Steps to reproduce: 1) I go to System Settings > Energy Saving > Screen energy saving = "1 minute". 2) I wait for a minute, the screen goes to sleep. 3) When I wake it up, I see a black screen + pointer. Sometimes I manage to restore it with Meta + P, going to a different screen and coming back. My system: Manjaro KDE - Plasma 5.18.4 + Frameworks 5.69.0 - Qt 5.14.2 - Kernel 5.5.18-1 Is there a solution or we just have to wait for this error to be fixed? Greetings! (Stay safe)
This just started happening for me in the past week or two on Arch Linux with the stock repo packages. Had been working fine up to that point. Randomly after a suspend-to-ram or monitor-suspend, the screen comes up entirely black with a themed mouse cursor able to be moved. I'm able to ctrl-alt-f2 into a terminal. I've tried poking around a bit to see what exactly is borked but the best I can come up with kwin_x11 has trashed itself in an unrecoverable and unlogged way. Trying to "DISPLAY=:0 kwin_x11 --replace" with or without the kquitapp5 / kstart5 voodoo results in a compositing unavailable error in the syslog. I'm not able to recover my session or any desktop environment once this occurs. Following prior discussion, I saw nothing of note in kscreen-doctor: it outputs the same 3 monitors enabled and connected before and after the black screen occurs. KDE Plasma Version 5.19.3 KDE Frameworks 5.72.0 Qt Version 5.15.0 Kernel Version 5.7.9-arch1-1 / 64-bit Running on Ryzen 1700x & Nvidia GTX 1080 with binary driver 450.57 (I tried rolling back to the previous driver, version 440, with no success). Please let me know if there is any logging or triage I can do to help uncover this mystery.
May or may not be of any consequence, but peeking at kwin_x11 with strace after the black screen occurs shows the process stuck at: restart_syscall(<... resuming interrupted read ...>
Having the same issue. Screen flickers after waking up from suspend or hibernate, when switching user I just get a black screen and can't do anything, when switching terminal I can successfully login. First screen connected with Displayport, second one with HDMI. GPU: AMD RX 5700XT with mesa drivers Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-58-generic OS Type: 64-bit Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 15,6 GiB