Description of problem: Was attempting to fix email problems by fixing various network issues (dns lookups etc.). Changed between the "home" and "public" zones (while working on "persistent" configuration) and attempted to reload this, whereupon an error was raised. The Firewall Configuration tool appears to continue running. Version-Release number of selected component: firewall-config-0.2.12-4.fc18 Additional info: cmdline: /usr/bin/python /usr/bin/firewall-config executable: /usr/bin/firewall-config kernel: 3.8.4-202.fc18.x86_64 uid: 1002 Truncated backtrace: connection.py:651:call_blocking:DBusException: org.freedesktop.DBus.Python.dbus.exceptions.DBusException: COMMAND_FAILED: '/sbin/iptables -N ACCEPT -t filter' failed: iptables v1.4.16.2: chain name may not clash with target name Try `iptables -h' or 'iptables --help' for more information. Traceback (most recent call last): File "/usr/bin/firewall-config", line 809, in onReloadFirewalld self.fw.reload() File "<string>", line 2, in reload File "/usr/lib/python2.7/site-packages/slip/dbus/polkit.py", line 141, in _enable_proxy return func(*p, **k) File "/usr/lib/python2.7/site-packages/firewall/client.py", line 638, in reload self.fw.reload() File "/usr/lib/python2.7/site-packages/slip/dbus/proxies.py", line 50, in __call__ return dbus.proxies._ProxyMethod.__call__(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) DBusException: org.freedesktop.DBus.Python.dbus.exceptions.DBusException: COMMAND_FAILED: '/sbin/iptables -N ACCEPT -t filter' failed: iptables v1.4.16.2: chain name may not clash with target name Try `iptables -h' or 'iptables --help' for more information. Local variables in innermost frame: byte_arrays: False self: <dbus._dbus.SystemBus (system) at 0x2606710> args: () object_path: '/org/fedoraproject/FirewallD1' signature: '' bus_name: dbus.UTF8String(':1.8') get_args_opts: {'byte_arrays': False, 'utf8_strings': False} timeout: 2147483.647 kwargs: {} dbus_interface: 'org.fedoraproject.FirewallD1' message: <dbus.lowlevel.MethodCallMessage path: /org/fedoraproject/FirewallD1, iface: org.fedoraproject.FirewallD1, member: reload dest: :1.8> method: 'reload'
Created attachment 716092 [details] File: backtrace
Created attachment 716093 [details] File: core_backtrace
Created attachment 716094 [details] File: dso_list
Created attachment 716095 [details] File: environ
(In reply to comment #0) > '/sbin/iptables -N ACCEPT -t filter' failed: iptables v1.4.16.2: chain name > may not clash with target name No idea where it came from. If you manage to reproduce it and have some steps to reproduce let me know. Thank you.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.