+++ This bug was initially created as a clone of Bug #477738 +++ SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE Created complete new userprofile, so no legacy setting from plasma 5 should affect here 1. screen locks or Meta + L 2. screen goes black, moving mouse shows cursor, hovering over textbox changes cursor, i can enter password, but screen is all black 3. after hitting enter i get back to desktop with no graphical glitches there OBSERVED RESULT black screen with cursor EXPECTED RESULT show screenlocker ADDITIONAL INFORMATION SUMMARY After I suspend to RAM and resume, my KDE setup (Wayland, Nvidia 1060, using the nvidia driver, on Arch Linux) leaves me with a black screen and a working cursor that changes when I hover over a textbox (but I can't see the textbox) on the lockscreen. I see this in the system journal right after I resume from RAM: ``` kwin_wayland[1399]: kwin_wayland_drm: Atomic commit failed! Permission denied kwin_wayland[1399]: kwin_wayland_drm: Presentation failed! Permission denied kwin_wayland[1399]: kwin_wayland_drm: Atomic commit failed! Permission denied kwin_wayland[1399]: kwin_wayland_drm: Presentation failed! Permission denied kwin_wayland[1399]: kwin_wayland_drm: Atomic modeset commit failed! Permission denied kwin_wayland[1399]: kwin_wayland_drm: Setting dpms mode failed! kwin_wayland[1399]: kwin_wayland_drm: Atomic modeset commit failed! Permission denied kwin_wayland[1399]: kwin_wayland_drm: Setting dpms mode failed! kwin_wayland[1399]: kwin_core: Could not find window with uuid "{38667f04-f9ad-4cc3-958b-f8d804def467}" kwin_wayland[1399]: kwin_core: Could not find window with uuid "{38667f04-f9ad-4cc3-958b-f8d804def467}" kwin_wayland[1399]: kwin_core: Could not find window with uuid "{38667f04-f9ad-4cc3-958b-f8d804def467}" kwin_wayland[1399]: kwin_core: Could not find window with uuid "{38667f04-f9ad-4cc3-958b-f8d804def467}" ``` and then lots of these lines, filling up my journal until I reboot ``` kwin_core: Applying KScreen config failed! ``` I can't seem to find a way to recover from this other than to reboot, which is, of course, extremely disruptive. STEPS TO REPRODUCE 1. Put the computer to sleep (i.e. suspend to RAM) 2. Wake it back up OBSERVED RESULT Black screen -- no lock screen displayed, but I can still move my mouse cursor around and see it respond to the presence of a text box EXPECTED RESULT I should be able to see my lock screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, latest packages (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION My hardware (Nvidia 1060, nvidia proprietary driver) is probably relevant? Not quite sure how to attach bugtraces, but I can if needed. Thank you!
Thanks for your bug report, this might be the same or related to: https://bugs.kde.org/show_bug.cgi?id=481308 Although I am not sure because there a conflicting information in this bug report. You mention X11 in the title and the component but the keyword is mentioning wayland as well as your journald. Additionally this is reported against 6.0.1 but in your comment you mention KDE Plasma Version: 5.27.9 If you can still reproduce this can you post the output of kinfo ?
(In reply to duha.bugs from comment #1) > Thanks for your bug report, this might be the same or related to: > https://bugs.kde.org/show_bug.cgi?id=481308 > > Although I am not sure because there a conflicting information in this bug > report. You mention X11 in the title and the component but the keyword is > mentioning wayland as well as your journald. > > Additionally this is reported against 6.0.1 but in your comment you mention > KDE Plasma Version: 5.27.9 > > If you can still reproduce this can you post the output of kinfo ? Sorry, looks like when i cloned the bug from Bug #477738 this got copied too. Correct is X11, Plasma 6.0.1 All below ADDITIONAL INFORMATION SUMMARY After I suspend to RAM and resume, my KDE setup (Wayland, Nvidia 1060, using the nvidia driver, on Arch Linux) leaves me with a black screen and a working cursor that changes when I hover over a textbox (but I can't see the textbox) on the lockscreen. is not for this bug
this is duplicate of https://bugs.kde.org/show_bug.cgi?id=481308 so can be closed
*** This bug has been marked as a duplicate of bug 481308 ***
Do you have file /etc/modprobe.d/nvidia-power-management.conf on your system? Containing such text. «# The destination should not be using tmpfs, so we prefer # /var/tmp instead of /tmp options nvidia NVreg_PreserveVideoMemoryAllocations=1 NVreg_TemporaryFilePath=/var/tmp» Here it is written about this file. https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks On tab «10 Preserve video memory after suspend» «The video memory contents are saved by default to /tmp, which is a tmpfs. NVIDIA recommends using an other filesystem to achieve the best performance. This is also required if the size is not sufficient for the amount of memory: point to a different location with the NVreg_TemporaryFilePath kernel module parameter, (e.g. NVreg_TemporaryFilePath=/var/tmp).»
(In reply to Victor Ryzhykh from comment #5) > Do you have file /etc/modprobe.d/nvidia-power-management.conf on your system? > Containing such text. > > «# The destination should not be using tmpfs, so we prefer > # /var/tmp instead of /tmp > options nvidia NVreg_PreserveVideoMemoryAllocations=1 > NVreg_TemporaryFilePath=/var/tmp» > > > Here it is written about this file. > https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks > On tab «10 Preserve video memory after suspend» > > «The video memory contents are saved by default to /tmp, which is a tmpfs. > NVIDIA recommends using an other filesystem to achieve the best performance. > This is also required if the size is not sufficient for the amount of > memory: point to a different location with the NVreg_TemporaryFilePath > kernel module parameter, (e.g. NVreg_TemporaryFilePath=/var/tmp).» not applicable here, as no nvidia card present in system, only intel gpu
(In reply to duha.bugs from comment #1) > not applicable here, as no nvidia card present in system, only intel gpu You write above several times. (In reply to duha.bugs from comment #1) > After I suspend to RAM and resume, my KDE setup (Wayland, Nvidia 1060, using > the nvidia driver, on Arch Linux) leaves me with a black screen and a > working cursor that changes when I hover over a textbox (but I can't see the > textbox) on the lockscreen.