VMware Horizon Community
JRovan
Contributor
Contributor

Horizon Client 2209: Problem with dual monitors

Beginning on 28Dec, I began having an issue where my dual monitor setup would stop working correctly while accessing a Win10 VPC. It mostly happens after switching to single monitor and then back to dual monitors, but not exclusively. Once it happens, I have to logout of the session and log back in. Creating a new writable volume also corrects the problem. I had been running Horizon Client 2209 on Ubuntu 22.04LTS for several weeks without any problems. No configuration changes had been made on either end other than security updates.

I notice in the client log file records such as the following once the issue occurs:

invalid unclassed pointer in cast to 'GtkContainer'
invalid unclassed pointer in cast to 'GtkWidget'
gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
invalid unclassed pointer in cast to 'GtkContainer'
invalid unclassed pointer in cast to 'GtkWidget'
gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
invalid unclassed pointer in cast to 'GtkContainer'
invalid unclassed pointer in cast to 'GtkWidget'
gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
invalid unclassed pointer in cast to 'GtkContainer'
invalid unclassed pointer in cast to 'GtkWidget'
gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
invalid unclassed pointer in cast to 'GtkContainer'
invalid unclassed pointer in cast to 'GtkWidget'
gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

AND

g_object_get: assertion 'G_IS_OBJECT (object)' failed

cdk_broker_view_clear: assertion 'CDK_IS_BROKER_VIEW(view)' failed

cdk_broker_view_add_item: assertion 'CDK_IS_BROKER_VIEW(view)' failed

cdk_broker_view_add_item: assertion 'CDK_IS_BROKER_VIEW(view)' failed

g_object_set: assertion 'G_IS_OBJECT (object)' failed

g_object_set: assertion 'G_IS_OBJECT (object)' failed

Also, I am running Xorg, not Wayland with Ubuntu.

Any ideas?

 

UPDATE 6Jan:

It appears that there used to be a similar problem with Win10 2004 VMs:

https://docs.nvidia.com/grid/15.0/grid-vgpu-release-notes-vmware-vsphere/index.html#bug-200607827-ca...  

NVIDIA indicated it wasn't on them, but was a problem with NVFBC support. The VM I am using is a Win10 21H2 which shouldn't be affected.

So similar effects have occurred previously. ...which also means it likely isn't just me this time.  ...I hope.

 

Also, I've discovered that the types of log records which I've noted above occur even before the dual monitor problem occurs. I see those record types immediately after logging in after recreating the writable volume while everything is still working normally with dual monitors.

 

UPDATE 9Jan:

The issue with dual monitors appears to have coincided with the deployment of NVIDIA vGPU Software Version 15.0. Unfortunately, we cannot revert to the previous vGPU version to test the theory that the problem is related to the update.

Reply
0 Kudos
0 Replies