Dear Maintainer,

one of the last updates drastically limited network-manager's usability -- whenever i try to up or down a connection via the kde applet, all i get is "not authorized to control networking" (in /var/log/syslog and since the latest update today at least also a popup).
looks like #657279 -- but further research indicated that it ay be related to systemd (and maybe KDM, there are reports, the GDM users do not experience such issues).
the users trying to access nm are in the groups

dialout cdrom floppy audio video plugdev netdev powerdev scanner nvram vboxusers bluetooth pulse-access pulse-rt fuse subversion

and unless there's yet another networking related group, this should cover it.

Am 18.08.2014 21:38, schrieb arne anka:

How do you start your X session?

What's the output of
loginctl show-session $XDG_SESSION_ID


If that doesn't list an active logind session, you've found your problem.

kdm via /etc/init.d/ (and whatever systemd does with it)

Id=1
Timestamp=Mon 2014-08-18 21:13:44 CEST
TimestampMonotonic=143765718
VTNr=7
Display=:0
Remote=no
Service=kdm
Scope=session-1.scope
Leader=1651
Audit=1
Type=x11
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
Name=<username>

I have the same bug with the lightdm or kdm

I have just hit up against this bug on my Debian Testing VM. The
solution for me was to follow the instructions posted here
(http://jeffhoogland.blogspot.se/2012/05/howto-give-network-manager-sufficient.html),
i.e. create
'/etc/polkit-1/localauthority/50-local.d/org.freedesktop.NetworkManager.pkla'
with the following contents:

==========================================

[nm-applet]
Identity=unix-group:netdev
Action=org.freedesktop.NetworkManager.*
ResultAny=yes
ResultInactive=no
ResultActive=yes

==========================================

The connection was instantly configurable (starting a VPN connection in
this instance) afterwards.

I had just switched away from broken gdm3 to lightdm on the VM prior to
this.
Debian Release: jessie/sid
  990 testing         10.1.0.3
  500 unstable        10.1.0.3
  500 quodlibet-unstable 10.1.0.3
    1 experimental    10.1.0.3
--- Package information. ---
Depends                         (Version) | Installed
=========================================-+-================
libc6                           (>= 2.17) |
libdbus-1-3                    (>= 1.0.2) |
libdbus-glib-1-2               (>= 0.102) |
libgcrypt11                    (>= 1.4.5) |
libglib2.0-0                  (>= 2.37.3) |
libgnutls-deb0-28           (>= 3.2.10-0) |
libgudev-1.0-0                   (>= 165) |
libmm-glib0                    (>= 1.0.0) |
libndp0                          (>= 1.2) |
libnewt0.52                               |
libnl-3-200                   (>= 3.2.21) |
libnl-genl-3-200              (>= 3.2.21) |
libnl-route-3-200              (>= 3.2.7) |
libnm-glib4                 (>= 0.9.10.0) |
libnm-util2                 (>= 0.9.10.0) |
libpolkit-gobject-1-0          (>= 0.101) |
libreadline6                     (>= 6.0) |
libsoup2.4-1                  (>= 2.39.3) |
libsystemd-daemon0                (>= 31) |
libsystemd-login0                 (>= 31) |
libuuid1                        (>= 2.16) |
init-system-helpers            (>= 1.18~) |
lsb-base                      (>= 3.2-14) |
wpasupplicant                (>= 0.7.3-1) |
dbus                           (>= 1.1.2) |
udev                                      |
adduser                                   |
isc-dhcp-client           (>= 4.1.1-P1-4) |
libpam-systemd                            |
policykit-1                               |


Recommends        (Version) | Installed
===========================-+-===========
ppp              (>= 2.4.6) | 2.4.5+git20130610-4
dnsmasq-base                | 2.71-1
iptables                    | 1.4.21-2
modemmanager                | 1.2.0-1
crda                        | 1.1.2-1


Suggests           (Version) | Installed
============================-+-===========
avahi-autoipd                |

Scratch that, in order to work around another bug, I deleted and then
attempted to recreate a VPN connection - the configuration dialog that
appears is almost completely disabled. The only interesting thing coming
out of stdout is lots of:

=====================================================================

** (nm-connection-editor:12444): WARNING **: Unsupported connection type
'generic'

=====================================================================

When I 'sudo nm-applet', I was able to configure the VPN connection
fine, so it must be a permissions issue. When the VPN connected it
failed to set up a route to the subnet at the other end but I guess
thats another story...

Status: fixed

Debian Release: jessie/sid
Linux debian 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64
GNU/Linux

loginctl show-session $XDG_SESSION_ID
Id=1
Timestamp=Sat 2014-08-30 00:07:34 PDT
TimestampMonotonic=13226634
VTNr=7
Display=:0
Remote=no
Service=kdm
Scope=session-1.scope
Leader=1098
Audit=1
Type=x11
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
Name=<username>


I had this same problem after a recent system update (of many packages,
not just network-manager) -- when I tried to up a connection in the KDE
network-manager applet, it said "Not authorized to control networking".
After doing some research I thought it might have been an issue with
Polkit permissions, as I was also unable to mount volumes in Dolphin
with udisks, and I was unable to grant root privileges to Apper to
download package lists and install packages.  It also seemed to be
related to ConsoleKit because when I ran ck-list-sessions it had "active
= FALSE" in the output.  I then found that "ConsoleKit is currently not
actively maintained. The focus has shifted to the built-in
seat/user/session management of Software/systemd called systemd-logind!".


Next I did some research on systemd, and found the following page which
explains how to determine which init is active on boot-up:
(http://www.reddit.com/r/debian/comments/29ydkj/jessie_am_i_running_systemd/).
My system was running sysvinit.  I found it a little odd that I had an
active logind session while running sysvinit.  So after looking around
some more and not getting anywhere, I decided to try switching to
systemd for a single boot by adding "int=/bin/systemd" (symlink to
/lib/systemd/systemd) to the kernel line in the grub menu (pressing "e"
to edit the line).  I was fairly surprised to find that this fixed all
three of the problems, and it didn't seem to break anything.  I was able
to enable a connection with network-manager, and mount volumes in
Dolphin, and download lists and install packages in Apper.
Additionally, my default connection was enabled automatically on boot,
and that hadn't happened for several months (I had also used nmcli to
set it to autoconnect so that may have helped, but at least didn't fix
it on its own).  I did find the following thread in which someone
recommends installing task-kde-desktop, so I installed that package:
(http://forums.debian.net/viewtopic.php?f=17&t=116810).  (Someone else
recommends not using Apper, especially not with testing, and I will
probably take that advice.)  I then went ahead and installed
systemd-sysv to use systemd permanently.  I then ran journalctl to view
the systemd journal so I could check for error messages, and there
wasn't anything of concern.

It sounds like jessie is in the process of switching over to systemd
from sysvinit before it is released as stable, so my guess is that
something was changed in one or more packages which made them dependent
on systemd.  At least in my case, the problem wasn't caused by a bug in
network-manager itself.** **

For reference I won't be switching over to systemd, so a normal SysV
init here. Debian is committed to supporting alternative init systems,
so having something only work under systemd is unacceptable.

Control: reassign -1 network-manager

And why is that?  The submitter of this bug, when asked how they start their
X session, replied:

This doesn't point to a problem in systemd-shim.

Am 22.10.2014 um 05:38 schrieb Steve Langasek:

Two users, Tyler [1] and OmegaPhil [2], confirmed that they are/were
using sysvinit and in case of Tyler the issue was fixed by switching to
systemd as PID 1.

To me this looks like a problem in systemd-shim and a duplicate of [3]


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557#35
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557#40
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757698

Am 22.10.2014 um 06:04 schrieb Michael Biebl:

And the original bug submitter mentioned, that he modified
/etc/init.d/network-manager to debug this issue.

Since that init script is not used under systemd, it's a clear
indication that he's actually using sysvinit+systemd-shim.

The submitter did not say anything like this.  A modified version of the
conffile was attached to the bug, but there was no indication that it
actually managed to generate the desired debugging output to /tmp/nm.txt.

Arne, when you experienced this problem with network-manager, were you
running systemd (i.e., did you have the systemd-sysv package installed), or
were you running sysvinit?

Probably those of you that don't want to install systemd but want a
working network manager would find this information useful:

* I rebuilt network-manager with the following patch:
http://paste.debian.net/plain/128994

* Also followed the following howto:
http://jeffhoogland.blogspot.com.es/2012/05/howto-give-network-manager-sufficient.html

After that I was able to successfully run network-manager without
systemd, libpam-systemd, logind or anythingd


I think the following upstream bug is relevant:
https://bugzilla.gnome.org/show_bug.cgi?id=686997

Hi,
i am having exact the same problem with

systemd (215-5+b1)
nodm (0.11-1.3)
xfce4
network-manager (0.9.10.0-3)

No systemd-shim involved here.


Message on clicking on a wireless network:

"Failed to add/activate connection
(32) Not authorized to control networking."


I have not found A SINGLE LINE in any syslog on
what happened here which is a serious bug in itself.

Flo


flo@dgrab:~$ loginctl show-session $XDG_SESSION_ID
Id=c3
Name=flo
Timestamp=Wed 2014-11-05 07:30:51 UTC
TimestampMonotonic=173179700
VTNr=0
TTY=???
Remote=no
RemoteUser=root
Service=nodm
Scope=session-c3.scope
Leader=1292
Audit=0
Type=tty
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0


Flo

I can also confirm the issue with systemd as PID 1 and kdm.

What I notice is that logind does not consider me on a seat:

[1/501]mh@swivel:~$ loginctl list-sessions
   SESSION        UID USER             SEAT
        c3       1001 mh

1 sessions listed.

Can this be the issue here?

[2/502]mh@swivel:~$ loginctl show-session c3
Id=c3
Name=mh
Timestamp=Sat 2014-11-29 16:47:52 CET
TimestampMonotonic=32935356
VTNr=0
Display=:0
Remote=no
Service=kdm
Scope=session-c3.scope
Leader=3700
Audit=0
Type=x11
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0

I can also confirm the issue with systemd as PID 1 and kdm.

What I notice is that logind does not consider me on a seat:

[1/501]mh@swivel:~$ loginctl list-sessions
   SESSION        UID USER             SEAT
        c3       1001 mh

1 sessions listed.

Can this be the issue here?

[2/502]mh@swivel:~$ loginctl show-session c3
Id=c3
Name=mh
Timestamp=Sat 2014-11-29 16:47:52 CET
TimestampMonotonic=32935356
VTNr=0
Display=:0
Remote=no
Service=kdm
Scope=session-c3.scope
Leader=3700
Audit=0
Type=x11
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0

I had a simmilar issue.

I'm using sysvinit-core since systemd no longer supports rcS scripts like my
firewall.

I fixed the issue by removing
from my /etc/fstab, that I had to add in the first place for lxc to work.

Here, this means that lxc doesn't work anymore when I can edit connections;
and that I can't edit connections when I reactivate the line to use lxc...

Am 20.10.2017 um 12:21 schrieb Jean-Michel Vourgère:

Please consider converting your custom rcS init script to a native
service file or if it's from a Debian package (if so, which one?), file
a bug report.