[SOLVED] NetworkManager "not authorized to control networking" error

Question

I'm installing arch with XFCE on an eeepc-1005ha. My wired ethernet works fine, both with dhcpcd eth0 and the NetworkManager (which connects automatically on boot). I'm following the instructions from this link: https://wiki.archlinux.org/index.php/Ne … nager#XFCE
I installed the NetworkManager and the xfce notify package. From the configuration setting part of the linked page, I disabled my internet connections with these commands:
ip link set down eth0
ip link set down wlan0
I added NetworkManager to the DAEMONS array, after dbus, per the instructions. I still get a "not authorized to control networking" error when I select a wireless network, so I followed the troubleshooting instructions. This is my .xinitrc file:
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
# exec gnome-session
# exec startkde
exec startxfce4 --with-ck-launch
#exec ck-launch-session dbus-launch startxfce4
# ...or the Window Manager of your choice
The exec line that's not commented out comes from the XFCE configuration instructions. The troubleshooting instructions for NetworkManager say to add
exec ck-launch-session wm
to .xinitrc, where wm is whatever window manager I'm using. Should
exec ck-launch-session startxfce4
or
exec dbus-launch ck-launch-session startxfce4
work? Neither of those options, nor the commented exec line in .xinitrc work.
Finally, I followed the NetworkManager troubleshooting instructions and added my user to the wheel group, using this command:
gpasswd -a myusername wheel
After a reboot, everything else still works (wired ethernet, xfce4, etc.) but the error upon connecting to wireless is still the same.
Any ideas? My user (username: myusername) does have full sudo privileges for this hostname.
Last edited by pythonscript (2012-05-22 18:41:41)

Answer 1

Both my flatmate and I are having this problem too, I am using openbox with consolekit and he is using awesome, again with consolekit.
We both use slim, me through inittab and he through the slim daemon.
By the way, it used to work, and has for around a year until now.
My outputs from ck-list-sessions:
Session1:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = 'x11'
active = TRUE
x11-display = ':0.0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2012-05-17T07:56:42.199869Z'
login-session-id = '1'
Session2:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = FALSE
x11-display = ':0.0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2012-05-17T07:56:43.178151Z'
login-session-id = '1'
Last edited by tntexplosivesltd (2012-05-17 10:37:04)