Bug 851726

Summary:	s-c-f -
Product:	[Fedora] Fedora	Reporter:	Flóki Pálsson <flokip>
Component:	system-config-firewall	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	flokip, jpopelka, twoerner
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-28 10:52:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Flóki Pálsson 2012-08-24 20:36:39 UTC

Description of problem:
Can not start system-config-firewall. 


Version-Release number of selected component (if applicable):
system-config-firewall-1.2.29-8.fc18.noarch


How reproducible:
always 

Steps to Reproduce:
1.  start from terminal or menu
2.
3.
  
Actual results:

org.fedoraproject.slip.dbus.service.PolKit.NotAuthorizedException.org.fedoraproject.config.firewall.auth: 

Expected results:
s-c-f usable.

Additional info:

Comment 1 Fedora End Of Life 2013-04-03 17:54:59 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 2 Thomas Woerner 2013-11-06 19:46:40 UTC

This is not a system-config-firewall bug. You may be using a desktop environment or window manager without a policykit authentication agent. Most D-Bus mechanisms or services are not working without working policykit authentication.

Please try to use a polkit authentication agent like for example /usr/libexec/polkit-gnome-authentication-agent-1 or /usr/libexec/polkit-mate-authentication-agent-1

Comment 3 Flóki Pálsson 2013-12-26 20:31:09 UTC

ok now.
I can now use system-config-firewall.  
I have to stop 
# systemctl stop firewalld.service

Comment 4 Thomas Woerner 2014-03-28 10:52:08 UTC

You can either use the new firewall solution with firewalld or the old one with the ip*tables services and system-config-firewall/lokkit.

With system-config-firewall/lokkit your firewall is static, with firewalld you have integration for example with NetworkManager to use firewall zones per connection and also with libvirt to react on service restarts and reloads. The changes in the firewall are done dynamically with firewalld, the firewall gets modified and not recreated for all changes.

Closing as not a bug.