** No longer affects: mutter (Ubuntu)
** No longer affects: mutter (Ubuntu Focal)
** Changed in: glib2.0 (Ubuntu)
Status: New => Fix Released
** Changed in: glib2.0 (Ubuntu Focal)
Status: New => In Progress
** Changed in: glib2.0 (Ubuntu Focal)
Importance: Undecided => High
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: glib2.0 (Ubuntu Focal)
Hi Daniel,
Yes, I am sure this is the same issue that they are experiencing there,
and I now believe the issue lies in glib, and not mutter.
When we install mutter-common, it calls the libglib2.0-0 hook to
recompile the gsettings schemas.
The customer provided me with a tarball of their
Are you sure that's the same bug as the original issue here? The
original issue sounded plausibly related to the fix for bug 1905825 as
you say.
The diff between:
ubuntu/3.36.7+git20201123-0.20.04.1
ubuntu/3.36.9-0ubuntu0.20.04.1
indeed shows no changes mentioning "schema" or "gsettings".
Okay, the affected user has now started experiencing the issue again,
and was forced to roll mutter back on their fleet.
We managed to get some logs this time, and we have determined what is
happening.
When the user upgrades the mutter packages, particularly mutter-common,
the libglib2.0-0 hook
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
** Summary changed:
- gdm fails to start with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates
+ gdm fails to start in a VMware Horizon VDI environment with latest mutter
3.36.9-0ubuntu0.20.04.1 in focal-updates
--
You received this bug notification because you are a member of Ubuntu
