Cannot edit rules after toggling OFF/ON

Bug #1956171 reported by Hump Tee
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

After clicking off the Firewall(Status) and then clicking it back on,
The Names of all the rules are missing (blank)
If I try to edit any one of them I get;

Immutable Rule
You can't edit a rule added from ufw

I'm having to re-enter all the rules from scratch, just so I can get the names in. And I must remember not to ever turn off the Status.

Revision history for this message
costales (costales) wrote : Re: [Bug 1956171] [NEW] Cannot edit rules after toggling OFF/ON

Hi, it should work, gufw uses a database for check when a rule is from ufw
or gufw. Could you run gufw from the shell and check if there is any dump?
Best regards

Revision history for this message
Hump Tee (humpty) wrote :

The msgs I get at start up is;

ls: cannot access '/usr/lib/python*/site-packages/gufw/': No such file or directory

( GLib-GIO-CRITICAL **: 23:32:16.520: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
 (above message displays 10 times)

It is definitely the Status toggle that is resetting the profile.

Before: toggle is ON
root:/etc/gufw> ls -l Home.profile
 -rw------- 1 root root 577 Jan 10 00:11 Home.profile

After: toggle is OFF
root:/etc/gufw> ls -l Home.profile
 -rw------- 1 root root 80 Jan 10 00:26 Home.profile

When the toggle is next switched to ON, the profile has no rules,
so gufw load the rules from UFW (which are un-editable)

Workaround is to save the profile while toggle is ON;
root:/etc/gufw> cp Home.profile Saved

And to overwrite it just before the next toggle to ON;
root:/etc/gufw> cp Saved Home.profile

( I'm using gufw_20.04.1-1 Lubuntu 20.04.02 (with fix_9 patch). )

Revision history for this message
John Ross (johnross-johnross) wrote :

I can confirm this bug on xubuntu 20.04.4 LTS and GUFW 20.04.1.

Revision history for this message
ananke (ananke) wrote :

We began evaluating gufw for a project, and came across the same issue. I'm a bit baffled by the current design, why would enabling/disabling state of a firewall result in complete wipe of the configuration file? What's the goal here?

As it stands, this is fundamentally broken by design.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers