* Revert r28400 because ConsoleKit got reverted to 0.4.1.

svn path=/nixos/trunk/; revision=28587
This commit is contained in:
Eelco Dolstra 2011-08-15 14:48:32 +00:00
parent 4bc0bfec4c
commit 4790c147bf
4 changed files with 4 additions and 25 deletions

View file

@ -75,8 +75,7 @@ in
security.pam.services =
[ { name = "chsh"; rootOK = true; }
{ name = "chfn"; rootOK = true; }
# Enable ownDevices for the services/x11/display-managers/auto.nix module.
{ name = "su"; rootOK = true; ownDevices = true; forwardXAuth = true; }
{ name = "su"; rootOK = true; forwardXAuth = true; }
{ name = "passwd"; }
# Note: useradd, groupadd etc. aren't setuid root, so it
# doesn't really matter what the PAM config says as long as it

View file

@ -52,11 +52,6 @@ in
'';
};
# The ConsoleKit PAM connector launches a local session, but it's
# not set as "active" (maybe because x11-display-device is not
# set). Launching a child session seems to fix that.
services.xserver.displayManager.forceCKSession = true;
};
}

View file

@ -55,8 +55,8 @@ let
# Start a ConsoleKit session so that we get ownership of various
# devices.
if [ \( -z "$XDG_SESSION_COOKIE" -o -n "${toString cfg.displayManager.forceCKSession}" \) -a -z "$CK_STARTED" ]; then
CK_STARTED=1 exec ${pkgs.consolekit}/bin/ck-launch-session "$0" "$sessionType"
if test -z "$XDG_SESSION_COOKIE"; then
exec ${pkgs.consolekit}/bin/ck-launch-session "$0" "$sessionType"
fi
# Handle being called by kdm.
@ -164,12 +164,6 @@ in
apply = toString;
};
forceCKSession = mkOption {
internal = true;
default = false;
description = "Whether to force launching of a ConsoleKit session.";
};
session = mkOption {
default = [];
example = [

View file

@ -106,17 +106,8 @@ in
# Allow null passwords so that the user can login as root on the
# installation CD.
security.pam.services = singleton
{ name = "slim";
allowNullPassword = true;
ownDevices = true;
};
security.pam.services = [ { name = "slim"; allowNullPassword = true; } ];
# The ConsoleKit PAM connector launches a local session, but it's
# not set as "active" (maybe because x11-display-device is not
# set). Launching a child session seems to fix that.
services.xserver.displayManager.forceCKSession = true;
};
}