pulseUi doesn't work in ubuntu 20.04

[antibanti]

Could you help me to fix pulseUi on Ubuntu 20.04?

/usr/local/pulse/pulseUi: error while loading shared libraries: libwebkitgtk-1.0.so.0: cannot open shared object file: No such file or directory

Thank you!

[bhccomp]

I got the same error trying to lunch UI client on Ubuntu 20.04. Any update?

[bhccomp · Accepted solution]

---

@bhccomp wrote:

I got the same error trying to lunch UI client on Ubuntu 20.04. Any update?

---

Ok here's the solution... 

I've followed these instructions: https://askubuntu.com/questions/1135065/cant-run-pulse-secure-on-ubuntu-19-04-because-libwebkitgtk-1... with only difference here: 

So instead version 19: 

sed -i "s/UBUNTU_VER\ \=\ 18\ \]/& \|\|\ [\ \$UBUNTU_VER\ \=\ 19 \]/" PulseClient_x86_64.sh

replace this line with your current version, in my case: 

sed -i "s/UBUNTU_VER\ \=\ 18\ \]/& \|\|\ [\ \$UBUNTU_VER\ \=\ 20 \]/" PulseClient_x86_64.sh

Then, do the rest and after that install this package: https://ubuntu.pkgs.org/18.04/ubuntu-main-amd64/libenchant1c2a_1.6.0-11.1_amd64.deb.html 

sudo apt-get install libenchant1c2a

You should be able to run Pulse UI now by running this command: 

/usr/local/pulse/pulseUi

It worked for me. Good luck!  

[zgoda]

Does not work because of missing libgnome-keyring.

[rayrosliabas]

Symptom:
Unable to install Pulse Secure (pulseUi) in Ubuntu 20.04 correctly.
Error message "missing libwebkitgtk"

Cause:
Library is not available in Ubuntu 20.04.
Works fine in Ubuntu 18.04

Solution:

Install using package repository of Ubuntu 18.04

Steps:

1. Set repository to 18.04

$ cat /etc/apt/sources.list
deb http://my.archive.ubuntu.com/ubuntu/ bionic main restricted
deb http://my.archive.ubuntu.com/ubuntu/ bionic universe
deb http://my.archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://security.ubuntu.com/ubuntu bionic-security main restricted
deb http://security.ubuntu.com/ubuntu bionic-security universe
deb http://security.ubuntu.com/ubuntu bionic-security multiverse
deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable

$ sudo apt update

2. Install latest Pulse Secure client from official website

$ sudo dpkg -i ps-pulse-linux-9.1r4.0-b143-ubuntu-debian-64-bit-installer.deb

3. Install dependency

$ sudo /usr/local/pulse/PulseClient_x86_64.sh install_dependency_packages

4. Launch Pulse Secure. Should works fine now

$ /usr/local/pulse/pulseUi

5. Change repository back to Ubuntu 20.04

$ cat /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu focal main restricted
deb http://archive.ubuntu.com/ubuntu focal universe
deb http://archive.ubuntu.com/ubuntu focal multiverse
deb http://archive.ubuntu.com/ubuntu focal-security main restricted
deb http://archive.ubuntu.com/ubuntu focal-security universe
deb http://archive.ubuntu.com/ubuntu focal-security multiverse

$ sudo apt update

[wiany11]

Here is a much better solution which is verified by a Pulse Connect Secure Certified Expert.

I simply did:

sudo add-apt-repository 'deb http://archive.ubuntu.com/ubuntu bionic main universe'
sudo apt install -t bionic libwebkitgtk-1.0-0
sudo dpkg -i ps-pulse-linux-9.1r5.0-b151-ubuntu-debian-64-bit-installer.deb

[IDtheTarget]

So, I've tried all of that. The pulse secure PSA5000 says that I'm an "Active User", but no IP address and no tunneling mode.  The client button never changes from "connect".

No idea where to go from here.

[cbrauckmiller]

For your issue, we're recommend opening a support case and supply your client side logs so we can take a look and see where things are going wrong.

It is a two step process for authenticating and getting your tunnel up.

1.  Over HTTPS, we authenticate and run any host check rules as defined on the VPN appliance. 

2.  Once auth is completed, the client should then either establish an ESP tunnel (UDP 4500) to the appliance or it will use the existing HTTPS connection for the tunnel.  During the tunnel setup, your endpoin will get an IP address for the virtual adapter either via DHCP or via an IP pool configured on the appliance.  If no IP is given for whatever reason, the tunnel will not come up.  So, you can save off the client logs from Pulse and then look at the ifconfig and netstat output to see if the virtual adapter got an IP address.

Additionally, Pulse has not qualified Ubuntu 20.x  as yet.  19 and below are qualified and officially supported.  Refer to this for a complete list : https://www-prev.pulsesecure.net/download/techpubs/current/2198/pulse-client/pulse-secure-client-des...

Thanks

Craig Brauckmiller

Pulse Secure

[IDtheTarget]

Sir,

Thank you for your reply.  I'm attempting to connect to a realm that's working fine for Windows clients, which is one of the reason I'm frustrated.

I will attempt to install Ubuntu 18.04 LTS and see if that works better. If not, then I will reinstall 20.04 LTS and open a ticket.

Thanks again!

Ben

[IDtheTarget]

Okay, I've installed Ubuntu 18.04 LTS, and I'm getting the same issue. The client says I'm not connected. The PSA5000 says I am, but doesn't show an IP address, VPN Tunnel Transport Mode, or agent version (though it shows agent type as Linux).

This is the exact same realm and account I use to connect from a Windows client.

Help!