I have been trying to reproduce this bug in VMware but have not been able to. Ubuntu 18.04 always starts up with a login screen successfully for me.
What it does not do successfully is offer the "Ubuntu on Wayland" option most of the time. So I expect that's the same root cause as this bug.
Ordinarily if Wayland support is attempted and fails gracefully then your journalctl log should show something like:
Jun 14 02:28:16 ubuntu gnome-shell[790]: Failed to create backend: Could not find a primary drm kms device
If you don't see that message and still don't get Wayland support then it suggests mutter/gnome-shell is crashing during that attempt to try Wayland. In that case we would ask you to follow these instructions from within the virtual machine:
I have been trying to reproduce this bug in VMware but have not been able to. Ubuntu 18.04 always starts up with a login screen successfully for me.
What it does not do successfully is offer the "Ubuntu on Wayland" option most of the time. So I expect that's the same root cause as this bug.
Ordinarily if Wayland support is attempted and fails gracefully then your journalctl log should show something like:
Jun 14 02:28:16 ubuntu gnome-shell[790]: Failed to create backend: Could not find a primary drm kms device
If you don't see that message and still don't get Wayland support then it suggests mutter/gnome-shell is crashing during that attempt to try Wayland. In that case we would ask you to follow these instructions from within the virtual machine:
https:/ /wiki.ubuntu. com/Bugs/ Responses# Missing_ a_crash_ report_ or_having_ a_.crash_ attachment
I'll dig a bit deeper to try and find out why Wayland support seems to work so rarely, because that's the part of this bug I can reproduce.