bllward
Contributor
Contributor

Horizon Client on Raspberry Pi showing black screen

Hi all,

I'm trying to install the Horizon 2103 Client on a Raspberry Pi 4 on IGEL OS 11.05, purely for demo purposes. I can get the client to launch and then ask for the server URL. I can type in the server URL, and then view the desktop resource. When I click on the desktop, it will start to launch, but then the client screen will turn black and I get the message: 'Remote Connection Failed: The connection to the remote computer failed.' When I click 'OK' I'm back at the connection screen.

These are the log entries I'm getting in the crtbora log:

2021-03-25T14:18:41.837Z| crtbora| I005: Initializing crt::lx::VM ...
2021-03-25T14:18:41.849Z| crtbora| I005: MKSControlClientBase: Initialized mksControl client 35FF008.
2021-03-25T14:18:41.853Z| crtbora| I005: CUIMKS: cui::MKS (3A2E148)
2021-03-25T14:18:41.853Z| crtbora| I005: CUIMKS: Grab in MKS Control is enabled for View Clients
2021-03-25T14:18:41.855Z| crtbora| I005: FcpMgr: MKS is ready.
2021-03-25T14:18:41.870Z| crtbora| I005: OnUnityStateChanged
2021-03-25T14:18:41.870Z| crtbora| I005: Initializing crt::lx::VM done
2021-03-25T14:18:41.871Z| crtbora| I005: InitAutoRedirect:1962: Entry
2021-03-25T14:18:41.871Z| crtbora| I005: OnAutoRedirect:2732: Entry
2021-03-25T14:18:41.871Z| crtbora| I005: OnAutoRedirect:2734: Exit
2021-03-25T14:18:41.871Z| crtbora| I005: InitAutoRedirect:1975: Exit
2021-03-25T14:18:41.871Z| crtbora| I005: CDR auto redirect done
2021-03-25T14:18:41.877Z| crtbora| I005: Init: Init enableUnity 0, Geometry (3840, 2160) MonitorsRect (3840, 2160)
2021-03-25T14:18:41.877Z| crtbora| I005: XKeymap_PowerOn: use evdev keycode mapping.
2021-03-25T14:18:41.877Z| crtbora| I005: SetMultiMonitorsInfo: 1 monitors were selected x 0 y 0 width 3840 height 2160.
2021-03-25T14:18:41.877Z| crtbora| I005: SetMultiMonitorsInfo: multi monitor: 1.
2021-03-25T14:18:41.877Z| crtbora| I005: SetProperty(): "VChan.VDPService.listener"="127.0.0.1:54387"
2021-03-25T14:18:41.878Z| crtbora| I005: SetProperty(): "target.name"="169.50.145.108"
2021-03-25T14:18:41.878Z| crtbora| I005: SetProperty(): "VChan.UsbOverVChan.desktopPID"="3879039867"
2021-03-25T14:18:41.878Z| crtbora| I005: SetProperty(): "VChan.UsbOverVChan.enabled"="FALSE"
2021-03-25T14:18:41.878Z| crtbora| I005: SetProperty(): "VChan.UsbOverVChan.isLoadUsbdNeeded"="FALSE"
2021-03-25T14:18:41.878Z| crtbora| I005: SetProperty(): "launchItemWindowID"="52428803"
2021-03-25T14:18:41.878Z| crtbora| I005: SetProperty(): "isAppSession"="FALSE"
2021-03-25T14:18:41.878Z| crtbora| I005: Local Dpi = 150
2021-03-25T14:18:41.878Z| crtbora| I005: GetRemoteDpi: Remote OS DPI = 0
2021-03-25T14:18:41.878Z| crtbora| I005: RemoteOS DPI = 96
2021-03-25T14:18:41.878Z| crtbora| I005: Custom Dpi = 0
2021-03-25T14:18:41.878Z| crtbora| I005: Set DPI scaling with scaleFactor=1.562500
2021-03-25T14:18:41.878Z| crtbora| I005: SetScaleFactor: Queueing up change of scale factor: current=1.000000, new=1.562500.
2021-03-25T14:18:41.878Z| crtbora| I005: SetLockedDPI: Customized dpi is 0
2021-03-25T14:18:41.878Z| crtbora| I005: EnsureEvenForRect: rect was changed from 0x0 @ 0,0 to 0x0 @ 0,0
2021-03-25T14:18:41.878Z| crtbora| I005: FitGuest: Waiting for the previous autofit to succeed. Will retry later.
2021-03-25T14:18:41.878Z| crtbora| I005: SetProperty(): "allowClientH264"="TRUE"
2021-03-25T14:18:41.878Z| crtbora| I005: SetProperty(): "allowClientHEVC"="FALSE"
2021-03-25T14:18:41.878Z| crtbora| I005: SetProperty(): "enableHardwareVideo"="TRUE"
2021-03-25T14:18:41.878Z| crtbora| I005: SetProperty(): "allowClientH264YUV444"="FALSE"
2021-03-25T14:18:41.878Z| crtbora| I005: SetProperty(): "enableUDP"="TRUE"
2021-03-25T14:18:41.881Z| crtbora| I005: VmdbAddConnection: cnxPath=/db/connection/#1/, cnxIx=1
2021-03-25T14:18:41.918Z| crtbora| I005: VmdbPipeStreamsOvlError Couldn't read: (104) Connection reset by peer.
2021-03-25T14:18:41.918Z| crtbora| I005: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'
2021-03-25T14:18:41.918Z| crtbora| I005: VmdbCnxDisconnect: Disconnect: closed pipe for sub cnx '/db/connection/#1/' (0)
2021-03-25T14:18:41.919Z| crtbora| W003: VDPLib_CreateMKS failed.
2021-03-25T14:18:41.919Z| crtbora| W003: MKSWindow connect failed

Any ideas?

0 Kudos
3 Replies
Chenddd
Contributor
Contributor

I think this problem is due to the Monitors resolution.You can try to adjust the resolution in the desktop pool

0 Kudos
bllward
Contributor
Contributor

Thanks Chenedd, but I don't think that's the problem. I think I may be missing the vmware-remotemks-container file, which is called out as missing by the app, but is not in the installer.

Any ideas?

0 Kudos
pawhitt69
Contributor
Contributor

A missing vmware-remotemks-container file is not the cause, as this file is specific to the obsolete legacy (non-lightweight) client that was removed a long time ago in Horizon Client 5.3.0.

FYI we (ThinLinX[.com]) are also encountering this exact problem when attempting to use Debian 11 (Bullseye) ARMHF.  A very similar problem occurs when using an x86 kernel that lacks CONFIG_X86_IOPL_IOPERM (https://communities.vmware.com/t5/VMware-Workstation-Player/VMware-Player-15-5-2-fails-to-start-newl...) but this is not applicable to ARM kernels, and we are still trying to fix this issue for Debian 11 ARMHF.  The issue is seemingly not kernel related, as Horizon Client (2106[.1]) works OK using Debian 10 when using a 5.10 kernel and fails when using the same kernel with a Debian 11 userspace.

 

0 Kudos