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!
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!
FS#58165 - [ferm] Systemd service failing at boot
Attached to Project:
Community Packages
Opened by Infanta Xavier (xavier83) - Sunday, 08 April 2018, 08:49 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 17 April 2018, 22:44 GMT
Opened by Infanta Xavier (xavier83) - Sunday, 08 April 2018, 08:49 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 17 April 2018, 22:44 GMT
|
DetailsDescription:
Reboot the system with ferm.service enabled. The service fails to start Additional info: * ferm 2.4.1 * linux 4.15.15-1 * systemd 238 Steps to reproduce: Reboot the system with ferm.service enabled Following error log appears. ferm[858]: Another app is currently holding the xtables lock. Perhaps you want to use the -w option? ferm[858]: Failed to run /sbin/iptables-restore ferm.service: Main process exited, code=exited, status=4/NOPERMISSION ferm.service: Failed with result 'exit-code'. systemd[1]: Failed to start for Easy Rule Making. |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Tuesday, 17 April 2018, 22:44 GMT
Reason for closing: Not a bug
Tuesday, 17 April 2018, 22:44 GMT
Reason for closing: Not a bug