Regarding the suid bit, why don't we let the program decide what suid
should be applied to it's programs?
https://github.com/NixOS/nixpkgs/pull/22532
On Tue, 7 Feb 2017 at 19:38 wrote:
> On 2017-02-07 19:50, Tomasz Czyż wrote:
> > David,
> >
> > I assume you are not talking
On 2017-02-07 19:50, Tomasz Czyż wrote:
David,
I assume you are not talking about
https://github.com/NixOS/nixpkgs/issues/16485 [2]?
In fact I'm talking about https://github.com/NixOS/nixpkgs/issues/16845
:-) my mistake
Usually I'm using this kind of stuff as part of user session/desktop
David,
I assume you are not talking about
https://github.com/NixOS/nixpkgs/issues/16485?
Usually I'm using this kind of stuff as part of user session/desktop
environment. Which means that xfce-session or gnome-session or whatever is
starting all those for user.
Do we really need to start is
As a user I would expect slock to be installed and added to the suid list
if I selected it as my screensaver. That way I can also invoke it manually
in cases where I want to lock the screen manually.
On Mon, 6 Feb 2017, 23:51 , wrote:
> Hi!
> I am making a patch to fix issue
Hi!
I am making a patch to fix issue #16485 but I have encountered an issue.
I added an option called screenLock to
services.xserver.desktopManager.xfce that can take only "xscreensaver"
"xlockmore" "slock" "gnome-screensaver" as values but:
- gnome-screensaver seems to not exist anymore, at