https://bugs.kde.org/show_bug.cgi?id=475605
--- Comment #32 from Sandro Cavazzoni <san...@skanetwork.com> --- (In reply to Nate Graham from comment #31) >- Does it happen when the system locks the screen? I think only when put the display to sleep, but i'm not 100% sure >- Does it happen when the system puts the display to sleep? Yes >- Does it happen when the system suspends? No, suspend is disabled on my system. >- Are there more than one screen? Yes, I have 2 4K monitor >- Are there more than one GPU? I have an nvidia 3090 card, but there is also a Radeon 580X as secondary card, but it's under vfio to be used inside VMs, so i don't think it's the problem. >- Is it a PRIME system with muxing? If so, which GPU was driving the display? No, it isn't a PRIME system. >- Is the cursor visible? Yes >- Are there any GUI elements visible? No >- Is the broken lock screen function (e.g. blindly typing your password and >hitting Enter unlocks)? I tried without success, but because is everything black i can't say for sure. >- Is there a method that brings you back to a working desktop (e.g. killing >kscreenlocker_greet). Not sure, I just reboot the PC when it happen. >- Is the desktop session using X11 or Wayland? The desktop is wayland, but SDDM should be X11 I'm not having this problem since the last 3/4 days (I had it also with RC1 at begin). But because it doesn't happen every time, i'm not sure if something is changed or was just a few lucky days. The only things I changed are distro updates (arch linux) and changed the render loop from threaded to to basic inside "kcmshell6 kcm_qtquicksettings" (to work around a different bug) -- You are receiving this mail because: You are watching all bug changes.
