Red Hat Bugzilla – Bug 134893
NetworkManagerInfo and the panel-icon life-cycle
Last modified: 2013-04-02 00:20:12 EDT
NetworkManagerInfo currently controls the NetworkManagerNotification
process in an unsophisticated fashion. It should make sure that when
it quits, it kills the icon. It should also monitor the icon for it
dying as well. Finally, it should kill the icon when we're in an
uninteresting state (Wired only).
After a discussion here, here is what needs doing for the life cycle:
* NetworkManager is considered 'on' if it's running. The way to
enable it is to do 'service NetworkManager start', or use chk-config.
* NetworkManagerInfo is always started at the beginning of the user's
session. If NetworkManager isn't running, it exits.
* NetworkManagerInfo needs to install a desktop file so that it gets
added to the user's session. Ray can probably help get this right.
* NetworkManagerInfo needs to monitor the state of network devices.
If we have just wired devices, then we need to kill the panel icon
after a certain time (say 20-30 seconds).
* The panel icon needs to exit if NetworkManagerInfo dies or is
* NetworkManagerInfo needs to restart the icon if it dies or is
killed. It should guard against starting it too many times. Also,
this behaviour is incompatable w/ something like bugbuddy so we'll
have to disable that.
> * The panel icon needs to exit if NetworkManagerInfo dies or is
Done and committed to gnome.org CVS. I currently call exit(), but
there's probably a better way?
exit change to gtk_main_quit in CVS
exit() should be fine.
> If NetworkManager isn't running, it exits.
Done. We exit in 30 seconds if NetworkManager goes down. If
NetworkManager is not available when NetworkManagerInfo starts, we quit.