ryniker at alum.mit.edu
Sat Nov 6 18:20:35 UTC 2010
>Yes, nm-applet complains this way (.xsession-errors) that NM is not running.
>I agree that, in addition, nm-applet should let the GNOME user know when NM
>service (/etc/inet.d/NetworkManager) is not running, instead of just removing
>nm-applet icon from the panel.
>I think of these ways to do that:
>1. display a standard GNOME notification message that NM is not available, at
> nm-applet startup time or at any time NM changes its status to unavailable
>2. keep nm-applet icon in a panel at all times, but if NM not available, then
> to mark it with a red arrow or some other visual overlay and display
> a "NetworkManager: disabled" message when moving a mouse over it.
> Note that red "x" overlay is already taken for "Networking disabled" status.
>3. both 1 and 2 above
I much prefer 2. This makes it clear that nm-applet is running (visually
distinct from the case where "Startup Applications" was configured to not
run nm-applet), and presents current status without disturbing the user
with notifications that require either explicit interaction to dismiss,
or patience to wait for them to vanish after some delay.
State-change notifications from strategy 1 can suffer when they do not
coincide with current activity: I was not interested in NetworkManager
yesterday, when nm-applet announced it was not running, but today is
different and I have forgotten the information from yesterday's notice.
More information about the test