Guarddog doesn't start - missing /etc/rc.firewall

Bug #74598 reported by Fabián Rodríguez
4
Affects Status Importance Assigned to Milestone
guarddog (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When installing Guarddog, automatic startup fails. Complete output:

magicfab@suzy:~$ sudo apt-get install guarddog
Password:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  gawk
The following NEW packages will be installed:
  gawk guarddog
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 954kB of archives.
After unpacking, 3445kB of additional disk space will be used.
Do you want to continue [Y/n]?
Get:1 http://us.archive.ubuntu.com edgy/main gawk 1:3.1.5.dfsg-4 [466kB]
Get:2 http://us.archive.ubuntu.com edgy/universe guarddog 2.5.0-1ubuntu1 [488kB]
Fetched 954kB in 13s (70.3kB/s)
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Selecting previously deselected package gawk.
(Reading database ... 114446 files and directories currently installed.)
Unpacking gawk (from .../gawk_1%3a3.1.5.dfsg-4_i386.deb) ...
Selecting previously deselected package guarddog.
Unpacking guarddog (from .../guarddog_2.5.0-1ubuntu1_i386.deb) ...
Setting up gawk (3.1.5.dfsg-4) ...

Setting up guarddog (2.5.0-1ubuntu1) ...
Unable to start guarddog firewall - /etc/rc.firewall does not exist

Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

I am not able to reproduce this issue in gutsy.

Changed in guarddog:
status: New → Incomplete
Revision history for this message
bobrownik (tolive-is-todie) wrote :

im using gutsy tribe5+updates, this is still the issue,
but guarddog can be started up from KDE,

the first message that comes up says that its ok if rc.firewall is missing because the guarddog hasn't been configured yet,

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

Same issue in Gutsy. Actually bobrownik is correct, the message indicates a problem that will be solved when guarddog is first invoked. This is mostly a usability issue, IMO.

Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Hardy Heron. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/

Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in guarddog:
status: Incomplete → Invalid
Revision history for this message
François (francois-letendre) wrote :

Same issue in Jaunty.

Everything is nicely explained after the first run of guarddog,
found in Applications - Internet (KDE 4)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.