I agree that my solution is not a proper solution. My point was that it
shows that the problem is a timing issue. NM has gotten so quick to make
a wired connection at boot, that it sometimes (fast dhcp transaction)
leaves nm-applet in the dust. You are right, some type of query is
needed. Maybe there should be a nm-applet "up/down" state that gets sent
to NM.
Bill Moss
Robert Love wrote:
On Tue, 2005-09-20 at 20:12 -0400, Bill Moss wrote:
My analysis is that on boot to wired NM reaches stage5 of activation
(where the dbus change of state signal is sent) before nm-applet is up
and ready to receive that signal. My solution was to change the order of
nm-applet in Gnome sessions Start Programs from the value 10 to the
default value of 50. Since that change, nm-applet has not once shown the
no-connection icon at boot when a good connection was in fact made.
This presumes you login right away (or even automatically), so its not a
proper solution. We should have nm-applet query the status if need be.
Robert Love
--
Bill Moss
Professor, Mathematical Sciences
Clemson University
_______________________________________________
NetworkManager-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/networkmanager-list
