Description of problem: My general intention was to enable x11vnc server in the firewalld.service. I used the GUI application and tried to create an advanced rule: ip v4 only Service: vnc-service Action: Accept Source: 192.168.2.0/24 Log: INFO level with [VNC] prefix When I entered all the things and pressed OK nothing actually happened. No new rule was seen in the GUI and after some seconds I saw the failure notification. PS: Currently I use Russian (RU_ru) locale. I am not sure but it might be essential for the bug. Version-Release number of selected component: firewall-config-0.3.9.3-1.fc20 Additional info: reporter: libreport-2.1.12 cmdline: /usr/bin/python -Es /usr/bin/firewall-config executable: /usr/bin/firewall-config kernel: 3.13.3-201.fc20.x86_64 runlevel: N 5 type: Python uid: 500 Truncated backtrace: firewall-config:1445:_add_rich_rule:UnicodeDecodeError: 'ascii' codec can't decode byte 0xd1 in position 0: ordinal not in range(128) Traceback (most recent call last): File "/usr/bin/firewall-config", line 1891, in onChangeZone self._add_rich_rule(rule) File "/usr/bin/firewall-config", line 1445, in _add_rich_rule elem = _("service") + "\n" + obj.element.name UnicodeDecodeError: 'ascii' codec can't decode byte 0xd1 in position 0: ordinal not in range(128) Local variables in innermost frame: audit: '' src: u'192.168.2.0/24' obj: <firewall.core.rich.Rich_Rule object at 0x2fc4c50> log: '' family: u'ipv4' dest: '' self: <__main__.FirewallConfig object at 0x2885d90> elem: '' action: ''
Created attachment 866482 [details] File: backtrace
Created attachment 866483 [details] File: environ
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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.
firewalld-0.3.14.2-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/firewalld-0.3.14.2-1.fc20
Package firewalld-0.3.14.2-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing firewalld-0.3.14.2-2.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-10265/firewalld-0.3.14.2-2.fc20 then log in and leave karma (feedback).
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.