I gave up and moved files back to /usr/local/pulse. Things are beyond my control.
@jsimonetti: thanks for testing results!
Search Criteria
Package Details: pulse-secure 22.8r1_b31437-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/pulse-secure.git (read-only, click to copy) |
---|---|
Package Base: | pulse-secure |
Description: | Ivanti Secure Access Client |
Upstream URL: | https://www.pulsesecure.net/ |
Licenses: | custom |
Conflicts: | pulse-connect-secure |
Submitter: | yan12125 |
Maintainer: | chiwanpark |
Last Packager: | chiwanpark |
Votes: | 37 |
Popularity: | 1.34 |
First Submitted: | 2017-09-02 07:40 (UTC) |
Last Updated: | 2025-02-18 11:56 (UTC) |
Dependencies (11)
- curl (curl-gitAUR, curl-c-aresAUR)
- dbus (dbus-gitAUR, dbus-selinuxAUR)
- dmidecode (dmidecode-gitAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- libbsd (libbsd-gitAUR)
- libgnome-keyring
- openssl (openssl-gitAUR, openssl-staticAUR)
- patch (patch-gitAUR)
- gtkmm3 (optional) – for pulseUi,
- psmisc (psmisc-selinuxAUR) (optional) – for pulsesvc -K,
- webkit2gtk (webkit2gtk-imgpasteAUR) (optional) – for pulseUi
Required by (0)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 Next › Last »
yan12125 commented on 2017-10-25 14:30 (UTC)
jsimonetti commented on 2017-10-24 18:07 (UTC)
It appears that actually it is the running of pulsesvc which is the problem.
I removed the symplink and ran pulseUi from terminal:
% LD_LIBRARY_PATH=/opt/pulsesecure:$LD_LIBRARY_PATH /opt/pulsesecure/pulseUi
(pulseUi:1623): libsoup-CRITICAL **: soup_cookie_jar_get_cookies: assertion 'SOUP_IS_COOKIE_JAR (jar)' failed
Cert Subject Name: <snip>
Cert Issuer Name: <snip>
Cert Expiry Date: <snip>
sh: /usr/local/pulse/pulsesvc: No such file or directory
rudepeople commented on 2017-10-24 12:58 (UTC) (edited on 2017-10-24 13:04 (UTC) by rudepeople)
@yan12125: how about this error;
(pulseUi:1614): libsoup-CRITICAL **: soup_cookie_jar_get_cookies: assertion 'SOUP_IS_COOKIE_JAR (jar)' failed
[EDIT]: never mind... this seems to be a proxy issue of some kind. I'm going to following up with Pulse team.
https://forums.pulsesecure.net/topic/pulse-desktop-clients/1003626-ubuntu-pulseui-4460-libsoup-critical-soup-cookie-jar-get-cookies-assertion-soup-is-cookie-jar-jar-failed
yan12125 commented on 2017-10-24 10:20 (UTC)
@jsimonetti: Could you run `sudo strace -fp <pid of pulsesvc> |& grep /usr/local/pulse` to see which path is it accessing?
I may reconsider putting things back to /usr/local/pulse. See also https://lists.archlinux.org/pipermail/aur-general/2017-August/033451.html for previous discussions.
@rudepeople: that message is less than informative. Only Pulse Secure staff can fix it - nobody else has pulseUi.cpp.
jsimonetti commented on 2017-10-24 10:00 (UTC)
For some reason, this package only works if I also add a symlink from /usr/local/pulse -> /opt/pulsesecure/
Our company uses a hostchecker (which doesn't do anything for linux platform, but still runs).
Without this symlink, the log is spammed with errors such as:
pulseui.error Failed to read return cookie from host checker process (pulseUi.cpp:948)
pulseui.error initiatePreAuthHostCheck() failed, isPostAuth: 1 (pulseUi.cpp:1055)
So somewhere in the pulseUi code there appears to be a hardcoded path to /usr/local/pulse ;(
rudepeople commented on 2017-10-24 05:18 (UTC) (edited on 2017-10-24 05:21 (UTC) by rudepeople)
@yan12125: Yep, I'm already using networkmanager, and before you responded, I went ahead and installed gnome... same issue.
On your suggestion, I ran:
$tail -f ~/.pulse_secure/pulse/pulsesvc.log
every time I click "submit" (within pulseUi) I get something like this:
20171023224951.187212 pulsesvc[p2864.t2864] pulseui.error (pulseUi.cpp:265)
I'm seeing it every time I hit "submit".
I tried googleing it, but I'm not seeing that specific error anywhere else (the search was only 2 pages deep so... gotta check 'em all!), and I cant seem to get to kb.pulsesecure.net to search for the error specifically. I get a DNS error when I try.
Any help would be greatly appreciated!
Before anyone suggests network issues, my ISP is a "last mile" provider. their network is secure as FSCK, but it's also completely transparent, lacking all the traffic shaping BS of large providers. Also, this all works fine in... *sigh* ...windows.
yan12125 commented on 2017-10-24 04:45 (UTC)
@rudepeople: This is DE-independent. I use this fine with LXQt.
I indeed got some issue with connman. Its routing table strategy conflicts with pulse-secure, so I switched to NetworkManager. BTW, I found that after checking ~/.pulse_secure/pulse/pulsesvc.log.
rudepeople commented on 2017-10-24 03:19 (UTC)
do I have to have gnome installed for this to work? when I open pulseUi and add my company connection, I get the user-name field, but clicking submit yields no response...
I'm attempting to run this in KDE.
yan12125 commented on 2017-10-23 17:08 (UTC)
Yes, you need the 64-bit version for the new version. BTW, I hope this can implemented: https://github.com/yan12125/aur/issues/7. Help wanted :)
codedmart commented on 2017-10-23 16:54 (UTC)
Nevermind I see what happened.
Pinned Comments
chiwanpark commented on 2021-02-24 10:21 (UTC)
If you want to use old pulse-secure client 9.1r9, please download the following package.
https://drive.google.com/file/d/1_8tRA-T9vV08n_TpHqdcG5IvalxBuZ7_/view?usp=sharing
The rewritten pulse-secure client requires a service called 'pulsesecure'. Please enable and start the service before running the client.