Description of problem: When I try to start firewall-config I get a popup dialog that says: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.9 was not provided by any .service files Version-Release number of selected component (if applicable): 0.2.11-2.fc18 How reproducible: 100% Steps to Reproduce: 1. at a shell prompt: firewall-config 2. observe dialog Actual results: Above described error. Expected results: Firewall configuration tool starts up. Additional info: If I simply restart firewalld: # service firewalld restart Redirecting to /bin/systemctl restart firewalld.service I can click Retry on the dialog and it works again.
Is this an updated system (from F-17 or earlier)? If yes, you have to enable the firewalld service manually with systemctl enable firewalld.service.
I'm pretty sure I've seen this error and needed to restart this service more than once during a single "boot" session. That would preclude the cause being that the service is not enabled, wouldn't it? I mean once I have done a "service firewalld restart" once after a boot that should be it, (assuming the service is actually not enabled), wouldn't it? Currently systemctl says about firewalld on my system: # systemctl status firewalld.service firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled) Active: active (running) since Mon, 2013-01-14 08:10:22 EST; 1h 55min ago Main PID: 20550 (firewalld) CGroup: name=systemd:/system/firewalld.service └ 20550 /usr/bin/python -Es /usr/sbin/firewalld --nofork Jan 14 08:10:22 brian-laptop systemd[1]: Started firewalld - dynamic firewall daemon. Haven't really become proficient with systemd yet but doesn't the "enabled" on the second line mean that the system is enabled at boot time? i.e. in the state you asked me to put it into with "systemctl enable firewalld.service" already?
(In reply to comment #2) > Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled) > > Haven't really become proficient with systemd yet but doesn't the "enabled" > on the second line mean that the system is enabled at boot time? Yes, it seems that firewalld service is enabled, i.e. planned to be started during boot. But from your description it looks like it actually doesn't start - and we need more information to know why. What's the 'systemctl status firewalld.service' output after you boot ? Do you see any valuable info in /var/log/messages or /var/log/firewalld after boot ?
(In reply to comment #3) > > Yes, it seems that firewalld service is enabled, i.e. planned to be started > during boot. But from your description it looks like it actually doesn't > start - and we need more information to know why. Or it starts and dies. Or it starts and just doesn't respond to firewall-config's DBus inquiry (i.e. deadlocks or goes AWOL for some other reason). I didn't check that it was in fact running before I did the "service firewalld restart" though. I will next time. > What's the 'systemctl status firewalld.service' output after you boot ? Unknown, at this point. Can't really just reboot right now to check. To much other stuff going on that a reboot would disrupt. > Do you see any valuable info in /var/log/messages or Unknown at this time. > /var/log/firewalld > after boot ? Current contents of that file currently are: 2012-12-17 16:18:04 WARNING: Ignoring deprecated attribute name='public' 2012-12-17 16:18:14 WARNING: Ignoring deprecated attribute name='public' 2012-12-20 10:56:28 WARNING: KeyboardInterrupt in run_server 2012-12-20 10:56:30 WARNING: Ignoring deprecated attribute name='public' 2012-12-20 10:56:30 ERROR: Failed to load zone file '/etc/firewalld/zones/public.xml': 2012-12-24 11:28:56 FATAL ERROR: Not starting FirewallD, already running. 2012-12-24 11:30:03 WARNING: KeyboardInterrupt in run_server 2012-12-24 11:30:06 WARNING: Ignoring deprecated attribute name='public' 2012-12-24 11:30:06 ERROR: Failed to load zone file '/etc/firewalld/zones/public.xml': 2013-01-05 22:23:20 WARNING: KeyboardInterrupt in run_server 2013-01-05 22:23:23 WARNING: Ignoring deprecated attribute name='public' 2013-01-05 22:23:23 ERROR: Failed to load zone file '/etc/firewalld/zones/public.xml': 2013-01-07 15:43:02 FATAL ERROR: Not starting FirewallD, already running. 2013-01-07 15:43:23 WARNING: KeyboardInterrupt in run_server 2013-01-07 15:43:26 WARNING: Ignoring deprecated attribute name='public' 2013-01-07 15:43:26 ERROR: Failed to load zone file '/etc/firewalld/zones/public.xml': 2013-01-07 16:32:22 WARNING: KeyboardInterrupt in run_server 2013-01-14 08:10:20 WARNING: KeyboardInterrupt in run_server
I have this on a freshly installed Fedora 18 system: $ systemctl status firewalld.service firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled) Active: active (running) since Fri 2013-02-01 15:41:57 EST; 2 days ago Main PID: 19224 (firewalld) CGroup: name=systemd:/system/firewalld.service └─19224 /usr/bin/python /usr/sbin/firewalld --nofork $ firewall-cmd --state Error: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.913 was not provided by any .service files :(
Can you attach (using 'Add an attachment' link above) /var/log/firewalld ?
(In reply to comment #6) > Can you attach (using 'Add an attachment' link above) /var/log/firewalld ? $ cat /var/log/firewalld 2013-01-19 05:06:51 WARNING: KeyboardInterrupt in run_server $
Have you restarted the polkit service? This results in a problem like this.
(In reply to comment #8) > Have you restarted the polkit service? This results in a problem like this. I can only speak for myself, but I most certainly have not restarted the polkit service.
(In reply to comment #8) > Have you restarted the polkit service? This results in a problem like this. Sorry for my slow reply if this was intended for me. I too have not ever personally restarted the polkit service. What systemd does on it's own however is anyone's guess.
*** Bug 887119 has been marked as a duplicate of this bug. ***
Summary reproducer: systemctl restart polkit.service work-around: systemctl restart firewalld.service
*** Bug 920019 has been marked as a duplicate of this bug. ***
*** Bug 928046 has been marked as a duplicate of this bug. ***
Seems to be fixed with python-slip-0.4.0-1.fc18
python-slip-0.4.0-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-4221/python-slip-0.4.0-1.fc18
python-slip-0.4.0-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.