VMWare Horizon >4.8 on linux fails to start: undefined symbols

VMWare Horizon 4.8 works well with Fedora but when your service forces you to move to a later version you will find Horizon client 4.9 and above to fail to start. What to do?

This is frustrating as clicking on the desktop icon nothing happens - when you figure out that the underlying script is /usr/bin/vmware-view and try running that directly you will find that the script complains about missing symbols:

/usr/lib/vmware/view/bin/vmware-view-crtbora: symbol lookup error: /usr/lib64/libpangomm-1.4.so.1: undefined symbol: _ZN4Glib6ObjectC2EOS0_

Initially most people will try to figure out why there are suddenly missing symbols after upgrading from VMware Horizon 4.8 and end up in a rat hole. The fix is remarkably simple (worked for 5.1) and to modify the /usr/bin/vmware-view file as below:

binFile=
if [[ $ROLLBACK_VMWAREVIEW = "" ]] && [ $cpu -eq 0 ]; then
binFile="vmware-view-crtbora"
else
binFile="vmware-view"
fi
# hack!! add this!!!
binFile="vmware-view"

The reason seems to be that the Horizon clients > 4.8 wants to start with a seamless desktop (and the vmware-view-crtbora) which causes problems - forcing the script to use the (legacy support) vmware-view binary will resolve your >4.8 client startup problems and you can get back to your work.