Seems to be an issue with mate-screensaver not supporting the PrepareForSleep systemd signal (it was previously supported but it was not configurable, so they removed the support).
As mentioned in one of the bug reports, a workaround is to install xss-lock and then create an item in the Preferences' Startup Applications to use:
xss-lock -l -- mate-screensaver-command -l
The xss-lock application will detect the systemd signal and instruct mate-screensaver to lock the screen. You can create the startup item manually or you can create a .desktop file in /etc/xdg/autostart/ to enable it for all users.
Upstream bug reports: /github. com/mate- desktop/ mate-screensave r/issues/ 228 /github. com/mate- desktop/ mate-screensave r/issues/ 84
https:/
https:/
Seems to be an issue with mate-screensaver not supporting the PrepareForSleep systemd signal (it was previously supported but it was not configurable, so they removed the support).
As mentioned in one of the bug reports, a workaround is to install xss-lock and then create an item in the Preferences' Startup Applications to use:
xss-lock -l -- mate-screensave r-command -l
The xss-lock application will detect the systemd signal and instruct mate-screensaver to lock the screen. You can create the startup item manually or you can create a .desktop file in /etc/xdg/autostart/ to enable it for all users.
This is really a kludge, but it works.