Chrome OS Version : 0.7.47.0 (56a18fe) Chrome Version : Chromium 6.0.425.0 (48831)

What steps will reproduce the problem? 1. Set network authentication parameters from outside of Chrome (via dbus to flimflam, for example) 2. Open menu and select network - new parameters are not visible. 3. Open menu and select network again - new parameters are now visible. (parameters are also visible if several seconds elapse between opening the menu and selecting the network)

The network parameters are updated when the libcros MonitorNetwork() callback is invoked. This happens at the end of a wireless network scan, as initiated when the network menu is opened, but it usually doesn't finish before the individual network is selected, so updated information may not be reflected in the UI.

At a lower level, MonitorNetwork() is registering with dbus to receive signals on flimflam's root Manager interface, while changes to network settings generate signals on a the Service interface of a particular service path.

Possible approaches to a solution: 1. Cause flimflam to fire the PropertyChanged signal on the Manager interface on / when auth info changes on a service. This is hack, since it's not a property of this node or interface that has changed; it also has the potential to be quite chatty, particularly if generalized.

2. Make MonitorNetwork monitor some more signals; in particular, it could monitor for changes to services that require authentication. This is a bit fragile as the set of services is highly dynamic as the user moves around, and it's not hard to see a situation where this falls out of sync. For the problem at hand, this could be limited to services usigng 802.1x authentication, and those should be present in our service list (as remembered services if nothing else).

3. Make the UI code explicitly request fresh network information before displaying it. This adds a potential UI delay.

I'm currently working on #3.

Issue 4032 has been merged into this issue.

Should be fixed with:

http://git.chromium.org/viewvc/chrome?view=rev&revision=53227 http://codereview.chromium.org/3019015 http://codereview.chromium.org/2901002

See bug #4674 for possible improvements to the implementation of this fix.

Able to reproduce the issue i.e (Network menu does not immediately reflect external changes to settings) with latest

Google Chrome OS 0.8.61.0 (Official Build e9e9ce49) dev x86-dogfood Google Chrome 6.0.472.15 (Official Build 54255)

Hence reopening the bug.

I believe the reported versions (0.8.61.0 and 0.8.60.3) both precede the fix.

We will retest with post 0.8.63.x

Verified fix with latest Google Chrome OS 0.8.65.201008091826 (Official Build 5f66b866) dev x86-dogfood Google Chrome 6.0.489.0 (Official Build 55374)

Moved to: Issue chromium:185790