I wonder if the affected system uses `xrandr` on GDM start? The settings
will be lost after a CTRC disable/enable cycle.
I had a discussion with maintainer here:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1619
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1619
** Attachment added: "screenshot of working gdm on AWS"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930359/+attachment/5505412/+files/Screenshot%20from%202021-06-18%2013-40-15.png
--
You received this bug notification because you are a member of Desktop
Packages, which is
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
I built a test package based on mutter 3.36.9-0ubuntu0.20.04.1, and
reverted the three commits introduced by LP #1905825, namely:
commit: 92834d8feceeac538299a47a8c742e155de4e6e8
From: Kai-Heng Feng
Date: Mon, 21 Dec 2020 14:34:43 +0800
Subject: renderer/native: Refactor modeset boilerplate into
** Tags added: focal
--
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 with latest mutter 3.36.9-0ubuntu0.20.04.1 in
focal-updates
Status in mutter
5 matches
Mail list logo
