Bug 805298 - Newly installed F16 - cannot configure Firewall - permission problems
Newly installed F16 - cannot configure Firewall - permission problems
Product: Fedora
Classification: Fedora
Component: system-config-firewall (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Thomas Woerner
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-03-20 16:15 EDT by Bob Gustafson
Modified: 2013-02-13 18:58 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 18:57:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bob Gustafson 2012-03-20 16:15:19 EDT
Description of problem:

  I went to Applications->Other->Firewall to open up the network access to this particular system (usb printer is connected - need to print from another system..)

It gave me an error:


  and two choices - redo, and quit.

Version-Release number of selected component (if applicable):

 Newly installed F16 system from scratch, all updates done as of this date.

How reproducible:


Steps to Reproduce:
1. Install new F16 system - not update, but install.
2. Click on Applications->Other->Firewall
3. Try to change configuration
Actual results:

 Error as previously noted

Expected results:

 I should be able to change my firewall settings.

Additional info:
Comment 1 Thomas Woerner 2012-04-19 04:07:08 EDT
Reassigning to the proper component: system-config-firewall.
Comment 2 Thomas Woerner 2012-04-19 04:08:06 EDT
Please verify if this is a SELinux problem by setting SELinux in permissive mode with "setenforce 0".
Comment 3 Dave 2012-09-16 15:24:53 EDT
I have the same problem with a fresh install of Fedora 17.  I need to to be root to make system-config-firewall work.

I have completely disabled SELinux.
Comment 4 Bob Gustafson 2012-09-19 13:37:32 EDT
I now am running Fedora 17 and the Firewall Configuration seems to work fine.

The authentication required is my own password (I have administrative privileges).

I am running with SELinux enabled and enforcing and targeted.
Comment 5 Fedora End Of Life 2013-01-16 15:33:24 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 6 Fedora End Of Life 2013-02-13 18:58:06 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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