xfce4-session issueshttps://gitlab.xfce.org/xfce/xfce4-session/-/issues2023-08-28T11:34:47Zhttps://gitlab.xfce.org/xfce/xfce4-session/-/issues/178monitors wake up if xflock4 run from hotkey2023-08-28T11:34:47ZChris Bainbridgemonitors wake up if xflock4 run from hotkeyxflock4 contains the following code (added in commit e4312c4983):
```
# Wait a bit so that user have time to raise finger from a key if
# the script is run in terminal.
[ -t 0 ] && sleep 1
```
`[ -t 0 ]` tests if the code is being run ...xflock4 contains the following code (added in commit e4312c4983):
```
# Wait a bit so that user have time to raise finger from a key if
# the script is run in terminal.
[ -t 0 ] && sleep 1
```
`[ -t 0 ]` tests if the code is being run in a terminal and, if so, sleeps for 1 second. However, xflock4 can be run by hotkeys (e.g. ctrl-alt-delete) from the desktop, which has the same wakeup issue as running from the shell. Therefore, the `sleep 1` should be unconditional.https://gitlab.xfce.org/xfce/xfce4-session/-/issues/175xflock4 does not lock the screen if the screensaver is disabled in settings2023-09-15T09:36:24ZLockywolfxflock4 does not lock the screen if the screensaver is disabled in settingsThis is clearly wrong, since the very point of disabling a screensaver in the Settings is to lock the screen manually when needed.
Locking the screen with xscreensaver also fails, since "xfce4-screensaver is already running".
I suggest...This is clearly wrong, since the very point of disabling a screensaver in the Settings is to lock the screen manually when needed.
Locking the screen with xscreensaver also fails, since "xfce4-screensaver is already running".
I suggest making sure that xfce4-screensaver is never running if the screensaver is disabled in the settings (perhaps by periodically polling the process space).