wifi login broken in Quantal

Bug #1047959 reported by Aaron Bentley
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
unity-greeter (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When lightdm starts up, it prompts me to enter the password for the WiFi network "BEER", but this is not my network, and I don't have credentials for it.

When I attempt to select a correct network, "bentley5", I get the error message "(32) Not authorized to control networking".

Of course, when I start a Unity session, it automatically logs me into "bentley5" (as it did under precise).

$ lsb_release -rd
Description: Ubuntu quantal (development branch)
Release: 12.10

$ apt-cache policy lightdm
lightdm:
  Installed: 1.3.3-0ubuntu3
  Candidate: 1.3.3-0ubuntu3
  Version table:
 *** 1.3.3-0ubuntu3 0
        500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Antti Kaijanmäki (kaijanmaki) wrote :

The error message "not authorized to control networking" is probably a duplicate of bug #1048522 which has been fixed in quantal. Please, try to reproduce with the latest updates and report back if the problem persists.

The network "Beer" probably has a system wide configuration which has been created earlier maybe even just by clicking the network under the normal session. You can get rid of your machine trying to autoconnect to it by removing the configuration:

1) log in to your normal session
2) click networking menu
3) -> Edit Connections...
4) -> Wireless
5) Select the network "Beer" and click "Delete.."

Changed in lightdm (Ubuntu):
assignee: nobody → Antti Kaijanmäki (kaijanmaki)
status: New → Incomplete
affects: lightdm (Ubuntu) → unity-greeter (Ubuntu)
tags: added: network-manager-applet
Revision history for this message
Aaron Bentley (abentley) wrote :

From my POV, the bug has not been fixed.

1. AIUI, it's still trying to connect to arbitrary connections (i.e. BEER), instead of letting the user decide which connection to use.

2. The new error message, something like "Insufficient privileges to add/activate connection" doesn't give the user any idea how to fix the problem

3. There is inconsistency about passwords. The fact that BEER prompts me for a password leads me to expect that if I choose a different network, I would be prompted for a password, not get an error.

Changed in unity-greeter (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity-greeter (Ubuntu):
status: New → Confirmed
Changed in unity-greeter (Ubuntu):
assignee: Antti Kaijanmäki (kaijanmaki) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.