[SOLVED] guwf refueses to start

[gg22LM]

Hi I have a problem with Linux Mint 19 and gufw:

If I start gufw from the GUI It just goes away after the password - no error
Here I call it inside an CLI :
~$ gufw
Traceback (most recent call last):
File "/usr/share/gufw/gufw/gufw.py", line 30, in <module>
gufw = Gufw(controler.get_frontend())
File "/usr/share/gufw/gufw/gufw/view/gufw.py", line 80, in __init__
self._set_initial_values()
File "/usr/share/gufw/gufw/gufw/view/gufw.py", line 285, in _set_initial_values
self.add_to_log(self.fw.get_log(), self.GRAY, False)
File "/usr/share/gufw/gufw/gufw/model/frontend.py", line 99, in get_log
return self.firewall.get_log()
File "/usr/share/gufw/gufw/gufw/model/firewall.py", line 222, in get_log
return self.backend.get_log()
File "/usr/share/gufw/gufw/gufw/model/ufw_backend.py", line 344, in get_log
cmd = self._run_cmd(['cat', self.GUFW_LOG])
File "/usr/share/gufw/gufw/gufw/model/ufw_backend.py", line 47, in _run_cmd
return stdout.decode('utf-8')
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf8 in position 25: invalid start byte

I have both a Danish keyboard and an UK - I get the samme error

I have tried an complete uninstall and afterwards a reinstall : no change

Can you help me ?

Kind regards gg22LM

[thx-1138]

...does it start with pkexec gufw?

[gm10]

Try

Code: Select all

sudo mv /var/log/gufw.log /var/log/gufw.log.bak

gufw should load now. Now toggle the firewall off and on again, close gufw, then see if you can reopen it or if the error occurs again.

[gg22LM]

ThankYou very much for your help !!

sudo mv /var/log/gufw.log /var/log/gufw.log.bak

worked fine

Once again thank you to all, who helped me

[Faust]

...does it start with pkexec gufw?

Not for me it doesn't .

I'm keeping Mint 19 as a side project until I get it "house-trained" , especially given some of the other recent headaches ...
viewtopic.php?f=46&t=272665

...... and then trying to get used to NOT typing "gksudo" anymore .

"gufw" works fine now from terminal ..... as to the reason ? .... for me that's in the "DFK/DFC" category .

@gm10
many thanks for the move command you posted ..... " Nice one centurion " -

[gm10]

@gm10
many thanks for the move command you posted ..... " Nice one centurion " -

He posted the stack trace so it was no problem to quickly check out that source code. The issue was the code was choking on decoding the log file. I just moved the offending log file out of the way, but this doesn't solve the problem of why it went bad in the first place. But unless it happens again no real reason to go investigate I guess - DFK/DFC very much indeed.

[thx-1138]

...does it start with pkexec gufw?

Not for me it doesn't .

Blocked (for having an attitude).

...exactly the kind of detailed bug report & in-depth analysis that i'm interested in.
Good to notify me explicitly of such - and furthermore informing the rest of us for your 'house-trained' Mint 19...
as i couldn't sleep the whole night yesterday not further knowing such (how was that for the useless information of the day?)

Definition of...dfkdfc
(see, i learn something useful everyday around, even if it's just slang...)

[Faust]

He posted the stack trace so it was no problem to quickly check out that source code. The issue was the code was choking on decoding the log file. I just moved the offending log file out of the way, but this doesn't solve the problem of why it went bad in the first place. But unless it happens again no real reason to go investigate I guess - DFK/DFC very much indeed.

Yes indeed ... curious .

I've been running two Mint 19 installs for a couple of weeks .... the main reason I read this topic in the first place
The first was a clean install from Live USB to a spare HDD , and that's the one that had the "gufw" problem .

The second was an upgrade using a clone of a rock-solid 18.3 system ,
and it had the widely-reported "failed to install GRUB" issue , but once fixed it did not have the "gufw" problem .

Might be a whiff of a clue to anyone wanting to track this down ?

[gm10]

Might be a whiff of a clue to anyone wanting to track this down ?

No idea, didn't run into the problem myself yet, but if you attach the problematic log file (the actual file, not just the contents) we can take a look.