What happens if you run gufw using the bash(1) shell's -x option? I get:
2.3$ $ bash -x $(which gufw)
++ whoami
+ c_user=USER
+ pkexec gufw-pkexec USER
Error executing command as another user: Not authorized
This incident has been reported.
where USER is my username. The "not authorized" is because I cancelled rather than enter my password (for this test, for other tests I entered the password and gufw itself started entirely as expected).
Running Kubuntu 22.04.1 LTS, I do *not* have this issue; gufw(8) v22.04.0 starts up properly.
I find the initial output line in the above odd:
/bin/gufw: line 2: [: too many arguments
1st, gufw is in /usr/bin, not /bin (this *may* be a copy-paste mistake?).
2nd, Line 2 of /usr/bin/gufw does not (directly) contain any "["s:
2.1$ $ nl -ba /usr/bin/gufw ld-linux- x86-64. so.2, BuildID[ sha1]=a18184f5d 26fce82fe5ccf84 2d3cf7b9c729030 f, for GNU/Linux 3.2.0, stripped
1 #!/bin/bash
2 c_user=$(whoami)
3 pkexec gufw-pkexec $c_user
2.2$ file $(which whoami)
/usr/bin/whoami: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/
What happens if you run gufw using the bash(1) shell's -x option? I get:
2.3$ $ bash -x $(which gufw)
++ whoami
+ c_user=USER
+ pkexec gufw-pkexec USER
Error executing command as another user: Not authorized
This incident has been reported.
where USER is my username. The "not authorized" is because I cancelled rather than enter my password (for this test, for other tests I entered the password and gufw itself started entirely as expected).