Red Hat Bugzilla – Bug 450233
Firestarter fails to start on boot using networkmanager
Last modified: 2009-11-09 12:37:13 EST
Description of problem: With networkmanager set to on in chkconfig you get a error on boot with firestarter saying failed. If you open firestarter on desktop it works fine. However if you disable networkmanager to off in chkconfig and set network to on in chkconfig no more errors on boot and firestarter runs without having to open it on the desktop. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I find it will work if I install a NetworkManager dispatcher script. See:- http://www.darrenalbers.net/wiki/index.php?title=NetworkManagerScripts I then chkconfig firestarter off and let the script start handle it.
This bug has been triaged -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This is a Firestarter bug, not NetworkManager. It should be changed to the Firestarter component.
Yeah; if firestarter can't handle network devices coming and going, or even not available when it starts, we have a few options: 1) install the dispatcher script to restart firestarter when the network config changes. This is the sledgehammer approach 2) fix firestarter to respond to network events (either netlink or dbus) and handle the fact that networking is dynamic and can change on-the-fly 3) set NETWORKWAIT=yes in /etc/sysconfig/network which will make NM block startup until something has a network connection, or until 30 seconds have passed.
Firestarter has been retired as a package since upstream has been dead for years.