immanuelhaffner / slock2 Goto Github PK

slock2 uses systemd suspend to suspend your computer. When running in debug mode, slock2 produces an error message, saying that suspending failed. However, it works. This is probably a false alarm. (Maybe suspend's return value changed...)

Since slock2 operates with root privileges, the --logfile parameter can be exploitet to overwrite any file.

Proposed fix:
When --logfile is specified, drop root privileges to open the specified file. On failue, fall back to the default logfile (with root privileges).

Since a recent update, when running slock2 I'm getting the following error:

slock2: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory