The affected user cannot reproduce the issue anymore. The new mutter
packages install fine in their environment, and gdm starts every time.
They have since rolled out the new mutter packages to their fleet
without any issues.
I'm going to mark this bug as invalid, as we can't reproduce the issue
anymore.
Maybe it was a temporary issue with restarting services? I'm not sure.
If the affected user ever experiences the issue again, I will re-open.
** Changed in: mutter (Ubuntu)
Status: New => Invalid
** Changed in: mutter (Ubuntu Focal)
Importance: High => Undecided
** Changed in: mutter (Ubuntu Focal)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1930359
Title:
gdm fails to start in a VMware Horizon VDI environment with latest
mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates
Status in mutter package in Ubuntu:
Invalid
Status in mutter source package in Focal:
Invalid
Bug description:
[Impact]
gdm fails to start in a VMware Horizon VDI environment, with Nvidia
GRID gpus passed into the VDIs.
Downgrading mutter from 3.36.9-0ubuntu0.20.04.1 to 3.36.1-3ubuntu3 in
-release fixes the issue, and the issue does not occur with
3.36.7+git20201123-0.20.04.1.
Currently looking into what landed in bug 1919143 and bug 1905825.
[Testcase]
[Where problems can occur]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930359/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
