What I am seeing seems to be a state change that happens at boot time,
so I can't capture it in gufw cli. I have filed
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1914816
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could you run gufw on terminal and put here the dump? thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914606
Title:
Wiping .cache makes gufw fail, cuts network access ?
To manage
I guess I can't close this issue myself, so please close it for me.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914606
Title:
Wiping .cache makes gufw fail, cuts network access ?
To
Okay, now I'm convinced my problems have nothing to do with ~/.cache, so
I'm closing this issue. But I'm still having gufw show "disabled" after
a reboot. When it happens, is that just reacting to some change that
ufw made to the iptables ? Such as setting the INPUT chain to empty ?
I think
Maybe ufw stores something important in ~/.cache ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914606
Title:
Wiping .cache makes gufw fail, cuts network access ?
To manage notifications about
No, it only sends commands to ufw
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914606
Title:
Wiping .cache makes gufw fail, cuts network access ?
To manage notifications about this bug go to:
Could it be something used by gufw ? Firewalld or iptables or something
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914606
Title:
Wiping .cache makes gufw fail, cuts network access ?
To
