Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57255 - [firewalld] Since upgrade to 0.5.0 failing to apply rules

Attached to Project: Community Packages
Opened by Deactivated account (TechnicalTotoro) - Sunday, 28 January 2018, 13:43 GMT
Last edited by Maxime Gauduin (Alucryd) - Monday, 29 January 2018, 21:34 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Since I upgraded firewalld on my up-to-date Arch Linux system from 0.4.4.6-1 -> 0.5.0-1 I have noticed that I get the following error on every startup:

1月 28 13:13:05 <computerName> systemd[1]: Starting firewalld - dynamic firewall daemon...
1月 28 13:13:06 <computerName> systemd[1]: Started firewalld - dynamic firewall daemon.
1月 28 13:13:08 <computerName> firewalld[4737]: ERROR: Failed to apply rules. A firewall reload might solve the issue if the firewall has been modified using
1月 28 13:13:08 <computerName> firewalld[4737]: ERROR: set_rule() missing 1 required positional argument: 'log_denied'
1月 28 13:13:08 <computerName> firewalld[4737]: ERROR: Failed to apply rules. A firewall reload might solve the issue if the firewall has been modified using
1月 28 13:13:08 <computerName> firewalld[4737]: ERROR: set_rule() missing 1 required positional argument: 'log_denied'

I have tried restarting and reloading firewalld.service through systemctl, but the same error is just given again. I have not changed any of the rules or done anything with it, all that I have done is upgrade the version. systemctl status reports that it is running and active, but this concerns me very much to what degree it is actually protecting me as it is unclear how deeply this error affects it. The only real configuring that I have done with the firewall is to set the zone to public.

I ran firewalld in debug mode level 10 and I have attached the output that I got. You can probably search for the "^C" to see where I cancelled it.
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Monday, 29 January 2018, 21:34 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.5.0-2
Comment by Maxime Gauduin (Alucryd) - Monday, 29 January 2018, 18:32 GMT
Confirmed, associated upstream issue: https://github.com/firewalld/firewalld/issues/287

Loading...