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?
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?