Package Details: icaclient 24.8.0.98-1

Git Clone URL: https://aur.archlinux.org/icaclient.git (read-only, click to copy)
Package Base: icaclient
Description: Citrix Workspace App (a.k.a. ICAClient, Citrix Receiver)
Upstream URL: https://www.citrix.com/downloads/workspace-app/linux/workspace-app-for-linux-latest.html
Licenses: custom:Citrix
Conflicts: bin32-citrix-client, citrix-client
Submitter: wmarshall
Maintainer: buzo (alhirzel)
Last Packager: buzo
Votes: 180
Popularity: 0.68
First Submitted: 2011-12-08 18:49 (UTC)
Last Updated: 2024-10-10 12:52 (UTC)

Pinned Comments

buzo commented on 2021-06-26 12:42 (UTC) (edited on 2023-02-02 09:00 (UTC) by buzo)

If you cannot build because of a missing tar ball or a failed sha256 checksum validation, then the package is most likely outdated and they have removed the old version already. In this case, please click on “Flag package out-of-date”.

evanator commented on 2020-07-02 06:46 (UTC)

Found a fix for "authentication service could not be contacted"

Edit the config file under /home/username/.ICAClient\WFClient.ini and add a new line SSLCiphers=ALL save file and run "killall AuthManagerDaemon ServiceRecord selfservice storebrowse"

Relaunch Citrix and you should be fine

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 57 Next › Last »

dedguy21 commented on 2023-07-30 16:36 (UTC)

@Moabeat, yes that's exactly what happened. $LANG did not populate causing the error. I changed PKGBUILD to $LANG='en' to just force English as the language, but I'm sure there's a more elegant solution.

moabeat commented on 2023-07-28 19:53 (UTC)

@dedguy21 I figured that one out. Probably your $LANG was empty. This caused the error. Added a line to default to "en" if that's the case. Should be more robust like this.

dedguy21 commented on 2023-07-25 00:49 (UTC) (edited on 2023-07-25 00:53 (UTC) by dedguy21)

Update: figured it out, it wasn't reading 'en' as a language in the build process, made a change to PKBUILD. Thanks

Hello, just wondering What is the workaround for:

cp: cannot stat '/home/user/.cache/paru/clone/icaclient/pkg/icaclient/opt/Citrix/ICAClient/nls//module.ini': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...
error: failed to build 'icaclient-23.7.0.17-1': 
error: packages failed to build: icaclient-23.7.0.17-1

buzo commented on 2023-07-24 12:31 (UTC)

Sorry for the late update – I've been quite busy. Adding two co-maintainers.

daniel_shub commented on 2023-07-13 18:48 (UTC)

@eLGi you could also complain to citrix (e.g., https://discussions.citrix.com/topic/415050-create-persistent-download-link-when-version-is-released-not-when-version-changes/#comment-2086300) and get them to create a persistent link at the time of release and not only when it becomes outdated.

eLGi commented on 2023-07-13 13:17 (UTC)

If you get this error: ==> ERROR: icaclient-x64-23.5.0.58.tar.gz was not found in the build directory and is not a URL.

Just edit build files and set 'url' to: https://www.citrix.com/downloads/workspace-app/legacy-workspace-app-for-linux/workspace-app-for-linux-latest7.html

class101 commented on 2023-06-27 22:19 (UTC)

Below a workaround to the Apps and Desktops not loading problem, the trick is to force Citrix to use IPv6 instead of IPv4

  • Delete all in ~/.ICAClient
  • Find the IPv6 address of your NetScalerGatewayDomain, normally return after the ping NetScalerGatewayDomain command
  • Bind the IPv6 address to your NetScalerGatewayDomain in /etc/hosts
  • Run selfservice and add your server normally with your NetScalerGatewayDomain
  • Authenticate

Apps are loading fine after that

class101 commented on 2023-06-27 20:37 (UTC) (edited on 2023-06-27 20:56 (UTC) by class101)

I finally opened a ticket to the Citrix Technology Preview about the selfservice IPv4/6 problem because I think I got the right technical details.
selfservice hanging and never returning Apps can translate to :
Citrix attempts to make a HTTPS request over IPv4, when supposed to do it in IPv6, and it does not return a HTTP response. On the other hand, the same HTTP request in IPv6 receives very well the response 200 OK

Attaching a Wireshark TCP sniffer on my machine revealed that the following HTTP request is never receiving a response from the NetScaler gateway, it is attemting 3 times, 10 minutes each, so the timeout is very long 30min.

The following HTTP request, converted to curl, fails and is never getting a response, and will work if you remove -4, or change -4 to -6.

curl 'https://<NetScalerGateway>/Citrix/<NetScalerEndpoint>/auth/v1/token' \
-4 \
-H 'User-Agent: CitrixReceiver' \
-H 'Content-Type: application/vnd.citrix.requesttoken+xml' \
-H 'Accept: application/vnd.citrix.requesttokenresponse+xml, application/vnd.citrix.requesttokenchoices+xml' \
-H 'Authorization: CitrixAuth <redacted>' \
-H 'Cookie: NSC_AAAC=<redacted>;' \
-H 'X-Citrix-Gateway: <NetScalerGateway>' \
-d '<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<requesttoken xmlns="http://citrix.com/delivery-services/1-0/auth/requesttoken">

  <redacted>

</requesttoken>
' \
-v

But the request gets a response if I remove -4 or change it to -6
The issue is, in my opinion, related to the recent changes they have made to bring the IPv6 support on Linux since 2305 because this is the first version I notice the issue.

I think they forgot old codes to update for IPv6 support, because the problem is not necessarily seen from one internet service provider to another but is a blocker issue to run selfservice when it happens.

class101 commented on 2023-06-22 06:52 (UTC) (edited on 2023-06-28 17:46 (UTC) by class101)

@johnnybash

Citrix Workspace App for Linux: How to trust a CA certificate? Created: 09 Jan 2018 | Modified: 02 May 2023

At work too I see codes existing from years that nobody gives a f. to update, this is not the right approach either to leave it as is because you don’t want to remove the fingers out of the ass, others more clairvoyant will do it.

The rehash tool is linked in documentation anyway. It is your approach messing up the Arch Linux standard and opening your system to scripts of Citrix, I’m sure they are safer than the experiment of linking opt to etc and hope it works.

Citrix is unaware the scripts are modifying a global system certificate folder, YOU are allowing it to do so, your responsibility. Crash a car in the Wall, your responsibility too.

Try to symlink /tmp to /, if it work, is it OK to leave it as it ? Try to symlink /usr/share/applications to `~/.local/share/applications``, if it work, is it OK to leave it as is ?

I think I just gave this reply too much attention...

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 57 Next › Last »