GNU bug report logs - #34630
slock: unable to disable OOM killer. Make sure to suid or sgid slock.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 34630 in the body.
You can then email your comments to 34630 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Matthew Brooks <matthewfbrooks <at> mailbox.org>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: slock: unable to disable OOM killer. Make sure to suid or sgid slock.
Date: Sat, 23 Feb 2019 02:10:14 -0600

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 lock the screen.

The version of slock installed is:
"slock   1.4     out     /gnu/store/0v8kkhpk4qvmyab0wmg9wa7w8xynig01-slock-1.4"

The version of Guix is:
"guix (GNU Guix) 2a1ec7bcf4d754fb8a3cb7037e74fbf9cae88bf5"
which should be from today.


Just in case anyone goes and tests this that is unfamiliar with slock, there is no UI to it, to unlock it just type in your password and hit enter.
A red screen means incorrect password, you've backspaced all the way, or you've stopped typing.
Blue is you're currently typing.

Message #8 received at 34630 <at> debbugs.gnu.org (full text, mbox):

From: Carlo Zancanaro <carlo <at> zancanaro.id.au>
To: Matthew Brooks <matthewfbrooks <at> mailbox.org>
Cc: 34630 <at> debbugs.gnu.org
Subject: Re: bug#34630: slock: unable to disable OOM killer. Make sure to suid
 or sgid slock.
Date: Sun, 24 Feb 2019 16:28:35 +1100

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 following error: "slock: unable to disable 
> OOM killer. Make sure to suid or sgid slock."

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-service). This is done automatically 
as part of the default %desktop-services. I don't know of a way to 
do this on a foreign distribution.

Carlo

Message #13 received at 34630-done <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Carlo Zancanaro <carlo <at> zancanaro.id.au>
Cc: 34630-done <at> debbugs.gnu.org, Matthew Brooks <matthewfbrooks <at> mailbox.org>
Subject: Re: bug#34630: slock: unable to disable OOM killer. Make sure to
 suid or sgid slock.
Date: Sun, 24 Feb 2019 16:53:07 -0500

[Message part 1 (text/plain, inline)]

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-service). This is done automatically as part of the default
> %desktop-services. I don't know of a way to do this on a foreign
> distribution.

On a foreign distro I recommend using the host distro's package manager
for things like this. Guix doesn't support setuid programs on other
distros. Please see the manual section Setuid Programs for more info:

https://www.gnu.org/software/guix/manual/en/html_node/Setuid-Programs.html

[signature.asc (application/pgp-signature, inline)]

Message #16 received at 34630-done <at> debbugs.gnu.org (full text, mbox):

From: Matthew Brooks <matthewfbrooks <at> mailbox.org>
To: 34630-done <at> debbugs.gnu.org
Cc: Carlo Zancanaro <carlo <at> zancanaro.id.au>, Leo Famulari <leo <at> famulari.name>
Subject: Re: bug#34630: slock: unable to disable OOM killer. Make sure to
 suid or sgid slock.
Date: Mon, 25 Feb 2019 00:20:40 -0600

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/setuid-programs now.

Sorry again about the bother, since this wasn't actually a guix problem, and thanks for the help!

Message #19 received at 34630-done <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Matthew Brooks <matthewfbrooks <at> mailbox.org>
Cc: 34630-done <at> debbugs.gnu.org, Carlo Zancanaro <carlo <at> zancanaro.id.au>
Subject: Re: bug#34630: slock: unable to disable OOM killer. Make sure to
 suid or sgid slock.
Date: Mon, 25 Feb 2019 10:46:12 -0500

[Message part 1 (text/plain, inline)]

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 manually add slock to setuid-programs and it's working fine from /run/setuid-programs now.
> 
> Sorry again about the bother, since this wasn't actually a guix problem, and thanks for the help!

Great! :)

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.