On Mon, Feb 25, 2019 at 12:20:40AM -0600, Matthew Brooks wrote:
> Thanks for the info, and sorry for the trouble. This isn't actually a foreign
> distro, my OS declaration just doesn't use %desktop-services, so the
> automatic setuid handling wasn't there. Thanks to your info I was able to
> man
Thanks for the info, and sorry for the trouble. This isn't actually a foreign
distro, my OS declaration just doesn't use %desktop-services, so the automatic
setuid handling wasn't there. Thanks to your info I was able to manually add
slock to setuid-programs and it's working fine from /run/setui
On Sun, Feb 24, 2019 at 04:28:35PM +1100, Carlo Zancanaro wrote:
> None of the programs in the Guix store (ie. /gnu/store) will have setuid or
> setgid set. On a Guix system you can install a slock screen-locker-service,
> which will provide a setuid binary for slock (via the
> setuid-program-servi
Hey Matthew,
I have successfully used slock on a Guix system, but I haven't
tried using the Guix slock on a foreign distribution. I would
expect it to not work, and the error message gives us an idea why:
When using the guix installed slock, it doesn't lock the screen,
and errors with the fo
When using the guix installed slock, it doesn't lock the screen, and errors
with the following error:
"slock: unable to disable OOM killer. Make sure to suid or sgid slock."
When downloading the source and doing the standard "make && sudo make install",
slock does not error, and will properly lo
