The Debian bug is marked as Fix Released and based on the changelog in
the Debian bug, this should be fixed in Hardy and later, so I am marking
the bug as such. If people are having problems with later releases, I
suggest filing a new bug.
** Changed in: firestarter (Ubuntu)
Status:
Firestarter has been dormant for a couple years (yes, there has been a
couple patches...). First off, the service portion of Firestarter is
loading on boot. You can verify on boot-up with a sudo iptables -L
-n...if you see anything special, Firestarter ran its scripts. So you
are protected.
I can confirm that the problem still persists with Karmic
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
Problem still in karmic with firestarter 1.0.3-7ubuntu5.
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
** Branch linked: lp:ubuntu/karmic/firestarter
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I had the same problem...
For people who are looking for an other firewall, just notice that you can
install Gufw, using synaptic
In console
#Uninstall Firestarter
$ sudo apt-get autoremove firestarter
#install Gufw
$ sudo apt-get install gufw
--
Firestarter init fails on system boot when
Reopened for Jaunty. The problem is still here on Ubuntu 9.04 RC. The
current package version (1.0.3-7ubuntu4) no longers contains the
/etc/NetworkManager/dispatcher.d/50firestarter file that was included
into the 1.0.3-2ubuntu2 version.
Looking at the changelog.Debian.gz file, I can see:
I'm second and confirming the bug on Ubuntu 8.10.
Firestarted still failing during the startup due the init order. It
starts before the wlan0 interface be created and, so, and error is
displayed. To add, it doesn't add itself to the Services as others
startup daemons.
Thanks!
Igor Gomes
--
Forget it... Wrong place.
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I just add that manual startup works for me. Firestarter just fails at
startup
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
I can confirm that the bug is still there in Gutsy.
Starting Firestarter firewall ... fail run-parts: /etc/network/if_up.d
50firestarter exited with return code 2
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug
Bug still present in Gutsy upgraded from Feisty. Somebody should care.
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Not fixed in Gutsy yet
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: firestarter (Debian)
Status: New = Fix Released
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
is this bug not fixed in gutsy? i heard that this bug was over and done wth.
what is this firestarter/debian bug? a duplicate? why isn't it confirmed?
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification
How much longer will we have to wait for the fix? This is still a
serious bug for us Feisty users.
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
I have the same problem (Starting the Firestarter firewall[failed]).
I have created the script in /etc/NetworkManager/dispatcher.d, made it
executable as Boris Maras proposed. However I still get the same message
when booting (well I have to do Ctrl+Alt+Backspace to see the message).
How do I
kilou:
You can run sudo /etc/init.d/firestarter status and it will tell you if it's
running or not.
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
** Changed in: firestarter (Ubuntu)
Assignee: Lionel Le Folgoc = (unassigned)
Status: Fix Committed = Fix Released
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of
** Changed in: firestarter (Debian)
Status: Unknown = Unconfirmed
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
** Bug watch added: Debian Bug tracker #417663
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417663
** Also affects: firestarter (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417663
Importance: Unknown
Status: Unknown
--
Firestarter init fails on system boot
Uploaded in gutsy, thanks for feedback. ;)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 20 May 2007 12:01:00 +0200
Source: firestarter
Binary: firestarter
Architecture: source
Version: 1.0.3-2ubuntu2
Distribution: gutsy
Urgency: low
Maintainer: Ubuntu MOTU Developers
On 16/05/07, Azalin [EMAIL PROTECTED] wrote:
Dear Dave,
so not to cloud the launchpad bug report with our conversation I
decided to mail you directly. I hope that is ok.
Yep no problem
In any case, what I mean with SOMEONE fix the problem is that someone
from Canonical or at least
Hi Dave,
dave s schreef:
In any case, what I mean with SOMEONE fix the problem is that someone
from Canonical or at least someone involved in maintaining Firestarter
should fix this problem.
Its worrying that this has been left out in the cold especially with a
fix sitting there.
I have to admit I had not thought of an update silently killing my
hack :) - In my books this is a VERY serious flaw and would have
thought it was #1 priority to be fixed. I only discovered I was
unprotected by accident was not best pleased.
I am a very green bug fixer, just setting up a KDE4
Dear Dave,
so not to cloud the launchpad bug report with our conversation I
decided to mail you directly. I hope that is ok.
In any case, what I mean with SOMEONE fix the problem is that someone
from Canonical or at least someone involved in maintaining Firestarter
should fix this problem.
As
@dave s: you migth run into problems again when firestarter is updated
... the script you edited migth be replaced... isn't better to add a
script like mentioned above to dispatcher of NetworkManager?
This problem indeed still persists in Feisty Fawn by the way... I urge
SOMEONE to do something
Hi,
this script seems to work fine on my Ubuntu 6.10. I upgraded it to 7.04
yesterday and it still works fine.
Hope you will have enough feedback to upload this patch for everyone.
Thanks
Boris Maras
Lionel Le Folgoc a écrit :
I've made a script based on the one from
Exactly the same problem as ChrisLasher earlier. WIFI not up when
firestarter script called - dangerous :(
My solution, edit /etc/firestarter ..
# *** Commented out by me otherwise firestarter wont start due to wifi not
started ***
#if [ $MASK = -a $1 != stop ]; then
# echo External
Opps - forgot to mention - fiesty fawn :)
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
** Changed in: firestarter (Ubuntu)
Assignee: (unassigned) = Lionel Le Folgoc
Status: Confirmed = In Progress
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of
I've made a script based on the one from debian-administration.org. Could you
test it? Copy it to /etc/NetworkManager/dispatcher.d and make it executable.
I'll upload it (and forward to Debian) if it works.
Thanks
** Attachment added: 50firestarter
same problem with feisty
:'(
--
Firestarter init fails on system boot when NetworkManager is used
https://bugs.launchpad.net/bugs/42759
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
** Changed in: firestarter (Ubuntu)
Status: Unconfirmed = Confirmed
--
Firestarter init fails on system boot when NetworkManager is used
https://launchpad.net/bugs/42759
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I think I have the same problem in feisty. The init script fails on
boot. Starting the GUI gives a eth0 not ready, failed to start
firestarter error. Strangely enough, disabling and enabling eth0 makes
firestarter start without problem.
sidenote: I use firestarter to share the internet connection
This problem persists in Feisty!
--
Firestarter init fails on system boot when NetworkManager is used
https://launchpad.net/bugs/42759
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I faced the same problem on my Ubuntu Edgy.
It has been a very serious issue for me, because I thought I was protected by
Firestarter. After installing Network Manager, it appears I wasn't at all.
I have several services (samba shares, ssh, vnc etc) that are supposed to be
accessible only by
** This bug has been flagged as a security issue
--
Firestarter init fails on system boot when NetworkManager is used
https://launchpad.net/bugs/42759
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
IMPORTANT NOTE
Manual running of the firestarter initscript works fine with Edgy Eft and
Network Manager. The initscript does not fail like mentioned in the bug
description, with Edgy Eft at least this doesn't happen. It just won't
start at boot.
Yes.. exactly what's happening to me.
--
Location of the dispatcher scripts changed in Edgy. They're now under:
/etc/NetworkManager/dispatcher.d
If you drop the script in there, it will run when (K)NetworkManager
connects.
--
Firestarter init fails on system boot when NetworkManager is used
https://launchpad.net/bugs/42759
--
As you could have read per my comment but better twice then no mention at all
;-)
Still, this should be fixed! Even though you can drop the script in
dispatcher.d this still should not happen, or at least a warning other then in
dmesg should be given... only when you examine your system logs
Oh ok I see..
On an unrelated problem, I got into package dependency problems last
night and decided to do a clean install. Anyways I'm no longer using
Firestarter so it's not an issue for me anymore.
Best of luck fixing it.
--
Firestarter init fails on system boot when NetworkManager is
I can confirm this bug is still not fixed in Edgy Eft. I use firestarter
version 1.0.3 and I have created a script in
/etc/NetworkManager/dispatcher.d that will launch firestarter upon NM
finding a network connection.
What disturbs me is that nobody seems to care about this problem, or at
least I
IMPORTANT NOTE
Manual running of the firestarter initscript works fine with Edgy Eft and
Network Manager. The initscript does not fail like mentioned in the bug
description, with Edgy Eft at least this doesn't happen. It just won't start at
boot.
--
Firestarter init fails on system boot when
Same problem, but I was able to solve it using the script posted here:
http://www.debian-administration.org/users/emeitner/weblog/2
I suggest calling the script
/usr/share/NetworkManager/dispatcher.d/50firestarter so it will launch
after the 01ifupdown script. Otherwise, it doesn't work. Of
I'm experiencing this same problem on Dapper Drake. So are others. See
http://ubuntuforums.org/showthread.php?p=1581628
--
Firestarter init fails on system boot when NetworkManager is used
https://launchpad.net/bugs/42759
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I suppose that wasn't the most helpful contribution to the bug above, sorry
about that--let me give a little more info. This is with ipw3945 (Intel
ProWireless 3945 ABG builtin module) seen as eth1. Happens on WEP, WPA, or
non-secure networks. Problem occurs because wireless is not up.
47 matches
Mail list logo
