http://defect.opensolaris.org/bz/show_bug.cgi?id=9799
Darren Kenny <dkenny at opensolaris.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXINSOURCE
AssignedTo|nwam-dev at opensolaris.org |dkenny at opensolaris.org
--- Comment #4 from Darren Kenny <dkenny at opensolaris.org> 2009-08-13
03:05:09 PDT ---
(In reply to comment #2)
> nwam 2009-08-04 with nwam GUI packages 2009-08-05
> this problem is still reproducible.
> hardware toshiba with iwk0 interface connected to security type WEP wlan.
>
> I think there are 2 problems here.
> 1. if user is in automatic profile, it is possible to complete edits in the
> wireless tab. The automatic iwk0 when selected should not be editable as the
> changes cannot be saved.
> (up'ing to P3 as this should not be allowed)
This must be allowed, since this information isn't really specific to the link,
but to the daemon as a whole. (maybe a UI Spec change is needed, but it still
make sense for someone to find it).
If you removed this ability, then if you had an empty User profile, and were
using the Automatic profile, you couldn't configure any wireless favourites.
>
>
> 2. When automatic profile is active, select to edit the wireless settings in
> User iwk0.
> It appears (logs and conf files attached) that the changes are saved.
> see known-wlan.conf.
Changes are saved as long as there is at least one entry in the list. If there
are no entries, the change isn't saved. This is the bug.
>
> However on relaunching the GUI, the original BBSID fields are filled in again,
> selecting Ok updates the known-wlan.conf file with all the available BBSID
> addresses see after_relaunch_known-wlan.conf
The fix is that if there is an empty list of values, then we should simply
delete the property, if we tried to set it to empty it would fail.
This has been fixed in SVN.
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
