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.* ** Package changed: gdm3 (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1733136 Title: wayland session in Ubuntu 18.04 chooses vmware driver on intel hardware Status in xorg-server package in Ubuntu: Incomplete Bug description: I upgraded to 18.04 and I no longer get an option to run a wayland session (17.10 offered both the default ubuntu wayland session and xorg on this laptop). gnome-shell runs under the llvmpipe driver. (Unity used to run when I first upgraded, but now gnome-shell is the only option because the gdm login screen offers no login options.) The upgrade did force me to remove bumblebee and nvidia, but afterwards I manually reinstalled bumblebee and nvidia-387 and reset to using intel via prime-select (installing nvidia changes some of the symlinks so that gnome-shell no longer boots, but "sudo prime-select intel" fixes this). The nvidia-387 modules are blacklisted in /etc/modprobe.d, and bumblebee isn't reporting any errors - bbswitch reports that the nvidia card is off, so I don't think it's an issue with hybrid graphics. (primusrun does work, as well.) Attached are the mutter logs that I generated via the environment variables mentioned in https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583 comment #20. I suspect that the culprit is hinted at in this message: Window manager warning: Failed to create renderer: Failed to initialize renderer: Missing extensio n for GBM renderer: EGL_KHR_platform_gbm, Missing EGL extensions required for EGLDevice renderer: EGL_EXT_device_base ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 Uname: Linux 4.14.0-041400-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 10:28:10 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-16 (94 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2017-11-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1733136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
