Open Captain-Barge opened 4 months ago
@Captain-Barge The logs for GUI is at ~/.local/share/gpclient/gpclient.log
, can you provide it? So I can investigate why it 'crashes'.
The root privilege is required, even though the GUI relies on a service running as root in the background. By leveraging https://polkit.pages.freedesktop.org/polkit/
I cannot get the CLI to run as root because I see the error: Error: Command { std: "/usr/bin/gpauth ........ cannot be run as root
@bagnaram Can you run it with the -E
option, e.g., sudo -E gpclient connect <portal> ...
and see what happens?
Describe the bug I can't connect without running
gpclient
as root. (This means that the GUI launched via desktop integration doesn't work).Expected behavior The GUI launched via normal desktop integration seems to connect but then mysteriously 'crashes' immediately and without explanation. Connecting from the terminal with
gpclient --ignore-tls-errors --fix-openssl connect vpn.domain.com:123 -u username@domain.com
accepts password & 2FA and seems to connect fine but then immediately closes and the console messages conclude with:The "openconnect must be running as root" messages motivated me to try again with sudo:
sudo gpclient --ignore-tls-errors --fix-openssl connect vpn.domain.com:123 -u username@domain.com
. This worked. The VPN connection established without issues and appears to be stable.Environment:
ps aux | grep 'gnome-keyring\|kwalletd5' | grep -v grep
:username 1431 0.0 0.0 239908 11880 ? SLsl 10:12 0:00 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring
gpclient --version
givesgpclient 2.3.4 (2024-07-08)
Additional context As already stated, running with
sudo
is a good workaround. But it would be convenient if it wasn't required.