This seems to have started after I updated plasma.
When the screen goes to turn off it seems to just dim but then locks completely. I have to close the lid of my laptop so that it goes to sleep and then open it up again to have it force the log in screen to get my laptop to be accessible again. It only seems to be an issue though is the screen is first dimmed and then the screen shuts off. If I have the dim and shutoff both set to the same time I’ve got no issue.
Anyone else see this issue?
i have not tried to find out the exact reason, but in several occasions the locked plasma session seems to be frozen - no password field appears. It helps if I switch to virtual console and back to plasma session - then the password field appears and unlocking is possible. It started after Neon upgraded to 6.5.4 etc…
Yeah the issue I’m seeing is that not only is the screen locked but when I try and use the keyboard to switch screens nothing happens. The only solution I’ve found is to close the lid of my laptop which puts it into a sleep mode. Then I open it up and I can log back in.
You should have Atomic errors in your journal.
Turn off Adaptive Sync in video settings.
journalct -f is full of:
dets 16 19:16:49 TPCarbonX1 kwin_wayland[1537]: Failed to create framebuffer: Invalid argument
dets 16 19:16:49 TPCarbonX1 kwin_wayland[1537]: Rendering a layer failed!
dets 16 19:16:49 TPCarbonX1 kwin_wayland[1537]: Failed to find a working output layer configuration! Enabled layers:
dets 16 19:16:49 TPCarbonX1 kwin_wayland[1537]: src QRectF(0,0 1920x1200) → dst QRect(0,0 1920x1200)
dets 16 19:16:49 TPCarbonX1 kwin_wayland[1537]: src QRectF(0,0 64x64) → dst QRect(607,1021 64x64)
dets 16 19:16:50 TPCarbonX1 kwin_wayland[1537]: Atomic modeset test failed! Permission denied
dets 16 19:16:50 TPCarbonX1 kwin_wayland[1537]: Applying output configuration failed!
dets 16 19:16:50 TPCarbonX1 kwin_wayland[1537]: Failed to find a working output layer configuration! Enabled layers:
dets 16 19:16:50 TPCarbonX1 kwin_wayland[1537]: src QRectF(0,0 1920x1200) → dst QRect(0,0 1920x1200)
dets 16 19:16:50 TPCarbonX1 kwin_wayland[1537]: Atomic modeset test failed! Permission denied
dets 16 19:16:50 TPCarbonX1 kwin_wayland[1537]: Applying output configuration failed!
Adaptive Sync is set to Never
I’m sorry. I forgot the other part.
Set Adaptive Sync to never.
Set power saving to never dim or shut off the screen. That’s what’s crashing Kwin.
Mine would freeze when waking up. I could still issue commands with kdeconnect to reboot, sleep or shutdown, but there wasn’t any way to get a login screen. Kwin was frozen.
See the bug here.
Yeah. Setting it up to never dim or shut off has resolved the issue for now though I’m not a huge fan of this. Reading though the postings in that bug report though does show a fix is in the wild and will show up in either the next plasma update.
Thanks for the info! So let’s hope that the fix gets soon packaged into KDE Neon too..
From what I understand (and that understanding is VERY limited) that the team the builds Neon is very small so we might need to wait. Time will tell 
Me too.
I have a desktop computer, so I can’t force it to sleep. I lock the screen, and then 5 minutes later the screen should go off but it just dims instead. I guess it freezes when trying to gradually dim from on to off ?
Anyway, the screen is dimmed, except for the mouse pointer, which is still 100% bright. And that mouse pointer is frozen ! I couldn’t find anything that works, and had to force shutoff, pressing the power button for a continuous 5 seconds.
I disabled the screen auto turn off in power management to avoid this.
i have reverted to X until it is fixed.
Unfortunately the fix did not get into yesterdays user iso-s, so I guess it is not recommended to use them for installing unless the user is aware of needed workarounds…