> On Sep 14, 2022, at 9:20 AM, Brian Foster wrote: > > 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?). It was a direct copy/paste. It appears that ‘gufw’ package installs /bin/gufw, which is identical to /usr/bin/gufw. Example from fresh ubuntu 20.04.04: ``` root@self:~# ls -l /bin/gufw ls: cannot access '/bin/gufw': No such file or directory root@self:~# apt-get -y install gufw Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: gufw 0 upgraded, 1 newly installed, 0 to remove and 26 not upgraded. Need to get 860 kB of archives. After this operation, 3539 kB of additional disk space will be used. Get:1 http://us-east-1.ec2.archive.ubuntu.com/ubuntu focal-updates/universe amd64 gufw all 20.04.1-1ubuntu1 [860 kB] Fetched 860 kB in 0s (23.2 MB/s) Selecting previously unselected package gufw. (Reading database ... 196134 files and directories currently installed.) Preparing to unpack .../gufw_20.04.1-1ubuntu1_all.deb ... Unpacking gufw (20.04.1-1ubuntu1) ... Setting up gufw (20.04.1-1ubuntu1) ... Processing triggers for desktop-file-utils (0.24-1ubuntu3) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for man-db (2.9.1-1) ... root@self:~# ls -l /bin/gufw -rwxr-xr-x 1 root root 196 Nov 7 2019 /bin/gufw root@self:~# ls -l /usr/bin/gufw -rwxr-xr-x 1 root root 196 Nov 7 2019 /usr/bin/gufw root@self:~# dpkg -S bin/gufw gufw: /usr/bin/gufw gufw: /usr/bin/gufw-pkexec ``` > 2nd, Line 2 of /usr/bin/gufw does not (directly) contain any "["s: > > 2.1$ $ nl -ba /usr/bin/gufw > 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/ld-linux-x86-64.so.2, BuildID[sha1]=a18184f5d26fce82fe5ccf842d3cf7b9c729030f, for GNU/Linux 3.2.0, stripped > > 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 Thank you for the debugging hint. It appears the ’too many arguments’ error is caused by the startup script not being able to handle situation if loginctl reports more than one session matching the same username, which is virtually guaranteed when the X11 session is accessed via xrdp. Please see the following: ``` agent@self:~$ bash -x $(which gufw) +++ loginctl ++++ whoami +++ grep agent +++ awk '{print $1}' ++ loginctl show-session c1 c2 -p Type + '[' Type=x11 Type=x11 = Type=wayland ']' /bin/gufw: line 2: [: too many arguments ++ whoami + c_user=agent + pkexec gufw-pkexec agent Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused (gufw.py:32911): Gdk-CRITICAL **: 13:55:22.936: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed […] (gufw.py:32911): Gtk-CRITICAL **: 13:55:22.938: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed /bin/gufw-pkexec: line 10: 32911 Segmentation fault (core dumped) python3 ${LOCATIONS[${i}]} $1 ``` And here is the output of loginctl: ``` agent@self:~$ loginctl SESSION UID USER SEAT TTY c1 1000 agent c2 1000 agent 2 sessions listed. ``` Now, even with that being solved by passing loginctl/awk via `head -1`, the issue persists, and appears to be solvable only by adjusting the pkexec policy. See the output: ``` agent@self:~$ bash -x $(which gufw) +++ loginctl +++ awk '{print $1}' ++++ whoami +++ grep agent +++ head -1 ++ loginctl show-session c1 -p Type + '[' Type=x11 = Type=wayland ']' ++ whoami + c_user=agent + pkexec gufw-pkexec agent Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.369: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.369: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.369: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.370: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.370: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.370: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.370: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.370: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.370: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.370: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.370: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.370: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gdk-CRITICAL **: 14:13:30.370: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.370: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.371: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.371: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed (gufw.py:33382): Gtk-CRITICAL **: 14:13:30.371: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed /bin/gufw-pkexec: line 10: 33382 Segmentation fault (core dumped) python3 ${LOCATIONS[${i}]} $1 ``` Granted, this may be an issue specific to running gufw in an X11 environment via xrdp, but this is the only piece of software we’ve encountered that behaves this way. We run thousands of vms via xrdp, based on Ubuntu 14/16/18/20, and this is the only software that’s given us any trouble. Like I mentioned above, the only reliable fix seems to be providing the correct and full path to the executable in the polkit policy. Thank you for your assistance.