VMWare Horizon 4.4.0 is not stable

[frakman1]

I upgraded to the latest and re-tried.
When running at full screen, the app soon dies and actually causes the desktop to reset. I have to then login to the desktop again

It seems to be stable when running in windowed mode but only in a small window. If I make it too big or even just screen size (not full screen) it crashes the desktop again.

[Gibbio]

Could you please post the log files here or in the forum?
strace too:
strace -o logs -s 44444 -f -ff vmware-view

Thanks!

[Gibbio]

the session crash right? Or the X11 server?

[frakman1]

Thanks for writing back Gibbio.

I'm not sure what you call it, I think you mean the X11 server since it's the Host that crashes (also the vmware horizon app). Anyway, this is the screen I get afterwards (VNC Server also breaks since I can't connect via VNC anymore):

Is there a log file I could provide that would be useful? It is highly reproducible.

It is also strange that on this screen, it says VMWare Horizon version 4.2, but on the About screen of the VMWareHorizon app, it says 4.4.0

[Gibbio]

I think the first problem isn't specifically related to the vmware client, happend to me while in VNC just by clicking in the Setting panel...
For the second problem, you have just to update the RPiTC Builder via the Other Update RPiTC Builder or by downloading manually from this repo

[frakman1]

• I am actually using the latest version of RPiTC Builder through the "Other Update RPiTC Builder "
• I tried using VNC via the "Remote Viewer" and that didn't have any problems connecting to my desktop and using it normally. It's only VMWare horizon doing this.
• The logs (there are too many) all basically point at a
  recvmsg(3, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)

Question. I have to re-enter the server and then select the desktop everytime I start VMWare Horizon. How can I have the server name persist ?

[frakman1]

I ran it again, this time from the command line with all the parameters. It pointed me to a log file but it didn't show anything interesting. Another log file in the same folder however showed the backtrace:
vmware-view --kioskLogin --nonInteractive --once --fullscreen --nomenubar --serverURL="xxxx" --userName="xxxx" --password='xxxx'

Using log file /tmp/vmware-rpitc/vmware-horizon-client-16381.log
2016-11-28 09:19:11.100-05:00: vmware-view 16381| CdkLaunchItemConnection_GetAutoConnect: assertion 'conn->userPreferences != NULL' failed
2016-11-28 09:19:12.927-05:00: vmware-view 16381| rmksContainer(16477): CreateMKSInterface: forcing mount, Remote MKS already present
2016-11-28 09:19:12.928-05:00: vmware-view 16381| rmksContainer(16477): OnMountUnmount: (0, 0) 1366 X 768.
2016-11-28 09:19:15.669-05:00: vmware-view 16381| rmksContainer(16477): OnDisplayTopologyChanged: monitor 0: left=0, top=0, right=1366, bottom=768
vmware-view: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
rpitc@rpitc-fd061ded:~/.vmware$ date
Mon Nov 28 09:22:14 EST 2016
rpitc@rpitc-fd061ded:~/.vmware$ cat /tmp/vmware-rpitc/vmware-mks-16478.log
<skip>
2016-11-28T09:19:12.466-05:00| main| I125: VDPOverlayHostPlugin_Init(): loading overlay plugins
2016-11-28T09:19:12.466-05:00| main| I125: MKSRoleMain: Powering on.
2016-11-28T09:19:12.466-05:00| main| I125: MKSRoleMain: Powering on SigMKS
2016-11-28T09:19:12.466-05:00| main| I125: MKSRoleMain: Powering on MKS
2016-11-28T09:19:12.466-05:00| main| I125: MKS PowerOn
2016-11-28T09:19:12.470-05:00| mks| I125: VTHREAD start thread 2 "mks" tid 16546
2016-11-28T09:19:12.470-05:00| mks| I125: MKS thread is alive
2016-11-28T09:19:12.476-05:00| mks| I125: VDPUsbRedirectionVmdb_PowerOn: powerOn skipped due to inactive plugin
2016-11-28T09:19:12.476-05:00| mks| I125: MKS-RenderMain: RenderMain: PowerOn allowed MKSBasicOps
2016-11-28T09:19:12.476-05:00| mks| I125: [I] VDPOverlayHost_BeginBackendSwitch(): complete
2016-11-28T09:19:12.476-05:00| mks| I125: MKS-RenderMain: Starting MKSBasicOps
2016-11-28T09:19:12.476-05:00| mks| I125: FBCompat_FinishBackendSwitch: gFBCompat.useIndirect = FALSE
2016-11-28T09:19:12.476-05:00| mks| I125: [I] VDPOverlayHostResetSharedSurfaceSupported(): shared surfaces are not supported
2016-11-28T09:19:12.476-05:00| mks| I125: [I] VDPOverlayHost_FinishBackendSwitch(): complete
2016-11-28T09:19:12.478-05:00| mks| I125: KHBKL: Unable to parse keystring at: ''
2016-11-28T09:19:12.478-05:00| main| I125: MKSRoleViewRemote: Powering on VDP Plugin
2016-11-28T09:19:12.478-05:00| main| I125: VDPPLUGIN: pcoip_client: connecting to target
2016-11-28T09:19:12.482-05:00| main| I125: Peer reported input preferences 0x1.
2016-11-28T09:19:12.483-05:00| main| I125: Peer has no preferred mouse mode.
2016-11-28T09:19:12.483-05:00| main| I125: Peer reported input capabilities 0x2.
2016-11-28T09:19:12.928-05:00| mks| W115: VDPPLUGIN: pcoip_client: set display topology while CONNECTING. Deferring.
2016-11-28T09:19:12.933-05:00| mks| I125: X11-Backend: successfully started by HWinMux to do window composition.
2016-11-28T09:19:12.936-05:00| mks| I125: MKS-X: XI major version 2, minor version 3
2016-11-28T09:19:12.959-05:00| mks| I125: X11-Backend: XINFO SHM available, version 1.2, shared pixmaps
2016-11-28T09:19:12.967-05:00| mks| I125: MKS-HWinCompMux: Started X11 presentation backend
2016-11-28T09:19:12.967-05:00| mks| I125: XINFO X fd is 14
2016-11-28T09:19:12.967-05:00| mks| I125: XINFO depth 24 bpp 32 class 4
2016-11-28T09:19:12.967-05:00| mks| I125: XINFO  ServerVendor: "The X.Org Foundation"
2016-11-28T09:19:12.967-05:00| mks| I125: XINFO VendorRelease: 11902000
2016-11-28T09:19:12.971-05:00| mks| I125: XINFO XKB available, version 1.0
2016-11-28T09:19:12.971-05:00| mks| I125: XINFO XTEST available, version 2.2
2016-11-28T09:19:12.971-05:00| mks| I125: XINFO Xinerama available
2016-11-28T09:19:12.972-05:00| mks| I125: XKeymap_PowerOn: use evdev keycode mapping.
2016-11-28T09:19:12.972-05:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1.
2016-11-28T09:19:13.016-05:00| mks| I125: KHBKL: Unable to parse keystring at: ''
2016-11-28T09:19:13.360-05:00| vthread-5| I125: VTHREAD initialize thread 5 "vthread-5" tid 16544
2016-11-28T09:19:13.360-05:00| vthread-5| I125: Peer reported input capabilities 0x6.
2016-11-28T09:19:13.361-05:00| mks| I125: VDPPLUGIN: pcoip_client: successfully connected
2016-11-28T09:19:15.634-05:00| vthread-6| I125: VTHREAD initialize thread 6 "vthread-6" tid 16507
2016-11-28T09:19:16.006-05:00| vthread-7| I125: VTHREAD initialize thread 7 "vthread-7" tid 16567
2016-11-28T09:19:16.006-05:00| vthread-7| I125: VDPRdeCommonHostVmdbSetDpi: Sending dpi = 96
2016-11-28T09:19:16.016-05:00| vthread-8| I125: VTHREAD initialize thread 8 "vthread-8" tid 16506
2016-11-28T09:19:16.017-05:00| mks| I125: Begin gathering input Locale Identifiers for the user.
2016-11-28T09:19:16.019-05:00| mks| I125: Number of installed Input Locale Identifiers for the user 1
2016-11-28T09:19:16.019-05:00| mks| I125: 1. Language 0x409 Layout unique id 0x0
2016-11-28T09:19:16.019-05:00| mks| I125: Finished gathering input Locale Identifiers for the user.
2016-11-28T09:19:16.358-05:00| vthread-7| I125: VDPUnityVmdbAddNotification: Sending notify client signal: ready
2016-11-28T09:19:16-05:00[+155.342]| mks| W115: Caught signal 6 -- tid 16546 (addr 405E)
2016-11-28T09:19:16-05:00[+155.342]| mks| I125: SIGNAL: pc 0x76ad16f6 sp 0x431581d8 lr 0x76adf3cd
2016-11-28T09:19:16-05:00[+155.342]| mks| I125: SIGNAL: r0 0x0 r1 0x431581e0 r2 0x0 r3 0x8 r4 0x0 r5 0x431581e0
2016-11-28T09:19:16-05:00[+155.342]| mks| I125:         r6 0x76ba6088 r7 0xaf r8 0x1 r9 0x1 r10 0x0 fp 0x0 ip 0xaf
2016-11-28T09:19:16-05:00[+155.343]| mks| I125: SIGNAL: stack 431581D8 : 0x431582f4 0x76adf3cd 0x10486e07 0x00000000
2016-11-28T09:19:16-05:00[+155.343]| mks| I125: SIGNAL: stack 431581E8 : 0x00000001 0x76b58bb1 0x431583b8 0x00000000
2016-11-28T09:19:16-05:00[+155.343]| mks| I125: SIGNAL: stack 431581F8 : 0x00000000 0x00000000 0x00000000 0x00000000
2016-11-28T09:19:16-05:00[+155.343]| mks| I125: SIGNAL: stack 43158208 : 0x00000000 0x00000000 0x00000000 0x00000000
2016-11-28T09:19:16-05:00[+155.343]| mks| I125: SIGNAL: stack 43158218 : 0x00000000 0x00000000 0x00000000 0x00000000
2016-11-28T09:19:16-05:00[+155.343]| mks| I125: SIGNAL: stack 43158228 : 0x00000000 0x00000000 0x00000000 0x00000000
2016-11-28T09:19:16-05:00[+155.345]| mks| I125: SIGNAL: stack 43158238 : 0x00000047 0x76bd2a84 0x76fdc9b8 0x43158294
2016-11-28T09:19:16-05:00[+155.345]| mks| I125: SIGNAL: stack 43158248 : 0x43158290 0x76ac7804 0x76fe0cf0 0x76bd2a84
2016-11-28T09:19:16-05:00[+155.345]| mks| I125: Backtrace:
2016-11-28T09:19:16-05:00[+155.345]| mks| I125: Backtrace[0] 0x13cd28 eip 0x431581d8
2016-11-28T09:19:16-05:00[+155.345]| mks| I125: SymBacktrace[0] 0x13cd28 eip 0x431581d8
2016-11-28T09:19:16-05:00[+155.345]| mks| E105: PANIC: Unexpected signal: 6.
2016-11-28T09:19:16-05:00[+155.345]| mks| E105:
2016-11-28T09:19:16-05:00[+155.346]| mks| W115:
2016-11-28T09:19:16-05:00[+155.346]| mks| W115+ The core dump limit is set to ZERO; no core dump should be expected
2016-11-28T09:19:16-05:00[+155.415]| mks| W115: Child process 17524 failed to dump core (status 0x6).
2016-11-28T09:19:16-05:00[+155.415]| mks| I125: Printing loaded objects
<skip>
2016-11-28T09:19:16-05:00[+155.419]| mks| I125: End printing loaded objects
2016-11-28T09:19:16-05:00[+155.419]| mks| I125: Backtrace:
2016-11-28T09:19:16-05:00[+155.419]| mks| I125: Backtrace[0] 0x13cd28 eip 0x76fe152c
2016-11-28T09:19:16-05:00[+155.419]| mks| I125: SymBacktrace[0] 0x13cd28 eip 0x76fe152c in function _rtld_global in object /lib/ld-linux-armhf.so.3 loaded at 0x76fb9000
2016-11-28T09:19:16-05:00[+155.419]| mks| I125: MKS could not find key event for 0xcd up
2016-11-28T09:19:16-05:00[+155.419]| mks| I125: MKS could not find key event for 0xcf up
2016-11-28T09:19:16-05:00[+155.419]| mks| I125: MKS could not find key event for 0xcd down
2016-11-28T09:19:16-05:00[+155.419]| mks| I125: MKS could not find key event for 0xcf down
2016-11-28T09:19:16-05:00[+155.420]| mks| I125: Msg_Post: Error
2016-11-28T09:19:16-05:00[+155.420]| mks| I125: [msg.log.error.unrecoverable] VMware Remote MKS Container unrecoverable error: (mks)
2016-11-28T09:19:16-05:00[+155.420]| mks| I125+ Unexpected signal: 6.
2016-11-28T09:19:16-05:00[+155.420]| mks| I125: [msg.panic.haveLog] A log file is available in "/tmp/vmware-rpitc/vmware-mks-16478.log".
2016-11-28T09:19:16-05:00[+155.420]| mks| I125: [msg.panic.requestSupport.withoutLog] You can request support.
2016-11-28T09:19:16-05:00[+155.420]| mks| I125: [msg.panic.requestSupport.vmSupport.vmx86]
2016-11-28T09:19:16-05:00[+155.420]| mks| I125+ To collect data to submit to VMware technical support, run "vm-support".
2016-11-28T09:19:16-05:00[+155.420]| mks| I125: [msg.panic.response] We will respond on the basis of your support entitlement.
2016-11-28T09:19:16-05:00[+155.420]| mks| I125: ----------------------------------------
2016-11-28T09:19:16-05:00[+155.420]| mks| I125: MsgIsAnswered: Using builtin default 'OK' as the answer for 'msg.panic.response'
2016-11-28T09:19:16-05:00[+155.420]| mks| I125: Exiting
rpitc@rpitc-fd061ded:~/.vmware$

[frakman1]

I don't know if this makes a difference or not, but when I run Outlook on the remote desktop is when I have the most success causing it to crash.

**UPDATE**
I've confirmed that running Outlook accelerates the demise of this app. Without Outlook, it can stay up for hours.

[Gibbio]

Did you use pcoip or standard rdp to connect to the remote session?
Did you have the same problem with horizon client 4.3?

[frakman1]

Did you use pcoip or standard rdp to connect to the remote session?

I don't know what that means. How do I know ? I used the command line I included above so whatever the defaults are.

Did you have the same problem with horizon client 4.3?

No. With 4.3, it would connect and display the screen for an instant before immediately disconnecting. I created an issue for this. With this version (4.4) the whole desktop crashes once VDI crashes/exits.

[Gibbio]

Could you please update the base OS with:
sudo apt-get update
sudo apt-get dist-upgrade

I've seen some update on the libxcursor/libxdamage/xorg-core packages today and after applying it I didn't have anymore the vnc crash problem (same symptoms as when horizon client crash).

[frakman1]

Thank you for the suggestion.
I performed the upgrade, rebooted and retried but still ran into the same error.