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

pythonscript · 2012-05-13 14:03:03

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)

wonder · 2012-05-13 14:26:51

install polkit-gnome, comment out this stuff from ~/.xinitrc and use "exec ck-launch-session startxfce4" and relogin.

if [ -d /etc/X11/xinit/xinitrc.d ]; then
  for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
  done
  unset f
fi

pythonscript · 2012-05-13 14:39:50

The error still occurs. I installed polkit-gnome, updated .xinitrc to this, and logged off/rebooted:

#!/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 startxfce4

# ...or the Window Manager of your choice

chamber · 2012-05-13 14:47:45

What are you using to log in? If you are using slim remove ck-launch-sessions from your .xinitrc

wonder · 2012-05-13 14:58:09

do ps ax and see if /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 runs. also it will be nice to paste ck-list-sessions

pythonscript · 2012-05-13 15:46:14

ps ax | grep polkit returns

671 ?        Sl     0:00 /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1

and ck-list-sessions returns:

Session1:
	unix-user = '1000'
	realname = 'Ricardo Altamirano'
	seat = 'Seat1'
	session-type = ''
	active = TRUE
	x11-display = ':0'
	x11-display-device = '/dev/tty7'
	display-device = ''
	remote-host-name = ''
	is-local = TRUE
	on-since = '2012-05-12T01:24:31.907162Z'
	login-session-id = ''
Session2:
	unix-user = '1000'
	realname = 'Ricardo Altamirano'
	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-12T01:24:32.485379Z'
	login-session-id = ''

I am using XDM to log in, configured per the instructions on the wiki.

tntexplosivesltd · 2012-05-17 08:03:31

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)

skunktrader · 2012-05-17 09:15:28

Did you try this incantation yet in your ~/.xinitrc

exec dbus-launch --exit-with-session startxfce4

pythonscript · 2012-05-17 14:14:33

skunktrader wrote:

Did you try this incantation yet in your ~/.xinitrc
exec dbus-launch --exit-with-session startxfce4

Currently I have

exec ck-launch-session startxfce4

in ~/.xinitrc. Will other aspects of my system fail when I change it to your suggestion? (It's trivial to change it back, of course, but I don't want to fix one problem only to cause another).

Hasenblut · 2012-05-18 12:04:37

Had a similar error as I could only connect to known networks and couldn't edit or establish vpn connections.

with
.xinitrc:

## test for an existing bus daemon, just to be safe
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
    ## if not found, launch a new one
    eval `dbus-launch --sh-syntax --exit-with-session`
    echo "D-Bus per-session daemon address is: $DBUS_SESSION_BUS_ADDRESS"
fi

exec openbox-session

and in /etc/slim.conf ( deleted 'ck-launch-session dbus-launch')

login_cmd           exec /bin/bash -login ~/.xinitrc %session

I am now able to edit the connections or connect to a vpn after restarting 'slim' and 'networkmanager' .
I also have now only two ck-sessions listed, not three as before.

Edit: Still works after a reboot

Last edited by Hasenblut (2012-05-18 12:20:49)

pythonscript · 2012-05-18 15:05:09

@Hasenblut - I'm not entirely sure your error is similar, since I couldn't connect to any networks at all because of authorisation problems. Also, I'm not using slim as a log in manager. I'm using xdm.
@skuntrader - Your suggested change worked, but another error cropped up (which is why I was asking if this would cause other problems). Now, every time I boot, I'm asked to manually run fsck on my /dev/sda1 partition. This has never occurred before I made your change. Is this an unrelated issue, or did removing ck-launch-session from my ~/.xinitrc file somehow foul this up?

Last edited by pythonscript (2012-05-18 15:05:35)

tntexplosivesltd · 2012-05-20 11:46:30

pythonscript wrote:

Now, every time I boot, I'm asked to manually run fsck on my /dev/sda1 partition. This has never occurred before I made your change. Is this an unrelated issue, or did removing ck-launch-session from my ~/.xinitrc file somehow foul this up?

Did you run fsck on the partition? It might just be coincidental. Does it still come up after you run fsck on the partition?

pythonscript · 2012-05-20 12:23:56

Yes, I ran fsck on that partition, but it still comes up most of the time when I reboot.

tntexplosivesltd · 2012-05-20 13:28:15

I can confirm that skunktrader's sugestion works for me at least, and I don't get the fsck messages (I beleive these are unrelated). Hope this helps everyone else.

pythonscript · 2012-05-20 13:51:10

tntexplosivesltd wrote:

I can confirm that skunktrader's sugestion works for me at least, and I don't get the fsck messages (I beleive these are unrelated). Hope this helps everyone else.

The error has since stopped after I rebooted 4-5 times and ran fsck each time. I think the problem is solved, then.

tntexplosivesltd · 2012-05-22 09:58:16

Cool, just add "[SOLVED]" to the start of the topic

Arch Linux

#1 2012-05-13 14:03:03

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

#2 2012-05-13 14:26:51

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

#3 2012-05-13 14:39:50

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

#4 2012-05-13 14:47:45

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

#5 2012-05-13 14:58:09

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

#6 2012-05-13 15:46:14

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

#7 2012-05-17 08:03:31

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

#8 2012-05-17 09:15:28

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

#9 2012-05-17 14:14:33

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

#10 2012-05-18 12:04:37

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

#11 2012-05-18 15:05:09

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

#12 2012-05-20 11:46:30

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

#13 2012-05-20 12:23:56

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

#14 2012-05-20 13:28:15

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

#15 2012-05-20 13:51:10

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

#16 2012-05-22 09:58:16

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

Board footer