Sleep issue in plasma desktop
When my steam deck oled goes to sleep due to inactivity in desktop mode, the screen will go blank as expected, however if i then press the power button to resume, the screen never turns back on, i can hear the controller chime, so its supposed to wake up, but it doesnt, this install isnt even that old so i have no clue what could cause this.
11 Replies
open the terminal and run this
perl -pi -e 's/TurnOffDisplayIdleTimeoutSec=\d{1,4}/TurnOffDisplayIdleTimeoutSec=-1\nTurnOffDisplayWhenIdle=false/g' ~/.config/powerdevilrc
it will disable the screen turning off when idling
i have not been able to replicate the issue when just sleeping the device (legion go), however the screen itself turning off it will not return unless you wait like 5 mins then try to do input again (and there is no log entry as to whats happening either)the strange thing is that putting the device to sleep manually will let me wake it up no problem
but if i let it idle and go to sleep, i cant
same
update, reboot, go into desktop, go back to gamemode
or run the command i mentioned ant it wont happen anymore as the issue is caused by the screen being turned off when idle in desktop mode. not sleep.
maybe not related, but just on this latest build, I get the same on a desktop (bazzite:stable), Hardware is AMD CPU, GPU is AMD too, an RX6800. Screen doesn't wake, connected via DP. can ssh to the host at that point.
huh thats odd i couldnt replicate it on desktop 🤔
deck image right?
nvm you said bazzite:stable so desktop image
then its actually a kde bug, great
i’ll have a tinker about with my monitor settings to see if i can find a correlation somewhere, but yeah, desktop image
Getting the same issue on Nvidia Gnome Desktop image, external monitor connected via DP.
Pressing my keyboard will wake the computer (I can hear the PSU click on and fans spin up) but there’s no video signal.
Not the exact same bug
Screen idle only turns the screen off, dosent lock the machine
But this is for the other issue non handheld users are experiencing which has a very similar behavior
This is still happening on the testing branch btw, GNOME Nvidia desktop image