1

I'm having issues with Citrix HDX Media Engine. I'm able to connect to my workstation virtual machine just fine using Citrix Receiver. However HDX Realtime Connector can't connect for some reason. Skype for Business can't find audio device, but when I go to the Windows volume manager, I both see my speakers and microphone detected as Citrix HDX Audio. The funny thing is it used to work just yesterday, but I had to format my drive and install OS from scratch. Now I can't make it work again. Before the format I had Ubuntu dual-booted with Windows if that makes any difference.

I'm using Citrix Receiver 13.4 and HDX Media Engine 2.2.

I've tried with both x64 and x86 version but no success.

Did anyone run into similar issue before?

Any help appreciated.

sztyrymytyry
  • 11
  • 1
  • 4
  • I had the same issue as the OP - I tried everything above. Finally I checked the version of the HDX Realtime Connecter on the receiver end (from the notification area, right click on 'about'). The receiver was on version 2.2 but my client had the latest version 2.5. I removed version 2.5 on my client and installed version 2.2 to match the receiver. Now Skype can see the audio device. Happy days. – user867560 Sep 04 '18 at 07:57

2 Answers2

2

Adding following line to the wfclient.in config file was a simple solution for me.

~/.ICAClient/wfclient.ini

[...]
[WFClient]
AllowAudioInput=True
[...]
Salzor
  • 21
  • 2
2

Go to /opt/Citrix/ICAClient/utils/ and run:sudo ./hdxcheck.sh

You will get a summary of the HDX pre-reqs and that will also show you what you need to install. Likely you are missing the gstreamer0.10-plugins-base and gstreamer0.10-tools.

You can check those two with: dpkg --status gstreamer0.10-plugins-base gstreamer0.10-tools | egrep "Package|Version|Status"

Fabby
  • 34,341
  • 38
  • 97
  • 191
Marlon
  • 916
  • 6
  • 13
  • If that doesnt work, upgrade to 17.10. Mine stopped working after some update or some package I installed. Upgraded to 17.10 and without changing any config files it started working again. You might have the same issue. – Marlon Nov 10 '17 at 18:20
  • Mine stopped working again, seemed to be related to dns issues with systemd. Fixed that, then something else broke. No errors that I can see the issue with or anything to give a hint. – Marlon Feb 13 '18 at 22:06
  • 2
    `dpkg --status` is a command that does not require elevated privileges, so sudo is not necessary to run the specified command. – holmb Mar 06 '18 at 12:23
  • 1
    @holmb you are right on that, I will edit it. I was troubleshooting my issues at the time and just kept reusing parts of the previous commands so I didnt even pay attention to that when I copied/pasted – Marlon Mar 17 '18 at 16:25