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:
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
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
ok now. I can now use system-config-firewall. I have to stop # systemctl stop firewalld.service
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.