© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
@ Alaric
This problem existed pre-Karmic and as such should not be considered a regression. Furthermore, the case outlined here is not the typical use case, as NM should automatically re-connect a hidden network that's been previously connected. Unfortunately, drivers don't always support the ability to scan for a specific ESSID ( that's how NM is able to detect that the hidden AP is available ), and there's not much NM can do about it... although one could argue that if the driver isn't fully capable, the feature should be disabled in the UI.
As for landing in Karmic, the plan was to try and get 0.8~rc2 released as an SRU for Karmic, however if that's not excepted then a stable version will be pushed to the NM main PPA.