On 12/05/2022 18:10, David Wright wrote:
On Thu 12 May 2022 at 17:34:55 (+0100), Ottavio Caruso wrote:On 12/05/2022 14:31, Greg Wooledge wrote:On Thu, May 12, 2022 at 02:06:24PM +0100, Ottavio Caruso wrote:#!/bin/sh systemctl suspend && mate-screensaver-command -l This one seems to work, however I would have thought that the logical sequence would be: mate-screensaver-command -l && systemctl suspend that is, a) lock screen; b) suspend; c) resume with lock screen on. Instead, if I use the latter syntax, upon resuming, there is a 10 second delay before locking the screen, which is not ideal for obvious privacy reasons. Any input on that?"race condition" or not, it doesn't make sense that, upon resume, the screen lock pauses for 10 seconds and then reactivates.https://github.com/mate-desktop/mate-screensaver/issues/231
Thanks. Well spotted. However, I tried the workarounds suggested over there and it still delays a few seconds upon resume. It's definitely a Mate bug, then.
-- Ottavio Caruso A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?