You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have 2 Ubuntu 24.04.1 LTS VMs running on VMware ESXi 6.5.0. If VMs are not used for a while and try to access the Web Console, it just shows a black screen as shown below:
Some users in the link: https://github.com/vmware/open-vm-tools/issues/725 1 have mentioned that using WaylandEnable=false /etc/gdm3/custom.conf solves the issue. However, once I do this change and restart the GSM service I am never able to access GUI login screen as I am presented with a black screen as shown below:
I have also tried to use lightDM as well but upon logging in system logs me out. As a temporary solution I have set the Power Saving to never turn off. With this setting issue does not occur however having a proper fix would be greatly appreciated
Reproduction steps
Leave Ubuntu 24.04 VM running on VMWare Esxi 6.5.0 and Web console will be inaccessible
...
Expected behavior
Web Console becomes inaccessible
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
We have 2 Ubuntu 24.04.1 LTS VMs running on VMware ESXi 6.5.0. If VMs are not used for a while and try to access the Web Console, it just shows a black screen as shown below:
Some users in the link: https://github.com/vmware/open-vm-tools/issues/725 1 have mentioned that using WaylandEnable=false /etc/gdm3/custom.conf solves the issue. However, once I do this change and restart the GSM service I am never able to access GUI login screen as I am presented with a black screen as shown below:
I have also tried to use lightDM as well but upon logging in system logs me out. As a temporary solution I have set the Power Saving to never turn off. With this setting issue does not occur however having a proper fix would be greatly appreciated
Reproduction steps
...
Expected behavior
Web Console becomes inaccessible
Additional context
No response
The text was updated successfully, but these errors were encountered: