ufw and gufw out of order

[raymond]

Hello,

the sudo ufw status command gives:

WARN: / is writable for everyone!
WARN: / is writable for the group!

and nothing else in the "flag" page of gufw. the "ufw" activity normally appears here!

with "gufw" can not enable or disable "ufw".
for that I have to use sudo ufw cds and enable or disable or status ...

finally the comparison of the screen "gufw" with the result of the cdes gives results totally reversed !!!

after complete désisntallation then reinstallation the result is always the same. it is to understand nothing more.

i have two screenshots that highlight this malfunction but i do not know how to attach them to this message ...

thanks for the help expected.

greetings.

Ray.

then, after

here is the result of the order: sudo systemctl status ufw.service

● ufw.service - Uncomplicated firewall
    Loaded: /lib/systemd/system/ufw.service; enabled; vendor preset: enabled
    Active: active (exited) since Fri 2018-08-03 13:39:12 CEST; 21min ago
   Process: 250 ExecStart = / lib / ufw / ufw-init start quiet (code = exited, status = 0 / SUCCESS)
Main PID: 250 (code = exited, status = 0 / SUCCESS)
    CGroup: /system.slice/ufw.service

August 03 13:39:12 ac2i-W240EU-W250EUQ-W270EUQ systemd [1]: Started Uncomplicated firewall.
Warning: Journal has been rotated since it was started. Log output is incomplete or unavailable.

also, after

Re,

actually but the operation via the gufw interface gives weird results.
you can see the 2 screens images obtained thanks to the ufw cdes and the gufw screen ...
here is the direct link for access to the shared folder: https://app.box.com/s/3q29ca27oebk788xqxlbjy2z4vd6idl6
why say ufw is useless? faced with these problems I tried to install "firestarter" without result ...
I think a firewall is a necessary evil nowadays. thank you.

[costales (costales)]

This is an ufw issue. I'll derivate to that project.

[Jamie Strandboge (jdstrand)]

Your '/' directory does not have proper ownership. You should run 'sudo chown root:root /' to resolve this. Before you do, you might want to investigate why the permissions are wrong.