As of 26 January build, either amd64 or i386, network manager detects the network, sees that an encryption key is needed, and then disconnects.
Manually connect to the hidden network, it's got the key already, click thru the drop downs and connects fine.
Obviously the network manager needs to put 2 and 2 together:
1. Hidden network.]
2. NM has the name of the network.
3. NM knows on a hidden network a key is required.
4. NM knows what the key is.
5. NM should enable wireless and connect but instead quits. Bug in the NM connection code.
6. Lost sight of how many times I had to manually connect today on two different pc's, one with Intel the other with Broadcom, same problem
Only thing NM is better at is going through the drop downs which was deadly slow. Now just slow.
As of 26 January build, either amd64 or i386, network manager detects the network, sees that an encryption key is needed, and then disconnects.
Manually connect to the hidden network, it's got the key already, click thru the drop downs and connects fine.
Obviously the network manager needs to put 2 and 2 together:
1. Hidden network.]
2. NM has the name of the network.
3. NM knows on a hidden network a key is required.
4. NM knows what the key is.
5. NM should enable wireless and connect but instead quits. Bug in the NM connection code.
6. Lost sight of how many times I had to manually connect today on two different pc's, one with Intel the other with Broadcom, same problem
Only thing NM is better at is going through the drop downs which was deadly slow. Now just slow.
BTW, Pangolin just goes ahead and connects.