Description of problem: Notification pops up when logging in. Basicly NetworkManager is not running so it can't get a connection and throws up the notification and then exits because NetworkManager is not running. Two issues here: Notifications should not be shown on startup. and Notifications should not be thrown up unless you have lost a connection not if you never had one. I'll leave it up to you to put this on the Blocker list but it is highly visable.
I can confirm that. NetworkManager not running and notification pops up after login. (this was not the point in the last week, I think) My Opinion: This Notification should appear on startup, if NetworkManager is configured to run _and_ is running _and_ there is no connection. This should be the same if there has been no connection before or if the connection is lost during boot or starting X Regards, Ingo Schaefer
*** Bug 183030 has been marked as a duplicate of this bug. ***
see also bug 171348 - NetworkManager and NetworkManagerDispatcher services not started by default
This is fixed now in rawhide.