GNOME Bugzilla – Bug 316806
nm-applet shows wrong state at boot
Last modified: 2006-02-27 06:57:03 UTC
Version details: CVS 2005/09/19 Distribution/Version: Ubuntu Breezy Badger fresh daily I've got a freshly updated, from CVS 2005/09/19, copy of NetworkManager running on Ubuntu "Breezy Badger". It was built using the debian/ scripts found in the 'network-manager-0.4.1+cvs20050817-0ubuntu5' package. /etc/network/interfaces has the "map eth0" line commented off in the hotplug map, and there is no "auto eth0" line. These settings are so that there is no attempt to configure the interface at boot time (auto) since that results in a 'hang' when there is no cable clicked in, and so that there is no ifup at coldplug time during the boot, for the same reason. When NetworkManager starts up, it starts eth0 iff there is a cable clicked in. That's fine and dandy --- it's what I expect. So, when my desktop session starts, the gkrellm shows eth0. The problem is that the nm-applet has the wrong state for eth0. See the attached screenshot.
Created attachment 52442 [details] Screenshot showing the problem. Gkrellm and the nm-applet connection details dialog have it right, but the applet is displaying the wrong icon and has the wrong message in the tooltip. Also notice that the formating of the MAC address is not right, since each number should be zero padded on the left to 2 digits.
I have the same problem with the network state not being detected for a wired network. The package is NetworkManager 0.5.1 on FC4. As far as I can tell, the network settings themselves are OK.
*** This bug has been marked as a duplicate of 323729 ***