But I did install the nvidia driver from a deb file (from one of the graphics driver PPAs). (What makes you suspect that I installed it using the nvidia installer?)
It's true that the first time you install the nvidia driver (and I mean via the PPA deb file), it tends to make /usr/lib/xorg/modules/extensions/libglx.so and /usr/lib/x86_64-linux- gnu/libGL.so point at the nvidia drivers, but this isn't the case in my setup, which works fine in artful, just not in bionic. (You just have to run "sudo prime-select intel" to fix this.) I guess that the affected package should probably be gdm3 instead of gnome-shell since gdm3 is already running under X on llvmpipe by the time it runs gnome-shell. Is there a way to figure out why gdm3 can't run in a Wayland session, eg log messages describing why it rejects the Intel MESA driver? ** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1733136 Title: wayland session in Ubuntu 18.04 chooses vmware driver on intel hardware Status in gdm3 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/gdm3/+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
