You are not logged in.
Recently, my monitor seems to be ignoring instructions to sleep via xscreensaver's "display power management" (standby/suspend/off after option) or from xfce4-power-manager.
When I try with xscreensaver, these lines are repeated many times in journalctl:
Feb 25 17:53:13 ease xscreensaver[725]: pam_unix(xscreensaver:auth): conversation failed
Feb 25 17:53:13 ease xscreensaver[725]: pam_unix(xscreensaver:auth): auth could not identify password for [facade]Meanwhile, the xscreensaver hack stops playing (pyro in this case), and the unlock screen is displayed. In the upper left, I see the following:
xscreensaver: 10:30:53: authentication via PAM timed out.When I try using xfce4's power management instead, the monitor doesn't go to sleep. I see nothing in journalctl to indicate that any event was tried and failed based on the time stamps of entries and when the events should have occurred based on my values for sleep.
DE: xfce4
Video: nvidia-390xx
CPU: Intel i7-4790K
MB chipset: Intel Z97
Last edited by graysky (2019-02-26 12:13:46)
Offline
Does it try to sleep and then wake up instantly? Also are you on AMDGPU?
Recently, my monitor seems to be ignoring instructions to sleep via xscreensaver's "display power management" (standby/suspend/off after option). DE is xfce4. Googling the output in journalctl hasn't yielded anything tangible. These lines are repeated many times:
Offline
@krutoileshii - I don't see it trying at all. The CPU in an Intel Haswell.
Offline
When I try with xscreensaver, these lines are repeated many times in journalctl:
w/o you actively trying to unlock the screen at the relevant timestamps?
I'd say sth. is causing spurious key input (the enter key) - since that would prevent dpms and might also fail to unlock xscreensaver w/ a bad password?
Does "xev -event keyboard" reveal anything? Can you ultimately unlock xscreensaver?
Offline
When I try with xscreensaver, these lines are repeated many times in journalctl:
w/o you actively trying to unlock the screen at the relevant timestamps?
I'd say sth. is causing spurious key input (the enter key) - since that would prevent dpms and might also fail to unlock xscreensaver w/ a bad password?
Does "xev -event keyboard" reveal anything? Can you ultimately unlock xscreensaver?
Yes, the entries in journalctl are autopopulating. I will try xev. Yes, I can unlock it fine.
Offline