© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Thanks for your bug. You probably have been confused by the way network-admin works on dapper.
When you add a profile it's created with the information you have at the moment. When you do changes, you don't modify the selected profile but the running session. To store the changes to add profile you have to add a profile with the same name. Reading that, do you think the tool works as described or do you still have some non expected behaviour from it?
The way the tool work on dapper is really not obvious and we worked with upstream to change that on edgy. Now the "add" button next to the profile has been changed to a "save" one which open a window asking for the name of the profile to use and the name is preset to the current profile. Do you think that behaviour change fixes your issue?