11 Replies Latest reply on Aug 16, 2019 10:26 AM by g0m3z

    Horizon client on Ubuntu 19.04 shows black screen after login

    g0m3z Lurker

      Hi,

       

      I have been using Horizon client 4.x without any issues on Ubuntu 19.04. Since a pop-up message was encouraging to update to the latest Horizon client version because of security reasons I did. I have removed the previous client as per the official documentation (by using sudo sh ./VMware-Horizon-Client-version.x64.bundle -u vmware-horizon-client). I set the required Linux env arameter to keep the original config. After this I have installed the latest version (5.1). I acn log in without any issue but after my client connects it shows a black screen only. I can access the menu bar at the top of the screen as well. I kept running it for like 5 minutes but nothing changed, so I got disconnected.

       

      I wanted to go back to the previous version but even after installation I have experienced the same black screen issue. I have checked the log files and found the following. I'm not sure if it helps but it seems that some basic configuration file is missing. I'm not sure if it's not there by default or if it was there previously.

       

      Thanks in advance,

       

      2019-07-23T19:08:39.820+02:00| usbArb| I125: Log for VMware USB Arbitration Service pid=14430 version=e.x.p build=build-13889129 option=Release

      2019-07-23T19:08:39.820+02:00| usbArb| I125: The process is 64-bit.

      2019-07-23T19:08:39.820+02:00| usbArb| I125: Host codepage=UTF-8 encoding=UTF-8

      2019-07-23T19:08:39.820+02:00| usbArb| I125: Host is Linux 5.0.0-20-generic Ubuntu 19.04

      2019-07-23T19:08:39.814+02:00| usbArb| I125: VTHREAD 140188648772352 "usbArb" tid 14430

      2019-07-23T19:08:39.814+02:00| usbArb| I125: DictionaryLoad: Cannot open file "/etc/vmware/config": No such file or directory.

      2019-07-23T19:08:39.814+02:00| usbArb| I125: [msg.dictionary.load.openFailed] Cannot open file "/etc/vmware/config": No such file or directory.

      2019-07-23T19:08:39.814+02:00| usbArb| I125: PREF Optional preferences file not found at /etc/vmware/config. Using default values.

      2019-07-23T19:08:39.814+02:00| usbArb| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

      2019-07-23T19:08:39.814+02:00| usbArb| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

      2019-07-23T19:08:39.814+02:00| usbArb| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

      2019-07-23T19:08:39.814+02:00| usbArb| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.

      2019-07-23T19:08:39.814+02:00| usbArb| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/config": No such file or directory.

      2019-07-23T19:08:39.814+02:00| usbArb| I125: PREF Optional preferences file not found at /usr/lib/vmware/config. Using default values.

      2019-07-23T19:08:40.150+02:00| usbArb| I125: DICT --- GLOBAL SETTINGS /usr/lib/vmware/settings

      2019-07-23T19:08:40.150+02:00| usbArb| I125: DICT --- NON PERSISTENT (null)

      2019-07-23T19:08:40.150+02:00| usbArb| I125: DICT --- HOST DEFAULTS /etc/vmware/config

      2019-07-23T19:08:40.150+02:00| usbArb| I125: DICT --- SITE DEFAULTS /usr/lib/vmware/config

      2019-07-23T19:08:40.150+02:00| usbArb| I125: USBArbRuleStore: Loading device rules from rules file.

      2019-07-23T19:08:40.150+02:00| usbArb| I125: VMware USB Arbitration Service Version 18.5.0

      2019-07-23T19:08:40.150+02:00| usbArb| I125: USBArb: Attempting to connect to existing arbitrator on /var/run/vmware/usbarbitrator-socket.

      2019-07-23T19:08:40.150+02:00| usbArb| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

      2019-07-23T19:08:40.150+02:00| usbArb| I125: USBArb: Connected to the existing arbitrator.

      2019-07-23T19:08:40.151+02:00| usbArb| I125: SOCKET 1 (10) recv detected client closed connection

      2019-07-23T19:08:40.151+02:00| usbArb| I125: USBArb: Arbitrator closed the connection.

      2019-07-23T19:08:40.151+02:00| usbArb| I120: USBArb: usb-arbitrator exit normally

        • 1. Re: Horizon client on Ubuntu 19.04 shows black screen after login
          pavlofflabbb Lurker

          Perhaps you did not completely remove the previous version, or you got an error during the installation. It may also be due to errors in the registry files.

          My knowledge is very minimal, perhaps it is worth raising the topic to the top to get an answer

          • 2. Re: Horizon client on Ubuntu 19.04 shows black screen after login
            mrGrab Lurker

            I have the same symptoms but different errors in log:

            Using log file /tmp/vmware-user/vmware-horizon-client-13430.log
            2019-07-22 23:13:50.909+03:00: vmware-view 13430| Failed to open file '/etc/vmware/udpProxy/config': No such file or directory
            2019-07-22 23:13:51.025+03:00: vmware-view 13430| cdk_window_set_multi_monitors Invalid desktop.
            2019-07-22 23:13:51.153+03:00: vmware-view 13430| udpProxyLib: FECHostSocket_Specialise: failed to get desired receive bufsize: 425984
            2019-07-22 23:13:51.153+03:00: vmware-view 13430| udpProxyLib: socket 101 transition to state SYN_SENT, reason FECSocketDoConnect refCount 4
            2019-07-22 23:13:51.221+03:00: vmware-view 13430| udpProxyLib: socket 101 transition to state CLOSED, reason FECSocketDoClose refCount 62019-07-22 23:14:52.971+03:00: vmware-view 13430| cdk_remote_desktop_get_usb_controller: assertion 'CDK_IS_REMOTE_DESKTOP(remote)' failed
            2019-07-22 23:14:52.971+03:00: vmware-view 13430| void cdk_usb_controller_set_available(gpointer, gboolean): assertion 'controller != NULL' failed
            2019-07-22 23:14:52.971+03:00: vmware-view 13430| cdk_remote_desktop_get_usb_controller: assertion 'CDK_IS_REMOTE_DESKTOP(remote)' failed
            2019-07-22 23:14:52.971+03:00: vmware-view 13430| void cdk_usb_controller_set_available(gpointer, gboolean): assertion 'controller != NULL' failed
            OSD ERROR: Session closed remotely!
            2019-07-22 23:14:53.790+03:00: vmware-view 13430| cdk_pcoip_desktop_present_changed: rmks present is FALSE.
            2019-07-22 23:15:14.892+03:00: vmware-view 13430| cdk_remote_desktop_collect_usb_status: usbd is not ready for conn cn=0a38f981-d046-4d8e-940b-04bfe2933ca6,ou=entitlements,dc=vdiglobal,dc=vmware,dc=int, ignore.
            2019-07-22 23:15:14.901+03:00: vmware-view 13430| Source ID 1906 was not found when attempting to remove it
            2019-07-22 23:15:14.904+03:00: vmware-view 13430| g_object_ref: assertion 'G_IS_OBJECT (object)' failed
            2019-07-22 23:15:14.904+03:00: vmware-view 13430| g_object_freeze_notify: assertion 'G_IS_OBJECT (object)' failed
            2019-07-22 23:15:14.904+03:00: vmware-view 13430| IA__gtk_widget_has_default: assertion 'GTK_IS_WIDGET (widget)' failed
            2019-07-22 23:15:14.904+03:00: vmware-view 13430| IA__gtk_widget_get_receives_default: assertion 'GTK_IS_WIDGET (widget)' failed
            2019-07-22 23:15:14.904+03:00: vmware-view 13430| g_object_notify: assertion 'G_IS_OBJECT (object)' failed
            2019-07-22 23:15:14.904+03:00: vmware-view 13430| IA__gtk_widget_has_default: assertion 'GTK_IS_WIDGET (widget)' failed
            2019-07-22 23:15:14.904+03:00: vmware-view 13430| g_object_thaw_notify: assertion 'G_IS_OBJECT (object)' failed
            2019-07-22 23:15:14.904+03:00: vmware-view 13430| g_object_unref: assertion 'G_IS_OBJECT (object)' failed
            2019-07-22 23:15:20.333+03:00: vmware-view 13430| TaskCombiner: Removing left CdkSetUserGlobalPreferencesTask(PEND) from combiner.
            2019-07-22 23:15:20.333+03:00: vmware-view 13430| TaskCombiner: Removing left CdkDoLogoutTask(TODO) from combiner.
            2019-07-22 23:15:20.333+03:00: vmware-view 13430| TaskCombiner: Combiner have 2 items left when it is freed.
            

             

            Tried different client versions on different PC - the same issue

            Ubuntu 18.04, 16.04

            • 3. Re: Horizon client on Ubuntu 19.04 shows black screen after login
              g0m3z Lurker

              mrGrab I can see in the log that your session got disconnected. In my case it keeps alive but I can't see anything just a black screen. I'm not even sure how can I check that the previous package got completely removed. I used the parameter to uninstall from terminal as it was defined on the official site.

              • 4. Re: Horizon client on Ubuntu 19.04 shows black screen after login
                mrGrab Lurker

                I got disconnected after I close black window. But if you talking regarding "OSD ERROR: Session closed remotely!" - then yes. But this error means nothing.

                By the way, horizon client on the same PC started from Windows 10 in virtual box working fine...

                • 5. Re: Horizon client on Ubuntu 19.04 shows black screen after login
                  arunshan04 Lurker

                  i am facing the same issue. But still no resolution at all..

                  • 6. Re: Horizon client on Ubuntu 19.04 shows black screen after login
                    adlerhn Lurker

                    Same issue here. Ubuntu 19.04, Horizon Client 4.x used to work perfectly. 5.0 crashed when launching the remote desktop, and 5.1 shows a black screen instead.

                    2019-08-14 21:16:02.084+02:00: vmware-view 10202| Failed to open file “/etc/vmware/udpProxy/config”: No such file or directory

                    2019-08-14 21:16:02.135+02:00: vmware-view 10202| cdk_window_set_multi_monitors Invalid desktop.

                    2019-08-14 21:16:07.592+02:00: vmware-view 10202| udpProxyLib: FECHostSocket_Specialise: failed to get desired receive bufsize: 425984

                     

                    2019-08-14 21:16:07.592+02:00: vmware-view 10202| udpProxyLib: socket 101 transition to state SYN_SENT, reason FECSocketDoConnect refCount 4

                     

                    2019-08-14 21:16:07.703+02:00: vmware-view 10202| udpProxyLib: socket 101 transition to state CLOSED, reason FECSocketDoClose refCount 6

                     

                    2019-08-14 21:16:48.149+02:00: vmware-view 10202| cdk_remote_desktop_get_usb_controller: assertion 'CDK_IS_REMOTE_DESKTOP(remote)' failed

                    2019-08-14 21:16:48.149+02:00: vmware-view 10202| void cdk_usb_controller_set_available(gpointer, gboolean): assertion 'controller != NULL' failed

                    2019-08-14 21:16:48.149+02:00: vmware-view 10202| cdk_remote_desktop_get_usb_controller: assertion 'CDK_IS_REMOTE_DESKTOP(remote)' failed

                    2019-08-14 21:16:48.149+02:00: vmware-view 10202| void cdk_usb_controller_set_available(gpointer, gboolean): assertion 'controller != NULL' failed

                    2019-08-14 21:16:48.910+02:00: vmware-view 10202| Source ID 1628 was not found when attempting to remove it

                    terminate called after throwing an instance of 'std::bad_alloc'

                      what():  std::bad_alloc

                    Unexpected signal: 6.

                    2019-08-14 21:16:54.868+02:00: vmware-view 10202| Source ID 1899 was not found when attempting to remove it

                    2019-08-14 21:18:18.508+02:00: vmware-view 10202| cdk_remote_desktop_collect_usb_status: usbd is not ready for conn cn=072b9eb4-db24-4dd1-89e7-eee915bdb4d9,ou=entitlements,dc=vdiglobal,dc=vmware,dc=int, ignore.

                    Loop on signal 11.

                    Panic loop

                    2019-08-14 21:18:18.519+02:00: vmware-view 10202| Source ID 1532 was not found when attempting to remove it

                    2019-08-14 21:18:18.522+02:00: vmware-view 10202| g_object_ref: assertion 'G_IS_OBJECT (object)' failed

                    2019-08-14 21:18:18.522+02:00: vmware-view 10202| g_object_freeze_notify: assertion 'G_IS_OBJECT (object)' failed

                    2019-08-14 21:18:18.522+02:00: vmware-view 10202| IA__gtk_widget_has_default: assertion 'GTK_IS_WIDGET (widget)' failed

                    2019-08-14 21:18:18.522+02:00: vmware-view 10202| IA__gtk_widget_get_receives_default: assertion 'GTK_IS_WIDGET (widget)' failed

                    2019-08-14 21:18:18.522+02:00: vmware-view 10202| g_object_notify: assertion 'G_IS_OBJECT (object)' failed

                    2019-08-14 21:18:18.522+02:00: vmware-view 10202| IA__gtk_widget_has_default: assertion 'GTK_IS_WIDGET (widget)' failed

                    2019-08-14 21:18:18.522+02:00: vmware-view 10202| g_object_thaw_notify: assertion 'G_IS_OBJECT (object)' failed

                    2019-08-14 21:18:18.522+02:00: vmware-view 10202| g_object_unref: assertion 'G_IS_OBJECT (object)' failed

                    Note: It works perfectly in Windows 10.

                    • 7. Re: Horizon client on Ubuntu 19.04 shows black screen after login
                      mchadwick19 Enthusiast

                      Do your VM's use a .local DNS name? Try turning off mDNS if so.

                      • 8. Re: Horizon client on Ubuntu 19.04 shows black screen after login
                        andersonabobrao Lurker

                        I have the same issue also..black screen followed by disconnect depending on version

                        running Debian 10

                        • 9. Re: Horizon client on Ubuntu 19.04 shows black screen after login
                          arunshan04 Lurker

                          Any of the Linux version is it working successfully?

                          • 10. Re: Horizon client on Ubuntu 19.04 shows black screen after login
                            mchadwick19 Enthusiast

                            We had a user with this issue and the resolution was to disable mDNS in nsswitch/resolv.conf and enable DNSSEC (if applicable).

                            • 11. Re: Horizon client on Ubuntu 19.04 shows black screen after login
                              g0m3z Lurker

                              @mchadwick19: Thanks for your response. Do you mean to change this DNS settings on server side? If so, I can talk to the sysadmin to check this. I'm an end user only.