What made me suspect you used the nvidia installer was the terminology: "manually reinstalled bumblebee and nvidia-387". My mistake, and moving on...
Next, note that the "VMware driver" in use is actually LLVMpipe. This is the Mesa software renderer that all systems can use, apparently written by VMware, but that part is not interesting.
So your system is falling back to software rendering is all. And gdm3 may have detected you have some kind of discrete graphics card that is disabled (please run lspci -k for us), it would in that case choose Xorg instead of the native/Wayland option. I believe the Nvidia driver prefers Xorg by default for various reasons so having Nvidia installed will/might hide the Wayland options. That's not a bug though, but a feature of the Nvidia driver I have heard of...
So I'll assign this bug to Xorg, which should be working better at least. Please also attach your /var/log/Xorg.*
What made me suspect you used the nvidia installer was the terminology: "manually reinstalled bumblebee and nvidia-387". My mistake, and moving on...
Next, note that the "VMware driver" in use is actually LLVMpipe. This is the Mesa software renderer that all systems can use, apparently written by VMware, but that part is not interesting.
So your system is falling back to software rendering is all. And gdm3 may have detected you have some kind of discrete graphics card that is disabled (please run lspci -k for us), it would in that case choose Xorg instead of the native/Wayland option. I believe the Nvidia driver prefers Xorg by default for various reasons so having Nvidia installed will/might hide the Wayland options. That's not a bug though, but a feature of the Nvidia driver I have heard of...
So I'll assign this bug to Xorg, which should be working better at least. Please also attach your /var/log/Xorg.*