Description of problem: When FirewallD returns a D-Bus error, it does so using a Python specific D-Bus type. Actual results: org.freedesktop.DBus.Python.dbus.exceptions.DBusException: INVALID_ZONE: lksflkds Expected results: org.freedesktop.FirewallD.Error: INVALID_ZONE: lksflkds or org.freedesktop.FirewallD.InvalidZone: lksflkds or ... Additional info: An example from NetworkManager: org.freedesktop.NetworkManager.UnknownDevice: No device found for the requested iface.
Fixed in firewalld.git: https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=bac3d4ac75c746cd497a9455003ba9bfcabbc806
After reading more about reporting D-Bus errors, I think that FirewallD is diverging a bit in this area. Is there a reason to use just one D-Bus error name, e.g. "org.fedoraproject.FirewallD1.Error", and then differentiating the specific errors by using an extra field, e.g. "INVALID_ZONE"? The D-Bus specification at http://dbus.freedesktop.org/doc/dbus-specification.html says the following: ------------ Error names have the same restrictions as interface names. Error names have the same naming conventions as interface names, and often contain .Error.; for instance, the owner of example.com might define the errors com.example.MusicPlayer.Error.FileNotFound and com.example.MusicPlayer.Error.OutOfMemory. The errors defined by D-Bus itself, such as org.freedesktop.DBus.Error.Failed, follow a similar pattern. ------------ Event the GlibMM/Gio API expects that the application will conform to this by providing a call to return D-Bus errors which accepts just an error name in the form "foo.bar.domain.SpecificError" and a error message.
firewalld-0.3.12-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/firewalld-0.3.12-1.fc21
firewalld-0.3.12-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/firewalld-0.3.12-1.fc20
Package firewalld-0.3.12-1.fc21: * should fix your issue, * was pushed to the Fedora 21 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.12-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-12912/firewalld-0.3.12-1.fc21 then log in and leave karma (feedback).
firewalld-0.3.12-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
firewalld-0.3.12-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.