You are not logged in.
I'm having an intermittent problem when the computer doesn't fully suspend. It takes a while, but the computer usually wakes from the pseudo-suspended state, or sometimes I have to kill the power.
I'm not sure if this could be related. I'm using xscreenserver to lock my screen before suspending with:
xscreensaver-command --lock; systemctl suspend
Even when the computer actually suspends, I get the following output in the terminal:
$ xscreensaver-command --lock; systemctl suspend
xscreensaver-command: activating and locking.
xscreensaver-command: waiting for window 0x00c00023 to map
xscreensaver-command: waiting for window 0x00c00023 to map
xscreensaver-command: waiting for window 0x00c00023 to map
...
xscreensaver-command: waiting for window 0x00c00023 to map
xscreensaver-command: waiting for window 0x00c00023 to map
xscreensaver-command: Timed out waiting for screen to blank on 0x00c00023
I already removed the fadeout when locking.
Has anybody come across this problem? I can't find any other posting with this "waiting for window ... to map" message.
Last edited by OhBoy (2019-10-19 05:56:45)
Offline
I'm not sure whether the error is relevant, but you most likely want to "sleep 5" or so between the xss-cmd and suspend calls to give xscreensaver some time to react before the system is suspended.
The problem and messages then probably arise after the wakeup?
Edit: testing xscreensavers fade, make it rather 5 seconds.
Last edited by seth (2019-10-19 06:43:15)
Online
Use && instead of ; between commands.
I.e.
xscreensaver-command --lock && systemctl suspend
Offline