SUMMARY STEPS TO REPRODUCE 1. use "systemctl restart sddm" 2. hibernate system (sleep option in menu) OBSERVED RESULT With systemctl restart sddm used one of the monitors doesnt turn off and stays at the last thing it was on, system is working normally, i can hear for example music played before restart, main monitor has white line on the top-left like in terminal, cannot switch to any tty EXPECTED RESULT system would work normally after restart SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch linux 6.6.7 zen (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Occurs on either xorg and wayland, on other installation i remeber i did something and it didnt occur, i think chmod -R 777 .local/share/kscreen/ worked it out(tried it now it doesnt fix the issue) journalctl error on kde: kwin_wayland_drm: Atomic commit failed! Invalid argument kwin_wayland_drm: Presentation failed! Invalid argument kwin_core: Applying KScreen config failed! (this one repeats a lot)
Why are you running `systemctl restart sddm`? When are you doing so? What's the circumstance that happens to make you want to do it?
(In reply to Nate Graham from comment #1) > Why are you running `systemctl restart sddm`? > > When are you doing so? What's the circumstance that happens to make you want > to do it? Once i needed to do it when installing something, It’s still having same issues when using sleep options, i Think its related to kde and drivers because on other DE it doesnt reproduce such errors even with same config
Issue was your system, swapped WM and everything works fine, thanks for helping with searching for the issue
When you say "swapped WM" do you mean you switched away from KWin, or Plasma, or something else?
(In reply to Nate Graham from comment #4) > When you say "swapped WM" do you mean you switched away from KWin, or > Plasma, or something else? I have gone for awesomewm and it doesnt have that bug so its kde issue
Ok, thanks. Since you're unable to reproduce the issue, and no developers could either, I'm afraid this isn't actionable. In the future, and in general, when you submit a bug report, it's important to preserve the buggy environment so you can answer questions, test proposed changes, etc. See https://community.kde.org/Get_Involved/Issue_Reporting#Issue_reporting_involves_responsibility