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

[Dave Morley]

I open n-m applet to connect to wifi click on my ssid and get the folloing dialog window

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

If I try and connect via ubiquity itself the installer just locks up on enabling the wifi.

I switched to Live desktop and there the wifi is working as expected.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubiquity 2.15.6
ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4
Uname: Linux 3.9.0-4-generic x86_64
ApportVersion: 2.10.2-0ubuntu1
Architecture: amd64
CasperVersion: 1.333
Date: Tue Jun 11 11:41:10 2013
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --
LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130611)
MarkForUpload: True
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Dimitri John Ledkov (xnox)]

Could be related to missing logind seat/session setup.

[Philippe Coval (rzr)]

Does this also fail as root ?
And please can you report the groups of the user ? just type "groups"

[Antti Laiti (pulk)]

I got this same problem when I installed Ubuntu 13.10. Did not see it with Ubuntu 13.04 running on same machine. I did not upgrade but made a clean install.

When I run nm-applet as root (gksu nm-applet), I get a different error: (32) Insufficient privileges. As a normal user I get "(32) Not authorized to control networking".

[laiti@minia ~]$ groups
guru adm dialout cdrom sudo audio dip video plugdev fuse netdev lpadmin sambashare jester koti maemo

I added myself to netdev just some minutes ago and did logout-login but it didn't help.

[Antti Laiti (pulk)]

also nm-connection-editor does not allow me to edit connections, not even when ran as root.

[Antti Laiti (pulk)]

It seems that I have accidentally erased part of my /etc/polkit-1 directory. Returning it to previous state & reboot fixed the error. I am not 100% sure if it was about that at all since I did other changes before the reboot.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1189875

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubiquity - 16.10.12

---------------
ubiquity (16.10.12) yakkety; urgency=medium

  * Automatic update of included source packages: base-installer
    1.158ubuntu4, console-setup 1.142ubuntu5, hw-detect 1.117ubuntu3.
  * data/ubiquity.desktop.in: run ubiquity in sudo rather than depending on
    pkexec to do the right thing. (LP: #1189875)

 -- Mathieu Trudel-Lapierre <email address hidden> Wed, 05 Oct 2016 15:04:21 -0400