disconnecting and reconnecting to a known wireless network prompts me for a key

[Steve Langasek]

In precise, if I disconnect from wireless and then try to reconnect to the same network, I'm prompted for a key for the wireless. This should not happen - the key is saved as part of a system-level connection, I should never need to be prompted for the key.

This is a regression vs. previous releases.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.1.90-0ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-2.6-generic 3.2.0-rc3
Uname: Linux 3.2.0-2-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Mon Dec 5 14:53:06 2011
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
IpRoute:
 default via 192.168.15.1 dev wlan1 proto static
 169.254.0.0/16 dev wlan1 scope link metric 1000
 192.168.15.0/24 dev wlan1 proto kernel scope link src 192.168.15.42 metric 2
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2011-11-08 (27 days ago)
WifiSyslog:

[Mathieu Trudel-Lapierre (cyphermox)]

I see InstallationMedia shows Ubuntu 10.04; upgraded to precise 27 days ago. Was this a formal upgrade test from the last LTS or an upgrade directly from Oneiric?

Regardless, confirming; this is indeed something that happens apparently because of the 0.8 to 0.9 migration and handling keyring passwords. I've noticed it only in those cases though, so it would be really useful to know the "precise" context of upgrades/updates for this system.

[Steve Langasek (vorlon)]

This is my main laptop continuously upgraded starting with lucid, so the last upgrade was from oneiric to precise.

[Mathieu Trudel-Lapierre (cyphermox)]

Steve,

Is there anything returned by 'gconftool -R /system/networking/connections'? I'm wondering if the applet might still be getting confused by gconf entries if some are left over from upgrades.

[Steve Langasek (vorlon)]

$ gconftool -R /system/networking/connections | wc -l
2521
$

So yes, a bit. :)

[Launchpad Janitor (janitor)]

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

[Mathieu Trudel-Lapierre (cyphermox)]

If this is indeed the gconf keys, it's all a matter of what the applet tries to do with them when converting them to system-level connections.

Steve, after stopping nm-applet, can you try to modify the "/apps/nm-applet/stamp" value to "2" then restarting it on the command-line? This should retry the conversion from gconf to keyfiles, and maybe seeing what's happening on the command-line will give clues as to what the problem is.

[Mathieu Trudel-Lapierre (cyphermox)]

Just in case, mind taking a backup of that gconf section first? ;)

[Steve Langasek (vorlon)]

well, I can't reproduce the issue now, so I guess we can consider this closed.