/etc/make.conf:
Code: Select all
USE="consolekit dbus pam policykit udev udisks upower"
Code: Select all
gnome-base/gvfs gdu
Code: Select all
# emerge -C hal hal-info policykit devicekit devicekit-disks devicekit-power
# emerge -av gvfs udisks upower
# emerge -avDNut world
For GTK+ based desktops:
Code: Select all
# emerge -av polkit-gnome
Code: Select all
# emerge -av lxpolkit
Code: Select all
# emerge -av polkit-kde-agent
Code: Select all
$ man 8 polkit
Code: Select all
CONFIG_USB_SUSPEND=y
CONFIG_IDE=n
Code: Select all
CONFIG_AUDITSYSCALL=y
Code: Select all
# /etc/init.d/hald stop
# rc-update del hald
# rc-update add dbus default
# rc-update add consolekit default
# /etc/init.d/consolekit start
Code: Select all
$ echo 'exec ck-launch-session startxfce4' > .xinitrc
$ startx
Code: Select all
$ echo 'exec ck-launch-session dbus-launch --sh-syntax --exit-with-session openbox-session' > .xinitrc
$ startx
Gentoo has following display managers in Portage with native ConsoleKit support:
xdm
slim
lightdm
old gdm-2 (note that gdm-3.8+ removed CK support and only works with systemd)
kdm
lxdm
Make sure to use latest version(s) since some of them gained support only recently.
In the end, you should see active session in or outside of X11:
Code: Select all
$ ck-list-sessions
Session1:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = FALSE
x11-display = ''
x11-display-device = ''
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2010-12-25T09:44:12.519713Z'
login-session-id = '1'
idle-since-hint = '2011-01-02T16:04:09.020983Z'
Session3:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = TRUE <- The most important part. This is what we are aiming at.
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2011-01-02T16:03:40.847555Z'
login-session-id = '1' <- If this is empty, you propably missed the CONFIG_AUDITSYSCALL=y option in kernel.
- You removed nox11 parameter from /etc/pam.d/system-login earlier, but forgot to restore it now that the native ConsoleKit support is available
in your display manager?
- When using the native ConsoleKit support (which is either enabled by USE="consolekit" or always enabled in the different display managers)
you should *not* write commands like dbus-launch or ck-launch-session yourself *anywhere* because the display manager does it for you.
- Entries in /etc/fstab *conflict* with sys-fs/udisks. For example, if you want your cdrom to be handled by udisks (and file manager supporting it, like nautilus, pcmanfm or Thunar) you should *remove entries* related to it from /etc/fstab.
- Need to recompile dev-libs/dbus-glib after deb-libs/glib upgrade. Yes, by hand:
Code: Select all
# emerge -av1 dbus-glib
Code: Select all
# emerge -av1 --noconfmem consolekit pambase shadow
# etc-update










