GlobalProtect vpn client will not connect

[blissjoe]

Qubes OS version:

Qubes release 4.0 (R4.0)

Affected component(s):

Debian 9 and Fedora 28 template
StandaloneVM based on Fedora 28 template
GlobalProtect Linux Client

---

Steps to reproduce the behavior:

1. Download globalprotect linux client
   1.1 RPM - https://drive.google.com/open?id=114b9qKCb6B9piwU7z5olaBM88cV7n3Hk
   1.2 DEB - https://drive.google.com/open?id=1w4vsEEwIXBCKreyP2SIj7P40Zc7auYL2
2. Install (rpm - i or dpkg -i)
3. Enable network-manager service
4. Run globalprotect from the terminal

Expected behavior:

Normally running globalprotect connect --portal portaladdress.com will result in the terminal requesting your username/password

Actual behavior:

The GlobalProtect agent is unable to get input from the terminal.

[user@work ~]$ globalprotect
Cannot connect to local gpd service.

[user@work globalprotect]$ systemctl status gpd
● gpd.service - GlobalProtect VPN client daemon
Loaded: loaded (/usr/lib/systemd/system/gpd.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2018-07-11 07:22:17 EDT; 1 day 1h ago
Process: 525 ExecStartPre=/opt/paloaltonetworks/globalprotect/pre_exec_gps.sh (code=exited, status=0/>
Main PID: 547 (PanGPS)
Tasks: 10 (limit: 4671)
Memory: 20.7M
CGroup: /system.slice/gpd.service
└─547 /opt/paloaltonetworks/globalprotect/PanGPS

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Sample log output -
cat /opt/paloaltonetworks/globalprotect/PanGPS.log
P 547-T-210675968 Jul 12 07:40:33:30146 Debug( 756): Display hip report V4 on the UI
P 547-T-210675968 Jul 12 07:40:33:30745 Error(1117): Failed to send 512 bytes to client
P 547-T-210675968 Jul 12 07:40:33:31450 Error(1117): Failed to send 464 bytes to client

General notes:

I opened the issue here instead of with PaloAlto because the client works under a non-Qubes Debian or Fedora installation. I tried to run yum groups install "Fedora Workstation" thinking that it may be a missing dependency. I'm under the assumption that this may be a Qubes security feature, but I'm unsure what terminology I would need to search for or how to troubleshoot further.

Any help would be appreciated.

[andrewdavidwong]

Based on our issue reporting guidelines, this does not appear to be suitable for qubes-issues. We ask that you please send this to the qubes-users mailing list instead. If, after reading our issue reporting guidelines, you believe we are mistaken, please leave a brief comment explaining why. We'll be happy to take another look, and, if appropriate, reopen this issue. Thank you for your understanding.

[andrewdavidwong]

Based on our issue reporting guidelines, this does not appear to be suitable for qubes-issues. We ask that you please send this to the qubes-users mailing list instead. If, after reading our issue reporting guidelines, you believe we are mistaken, please leave a brief comment explaining why. We'll be happy to take another look, and, if appropriate, reopen this issue. Thank you for your understanding.