Comment 42 for bug 1017738

Revision history for this message
jerrylamos (jerrylamos) wrote :

This bug is still present on latest Saucy Salamander 3.11.0-3.
On the same WPA encrypted network:
Precise on the same hardware boots up and connects automatically.
Nook HD+ boots up and connects autmatically even faster.
Asus Transformer TF101 boots up and connects automatically.
Samsung Galaxy Tab 2 7" boots up and connects automatically.
Boot Saucy and it "Disconnects" automatically.
1. Select internet applet.
2, Select connect to hidden wireless network.
3. Drop down window to show the networks.
4. Select the only network listed which Saucy had stored already.
5. Select connect to network.
Note, did not have to enter the network name, Ubuntu had it already.
Note, did not have to enter the encryption key, Ubuntu had it already.
Why did network manager decide not to use the info it had? Has to be a policy decision since it used to work.
Five manual mouse actions to do what Ubuntu's competition does automatically, and much faster.
Oh, on two different pc's same trouble. Ubuntu used to connect automatically, now it disconnects automatically.
Perhaps it might be worthwhile for ubuntu to look how easily the competition works....
BTW, I have tried the upstream kernel. Debian Development says their kernel has no problem, it authenticates as soon as Ubuntu asks it to.
Crawling through the syslogs etc. Saucy kernel authenticates as soon as it is asked to.
Saucy Network Manager tries to connect without using the key, of course it doesn't work, decides the network is out of range, it is not. Network Manager already has the key, knows it has the key, then and decides not to use it. ??