Created attachment 489584 [details]
NM screenshot directly after boot with no existing network config

Hi,

I noticed some weirdness with NetworkManager's gnome3 applet on a system
with a motherboard with 2 integrated wired ethernet-controllers (of which 1 is in use).

I upgraded to the latest NM (and sub-packages) + gnome-shell from koji, but that did not help:
NetworkManager-0.8.997-8.git20110331.fc15.x86_64
gnome-shell-2.91.93-3.fc15.x86_64

I then removed all connections in nm-connection-editor, as well as removing any left over ifcfg-* files, and rebooted.

Directly after the (no config) boot, the gnome-shell nm-applet shows 3 on off
control for Wired without explaining which is which, see the screenshot: "NM-no-config-boot.png".

This is issue 1, which I'll title "on off controls without label"

By default NM did not try to connect (do dhcp or anything), which is different
from previous versions (iirc), this is issues 2: "does not auto connect to wired ethernet"

In my case the not auto-connecting is fine since I want to use a static IP. So I clicked on "Network Settings" and I wanted to configure my first wired connection, which NM correctly indicated as having a cable plugged on. But I couldn't the option button is turned off. I first needed to turn the connection on, wait for dhcp to finish before I could configure it. This is issue 3: "Cannot configure connection until it has established an ip connection"

Then I changed the settings to the static IP settings I wanted, but this was not
applied instantly. I believe this has always been the case, and it makes sense
(so as to not break any open tcp - sockets), but it is a bit surprising from an end user pov. IMHO the dialog where you can set the options should show a warning dialog when you save them, that they won't apply until you turn of and back on the connection (and that this may break ongoing downloads, etc.).
Issue 4: "Connection setting changes not instant applied, and user not informed of this"

While editing the connection I named it "eth0" rather then "Wired Connection 1", old habits are hard to loose I guess. After turning it off (to apply the new settings), the gnome-shell nm-applet looked really funky. See the
"NM-after-turning-eth0-off.png" screenshot. Note that turning it on and off repeatedly results in the same nm-applet menu in the off status every time.
Issue 5: "nm-applet menu funky after turning off wired connection"
I also looked in nm-connection-editor and that only saw the eth0 connection
once.

Then I turned eth0 back on, resulting in the "NM-eth0-on.png" screenshot. This again has 3 on/off controls for wired, 2 off which have no clear label what they turn on/off. I guess this is more or less the same issue as issue 1 "on off controls without a label""

Then I turned the wired connection of again, to see if the funky dialog in the
off state was a one time thing immediately after the reconfiguring if the
connection, but it was not, each time I turned it off I got the menu from
the "NM-after-turning-eth0-off.png" screenshot. I then did a
systemctl restart NetworkManager.service, which lead to an even funkier
nm-applet menu (it now had 4 on/off controls) regrettably I forgot to take
a screenshot of that one.

So all in all I've seen / encountered the following 5 issues:
1: "on off controls without label"
2: "does not auto connect to wired ethernet"
3: "Cannot configure connection until it has established an ip connection"
4: "Connection setting changes not instant applied, user not informed of this"
5: "nm-applet menu funky after turning off wired connection"

First of all sorry for lumping these all together, I wasn't sure how to group them hence I've just put them all in here for now, let me know if you want me to split some out in separate bug reports. I realize 2 might be intentional behavior, if it is that is fine with me. And I guess 4 is more of an RFE. 1, 3 and 5 I consider real bugs though.