Bug 182685 - nm-applet puts up a disconnected notification when I log in
Summary: nm-applet puts up a disconnected notification when I log in
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Christopher Aillon
QA Contact:
URL:
Whiteboard:
: 183030 (view as bug list)
Depends On:
Blocks: FC5Blocker
TreeView+ depends on / blocked
 
Reported: 2006-02-24 00:40 UTC by John (J5) Palmieri
Modified: 2013-03-13 04:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-01 00:22:42 UTC
Type: ---


Attachments (Terms of Use)

Description John (J5) Palmieri 2006-02-24 00:40:35 UTC
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.

Comment 1 Ingo Schaefer 2006-02-24 08:31:43 UTC
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

Comment 2 Dan Williams 2006-02-27 07:14:06 UTC
*** Bug 183030 has been marked as a duplicate of this bug. ***

Comment 3 Phil Anderson 2006-02-27 11:45:46 UTC
see also bug 171348 - NetworkManager and NetworkManagerDispatcher services not
started by default

Comment 4 Christopher Aillon 2006-03-01 00:22:42 UTC
This is fixed now in rawhide.


Note You need to log in before you can comment on or make changes to this bug.