Bug 450233 - Firestarter fails to start on boot using networkmanager
Summary: Firestarter fails to start on boot using networkmanager
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: firestarter
Version: rawhide
Hardware: All
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Adam Miller
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-06 01:19 UTC by David
Modified: 2009-11-09 17:37 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-09 17:37:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David 2008-06-06 01:19:41 UTC
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:

Comment 1 Mark Whidby 2008-08-21 11:37:40 UTC
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.

Comment 2 Jessica Sterling 2009-03-06 22:06:59 UTC
This bug has been triaged

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 Paul Jenner 2009-04-17 18:59:49 UTC
This is a Firestarter bug, not NetworkManager. It should be changed to the Firestarter component.

Comment 4 Dan Williams 2009-10-16 22:38:01 UTC
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.

Comment 5 Adam Miller 2009-11-09 17:37:13 UTC
Firestarter has been retired as a package since upstream has been dead for years.


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