PINE64
Phosh: Idles to Lockscreen Without Powering Off Display - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+--- Thread: Phosh: Idles to Lockscreen Without Powering Off Display (/showthread.php?tid=15002)



Phosh: Idles to Lockscreen Without Powering Off Display - Merc - 10-01-2021

I have my Pinephone with Arch+Phosh installed set to turn off the display after one minute, the problem is that instead of turning off the display it will switch to the lock screen and stay powered on indefinitely. This is remedied when I restart Phosh with
Code:
# systemctl restart phosh.service
then it will behave as expected and power off the screen after one minute and the problem is gone until I reboot.

I've re-installed Arch+Phosh but the problem persists. It's a custom build so it could be one of a hundred things causing this to happen.

I looked to see if anyone else was having this problem but I couldn't find anything about it. I played around with the phosh.service file thinking  the problem had something to do with the order Phosh is started but I haven't gotten anything to work. Anyone have this problem?

Edit: I solved the problem, it was caused by
Code:
/usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSaver
running at boot causing conflict with the screen turning off. I renamed org.gnome.ScreenSaver to org.gnome.ScreenSaver.bak effectively disabling it and the problem went away.


RE: Phosh: Idles to Lockscreen Without Powering Off Display - e1337 - 11-01-2021

I actually think this is some sort of GNOME overall bug. It happens with GNOME 3, too, on my x64 machine: launch any application that inhibits screensaver. Naturally (and as expected), this now will block the automatic screen turn-off and lock screen while you still see your desktop. BUT if you now lock the screen manually, where GNOME 3 usually will turn it off after in seconds, it suddenly is shown forever - even though that makes absolutely no sense IMHO: the entire point of screensaver inhibit is to keep something visible like a video with with no user interaction, which of course already is a lost battle when the screen was locked (no video visible anymore then, is it?). Preventing a further power save via screen turn-off at this point just seems super pointless to me. Maybe preventing suspend actually makes sense so audio players can use it, but keeping the lock screen lit up feels like a conceptual bug/design mistake with only disadvantages.

So it might probably make sense to report it at https://gitlab.gnome.org/ but don't ask me for which subproject.