I spent some time attempting to reproduce on AWS today, using a g4dn.xlarge instance, which has a Nvidia Tesla T4 GPU, which supports GRID.
I installed ubuntu-desktop-minimal and rebooted, and gdm started fine with mutter 3.36.9-0ubuntu0.20.04.1. I confirmed this by looking at the instance screenshot. I then downloaded and installed the Nvidia GRID 450.51.05 driver, and rebooted. The system came up, I checked lsmod, the nvidia kernel modules were loaded, and the instance screenshot shows gdm running. I then installed VMware Horizon Agent 7.13.0-17123958 and rebooted, and again, gdm started just fine. Attached status of gdm3.service, nvidia-smi and instance screenshot. I wonder if this is GPU specific? or hypervisor specific, since the affected user runs on VMware esxi. I will again ask for more information. But for the moment, this seems very specific to the affected user's environment, and not a widespread regression. ** Attachment added: "Output of systemctl status and nvidia smi" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930359/+attachment/5505411/+files/aws-working-g4dn-xlarge.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930359 Title: gdm fails to start with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930359/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
