oem-config fails on Nvidia GPU machine on 18.04.1

[Michel-Ekimia]

More an nvidia driver fail but happens in a oem-config scenario :

- Install 18.04.1 on an Nvidia GPU machine ( desktop or laptop)
- full-upgrade
- ubuntu-drivers autoinstall ( To get nvidia drivers)
- Reboot and confirm nvidia driver work great

- oem-config-prepare

- Send machine to client

- client goes through oem-config wizard normally

- instead of going to the new desktop , client gets a blackscreen

- After reboot he always get a black screen.

- If he logs into TTY1 , he can login and startx to get a gnome3 desktop.

[Michel-Ekimia (michel.ekimia)]

Reproduced on a 1080 ti desktop

Not reproductible on a 1050 ti prime laptop.

[Sebastien Bacher (seb128)]

Thank you for your bug report. Could you attach the journalctl log from a boot hitting the issue of not getting the greeter? Is the configuration a dual GPU or nvidia only?

[Michel-Ekimia (michel.ekimia)]

Salut Sebastien

It happens on a dual GPU ( nvidia 1080 ti) ( threadripper CPU thus NO other GPU)

Getting the systemd log now.

Still no way to upload files using ubuntu-bug on a command line system ( without logging with a browser ) or do you see a simple way to grab all log files using command line only ?

[Michel-Ekimia (michel.ekimia)]

Please find attached the Journal log with the user oem-config wizard and one reboot

[Sebastien Bacher (seb128)]

The log has those errors

gnome-shell[30907]: Failed to create backend: No resources
gnome-session[30496]: gnome-session-binary[30496]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
gnome-session-binary[30496]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1

Which seems the issue, before that nvidia-persistenced is started unsure if that can be creating issues though...

Reassigning to gnome-shell since the issue is rather on that side than on the installer one

Looking to that error upstream it's mentioned on https://gitlab.gnome.org/GNOME/mutter/issues/261

bug #1769857 seems somewhat similar on launchpad

[Michel-Ekimia (michel.ekimia)]

Many thanks for being so quick to answer.

I was wondering if this could have something to do gnome-shell greeter using wayland ?

We pause our nvidia powered machines shipment for now.

[Sebastien Bacher (seb128)]

Well, the upstream discussion/other bug are about gdm failing to fallback from wayland (which it uses by default) to xorg on nvidia machines where wayland is not working, that could be the issue here as well

[Daniel van Vugt (vanvugt)]

> gnome-shell[30907]: Failed to create backend: No resources

I don't think that's an error. It's just telling you the Nvidia driver doesn't support Wayland (which always gets tried first). In theory gdm3 is then meant to drop back to Xorg in this case (as Seb says). But some Nvidia users (including Laney) have reported that this fallback doesn't work for them:

  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bugs?field.tag=nvidia

So this bug is possibly a duplicate of one of those.

Please try this as a workaround: edit /etc/gdm3/custom.conf and uncomment the line:

   #WaylandEnable=false

Reboot, and if that fixes the problem then it appears to be a duplicate of bug 1798790.

[Launchpad Janitor (janitor)]

[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for OEM Priority Project because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

[Michel-Ekimia (michel.ekimia)]

I think that is a real important problem, could anybody at least reproduce the issue ?

[Daniel van Vugt (vanvugt)]

Please follow the instructions in comment #8.

[Yuan-Chen Cheng (ycheng-twn)]

per current oem project, we don't have this issue.

[Michel-Ekimia (michel.ekimia)]

Just a note :

- We add oem-priority because it affects our clients directly but we don't have any contract with Canonical.

- Let us know what tag we could use when we want to raise a business impacting problem

[Sebastien Bacher (seb128)]

> - We add oem-priority because it affects our clients directly but we don't have any contract with
> Canonical.

You didn't add it though, overlook?

Also do you have anyone able to reproduce we can contact for testing/getting extra informations?

[Daniel van Vugt (vanvugt)]

Due to no reply to comment #8 I'm just going to assume this is a duplicate of bug 1798790, which seems most likely. Otherwise maybe bug 1705369.