Gufw was working (xorg only, not under Wayland) until today. Today, I
did a large update of multiple packages - about 240 Mb worth. After
that Gufw no longer starts.
When gufw icon is clicked, the authentication window pops up as usual,
requesting the user password. When entered incorrectly, the window
just says incorrect, try again. When entered correctly, the
authentication window disappears, and nothing further happens.
Same behavior using Linux, Linux-lts, and Linux-grsec kernels.
Note: Gufw always started correctly under xorg (chosen at GDM login).
Gufw has never worked, just displayed the symptoms stated above, under
Wayland (chosen at GDM login).
Since the update today involved many packages, I don't know which
one(s) are the culprit(s). The updated packages seemed to be mainly
about GTK and Python. All dependencies seem okay, and I did remove and
reinstall Gufw. Same results. (Python-gobject is intalled and up to
I searched online, in the wiki, in the forums, and in the Arch bug
reports, all to no avail. I did come across some old reports of
similar problems, possibly where GTK was responsible.
Ufw is and has been working fine, enabled and autostarted under systemd.
I can't see anything suspect in dmesg or journalctl, but might not
recognize it if I did.
machine is UEFI-capable, but using bios (MBR).
1 root partition (EXT4)
1 swap partition
Contents of /var/log/gufw.log:
[12/29/2016 10:47:41 PM] /usr/sbin/ufw --force delete 1
[12/29/2016 10:47:32 PM] /usr/sbin/ufw --force delete 2
[12/29/2016 10:46:15 PM] /usr/sbin/ufw deny in proto tcp from any to any port 23
[10/31/2016 09:41:17 PM] Confirm Delete Dialog: Enabled
I don't have 6 months to learn to use ufw without a gui.
Any magic solution?
If not - I'm so disgusted with ufw on Arch - can I just remove gufw,
ufw, and ufw from systemctl, and then install firewalld. If so, will
the existing iptables configuration be overwritten automatically, or
would it have to be somehow purged manually?
Note: I have not filed a bug report yet. I wanted to see if it was
really a bug, or a PEBKAC error.