On Wed, May 16 2012, Michael Biebl <bi...@debian.org> wrote: > You need a active ConsoleKit session, ie. please make sure you have > consolekit and policykit installed (the latter is a recommends of > network-manager). > Then use a login manager, like gdm3, kdm or lightdm, which set's up a > ConsoleKit session properly. > > A active ConsoleKit session is required by NetworkManager to determine > if you are allowed to control the network settings or not.
I have consolekit, policykit-1, and policykit-1-gnome all already
installed. I guess you wanted me to run ck-list-sesssions, not
ck-list-session:
servo:~ 0$ ck-list-sessions
Session12:
unix-user = '1000'
realname = ''
seat = 'Seat2'
session-type = ''
active = FALSE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = FALSE
on-since = '2012-05-16T10:36:53.044308Z'
login-session-id = '4294967295'
servo:~ 0$
In any event, as far as I understand things according to the
documentation included with network-manager, the point of consolekit is
to ensure that the user is a member of netdev. That can either be
managed by consolekit, or the user can be added to that group manually.
As I am already a member of netdev, even without consolekit's help, I
don't see how this is the issue:
servo:~ 0$ groups
jrollins adm dialout cdrom floppy sudo audio dip video plugdev netdev bluetooth
lpadmin fuse kvm
servo:~ 0$ getent group | grep netdev
netdev:x:109:jrollins
servo:~ 0$
If there is something else that consolekit is supposed to be doing the
documentation makes no mention of it.
jamie.
pgpdGWFJoRiTY.pgp
Description: PGP signature
