** Description changed:
[ Impact ]
- Bug Description:
-
- If the monitor layout changes while the overview startup animation is
- running, gnome-shell never finishes starting up. 'startup-complete' is
- never emitted, the input-blocking cover pane stays on top, and the
- session never registers with GDM. The user is left with an unusable gray
- screen, and the session does not recover by itself.
+ If the monitor layout changes while GNOME Shell is starting in the
+ overview, login can stall at a gray screen that blocks input. The
+ desktop does not recover on its own. This can happen when a virtual
+ machine or remote desktop changes resolution as the client connects.
Who Is Affected:
- Sessions whose monitor layout changes in the first few seconds of the
- session, on the overview startup path. The layout change is routine on
- virtual machines and remote desktops, where the client resizes the
- session as it connects. Exposure differs by release:
-
- - Noble (GNOME 46): ubuntu-dock normally skips the overview startup
animation (disable-overview-on-startup=true), but the overview path is still
taken when disable-overview-on-startup is set to false by the user or
administrator (every login is exposed), or when ubuntu-dock has not finished
loading when the startup animation begins (default installs are exposed on some
logins).
- - Resolute (GNOME 50): exposed when org.gnome.shell start-in-overview is
set to true by the user or administrator (Ubuntu's default is false). With it
set, a layout change during the startup animation hung on every run where it
was triggered.
- - Stonking and Tenacious (GNOME 51.0): the same as Resolute. 51.0 has the
same code, and with start-in-overview=true a layout change during the startup
animation hung on every run where it was triggered.
- - Jammy (GNOME 42): default installs are not affected. Extensions load
synchronously before the startup animation, so ubuntu-dock always replaces the
overview startup animation (disable-overview-on-startup=true is Ubuntu's
default). When ubuntu-dock is disabled or removed, every login runs the
vulnerable startup code, but in testing it only hung when the layout changed in
a narrow window (after the overview starts showing, but before its controls
start their startup animation.) Only the reproducer's special 999 value (see
"How the Test Works") hit that window, and it hung every time. Layout changes
0-200 ms later did not hang, and neither did real layout changes on a cloud
virtual desktop. With ubuntu-dock enabled and
disable-overview-on-startup=false, 999 did not hang either (6/6 OK). The test
VMs render in software, where GNOME disables animations, so Jammy was also
tested with animations enabled, as on systems with hardware-accelerated
graphics (emulated by lifting GNOME's software-rendering animation inhibit).
The result was the same: 999 hung 3/3, and delays of 0-700 ms were OK 30/30. In
22 of those runs the layout change arrived while the final dash animation was
running. On GNOME 42 that animation keeps running after the overview is hidden
and finishes normally, so its completion callback still runs and the second
failure mode above was not observed on Jammy. No real-world trigger has been
found, but this is a potential pitfall worth considering regardless, since
Jammy has the same unguarded code as Noble (Overview._relayout() hiding the
overview and an unconditional await on ensureAllocation()). Because of this,
anything that changes the monitor layout in that window, such as an extension
reacting to the overview's 'showing' signal, would leave the session stuck
behind the gray cover pane. The backport is therefore preventive on Jammy.
-
- Root Cause:
-
- When 'monitors-changed' is emitted during the overview startup
- animation, Overview._relayout() calls this.hide(), which leaves the
- overview hidden in the middle of its startup animation.
- ControlsManager.runStartupAnimation() in js/ui/overviewControls.js then
- never completes, in one of two ways:
-
- - Before the first allocation, it is waiting on "await
this.layout_manager.ensureAllocation()". The hidden overview is never
allocated, so the promise never resolves.
- - After the first allocation, its final dash ease is stopped before it
finishes. The startup callback is attached to onComplete, which only runs for a
finished transition, so it is never called.
-
- In both cases LayoutManager._startupAnimationComplete() never runs, so
- the cover pane stays up and 'startup-complete' is never emitted.
-
- Resolute's gnome-shell 50.1, and the 51.0 in Stonking and Tenacious,
- already contain 93b33cf3 (the startup eases are promises collected with
- Promise.allSettled), so only the first failure mode remains there.
- Overview._relayout() still hides the overview, and ensureAllocation()
- never resolves.
-
- Fix:
-
- Three upstream commits: "overviewControls: Make sure startup animation
- completes" (93b33cf3, MR !3422) changes the dash ease from onComplete to
- onStopped, so the startup callback runs even when the transition is
- interrupted. "workspacesView: Update views on monitor changes" and
- "overview: Stop hiding on monitor changes" (ce10cb67 and 9a753aa9, MR
- !4455) stop the overview from hiding on 'monitors-changed' and let the
- workspace views rebuild themselves instead, so the overview is never
- hidden mid-animation and ensureAllocation() resolves. Each change alone
- covers only one of the two failure modes above, so all three are needed
- on Noble and Jammy. Resolute, Stonking and Tenacious already have
- 93b33cf3 and need only ce10cb67 and 9a753aa9.
-
- SRU Justification:
-
- The failure makes the session unusable and gives the user no way to
- recover. The trigger is routine for virtual machines and remote
- desktops. The fix is small and already upstream. On Noble and Jammy the
- changes are confined to 3 commits, 3 files, +5/-6 lines, touching only
- js/ui/overview.js, js/ui/overviewControls.js and
- js/ui/workspacesView.js. On Resolute, Stonking and Tenacious, 2 commits,
- 2 files, +4/-5 lines, touching only js/ui/overview.js and
- js/ui/workspacesView.js.
+ - Noble: Ubuntu Dock normally skips the overview at login. The hang can
occur if that setting is changed, or if the dock has not loaded in time to skip
the overview.
+ - Resolute, Stonking and Tenacious: Ubuntu starts on the desktop by
default. This hang requires enabling "start in overview" (org.gnome.shell
start-in-overview=true).
+ - Jammy: Ubuntu Dock loads before startup and normally skips the overview.
The hang was reproduced only with the dock disabled and a simulated monitor
change at a precise point in startup. It wasn't reproduced with real monitor
changes, so this is a preventive backport.
[ Test Plan ]
Reproducer Contents:
- reproducers.tar.gz contains one directory per release (noble/, jammy/,
- resolute/, stonking/, tenacious/), each with:
+ reproducers.tar.gz contains a reproducers/ directory with one
+ subdirectory per release (noble/, jammy/, resolute/, stonking/,
+ tenacious/), each with:
- startup-relayout@test: a GNOME Shell extension for that release (GNOME
Shell 46, 42, 50 or 51) that emits Main.layoutManager's 'monitors-changed' a
set delay after the overview startup animation begins. The delay in
milliseconds is read from ~/.config/srt-delay-ms.
- run-startup-relayout-lxd.sh: installs and enables the extension for the
ubuntu user, forces the overview startup path on every login, then restarts gdm
once per delay and reports OK or HUNG.
- - steps.txt: the steps below for that release.
+ - steps.txt: the steps below for that release. The Noble and Jammy files
list 93b33cf3 with the fix; that commit fixes the separate dash hang (LP
#2175432), included in the same upload.
The overview startup path is forced as follows:
- Noble: dash-to-dock disable-overview-on-startup=false.
- Jammy: ubuntu-dock is disabled for the ubuntu user (org.gnome.shell
disabled-extensions).
- Resolute, Stonking and Tenacious: org.gnome.shell start-in-overview=true.
- How the Test Works:
-
- For each run, the script writes the delay to the ubuntu user's
- ~/.config/srt-delay-ms and restarts gdm, which autologs in as ubuntu.
- The extension emits 'monitors-changed' the set delay after the
- overview's startup animation begins. A run is OK if the new gnome-shell
- logs "Registering session with GDM" within 25 seconds, and HUNG
- otherwise. Each result line also shows fired=1 when the extension
- emitted the signal during the startup animation; a result tagged (not-
- fired) did not exercise the race. With the current package, delay=0ms
- hangs on every run, while 100-300 ms hang only some of the time.
-
- The script stops gdm and waits for the previous session to finish
- stopping before starting gdm again. Restarting gdm directly can start
- the new autologin session while the old session's user units are still
- stopping, which makes autologin fail and leaves GDM on the login screen.
- If no new gnome-shell appears, the script retries (up to 3 attempts) and
- appends relogin=N to the result line.
-
- Release differences:
-
- - Jammy: the delay 999 is a special value built into the Jammy reproducer,
not a real delay. When it is set, the extension skips the timer and emits
'monitors-changed' immediately from the overview's 'showing' handler, before
the overview's controls have started their startup animation. The hide that
this triggers is then cut short when the controls start their own animation, so
the overview is hidden before it is ever allocated and ensureAllocation() waits
forever. A 0 ms timer also fires before the first allocation, on Jammy as on
Noble, but the outcome differs because of how each release handles disabled
animations (the test VMs use software rendering, so GNOME disables animations).
GNOME 42 still runs disabled animations as 1 ms transitions, so the hide takes
one frame, the overview is allocated during that frame, and startup completes.
GNOME 46 and later run them with zero duration, so the hide completes
immediately, the overview is never allocated, and startup hangs. That is why a
0 ms timer is enough on Noble and Resolute, and why Jammy needs the special
value. The 0-200 ms delays are kept on Jammy as controls and pass with the
current package. The default delays are "999 0 100 200".
- - Resolute: "Registering session with GDM" is logged before startup
completes on GNOME 50, so a run is OK only if "GNOME Shell started" (logged on
'startup-complete') appears within WAIT seconds (default 60). Extensions load
asynchronously on GNOME 50 and the startup animation is short, so some logins
finish the animation before the extension is ready and are reported as
(not-fired); only fired=1 runs count. Default delays are "0 50 100 150".
- - Stonking and Tenacious: the same as Resolute (GNOME 51.0, Wayland). Their
desktop images use dbus-broker and do not include dbus-run-session, which the
script needs to change the ubuntu user's settings, so the dbus-daemon package
must be installed first (it only adds the tool; dbus-broker remains the bus).
The script stops with an error if dbus-run-session is missing. There is no
Tenacious desktop image yet, so the Tenacious VM is created from the Stonking
image and upgraded (see Steps).
+ Count only runs marked fired=1: HUNG means startup did not complete
+ before the timeout; OK means it did. A result marked (not-fired) did not
+ exercise the bug. A relogin count indicates an automatic-login retry,
+ not a hang.
Steps:
Create a LXD VM from the desktop image of the release under test and
copy the reproducer into it. The images create an ubuntu user with GDM
autologin enabled. <release> is noble, jammy, resolute or stonking, and
<image> is 24.04, 22.04, 26.04 or 26.10 respectively. For Tenacious, use
<release> tenacious with <image> 26.10, then upgrade the VM as shown
below.
lxc launch images:ubuntu/<image>/desktop desktop-<release> --vm -c
limits.cpu=4 -c limits.memory=4GiB
lxc file push reproducers.tar.gz desktop-<release>/root/
lxc shell desktop-<release>
Inside the VM, extract the reproducer and confirm the ubuntu user and
autologin (expect AutomaticLogin=ubuntu and AutomaticLoginEnable=true):
tar xzf reproducers.tar.gz
getent passwd ubuntu
grep AutomaticLogin /etc/gdm3/custom.conf
On Stonking and Tenacious, install dbus-daemon:
apt install -y dbus-daemon
On Tenacious only, upgrade the VM from Stonking first, reboot, and log
back in with "lxc shell desktop-tenacious" (VERSION_CODENAME in /etc/os-
release should show tenacious, and autologin still works after the
upgrade):
sed -i 's/stonking/tenacious/g' /etc/apt/sources.list.d/ubuntu.sources
apt update && apt full-upgrade -y
reboot
- To verify the fix, first install gnome-shell and gnome-shell-common from
- -proposed. Then run the reproducer for that release as root:
-
- cd <release>
+ Run the reproducer as root with the current packages. Then install
+ gnome-shell and gnome-shell-common from -proposed and repeat the same
+ command:
+
+ cd reproducers/<release>
chmod +x run-startup-relayout-lxd.sh
- ./run-startup-relayout-lxd.sh
+ ./run-startup-relayout-lxd.sh "0" 10
Optional arguments:
- Noble: "DELAYS_MS" (default "0 100 200 300") and REPEATS (default 3).
- - Jammy: "DELAYS_MS" (default "999 0 100 200") and REPEATS (default 3). Use
"999" 10 for the hanging case only.
+ - Jammy: run with "999" 10 instead of "0" 10. The optional arguments are
"DELAYS_MS" (default "999 0 100 200") and REPEATS (default 3).
- Resolute, Stonking and Tenacious: "DELAYS_MS" (default "0 50 100 150"),
REPEATS (default 3) and WAIT (default 60). Use "0" 10 for the most reliable
trigger.
Results Obtained Before Upload:
Jammy, with the current package, default delays, 5 repeats (./run-
startup-relayout-lxd.sh "999 0 100 200" 5):
rep=1 delay=999ms pid=67060 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=999ms hasOverview=true] HUNG
rep=1 delay=0ms pid=67757 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=0ms hasOverview=true] OK
rep=1 delay=100ms pid=68550 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=100ms hasOverview=true] OK
rep=1 delay=200ms pid=69340 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=200ms hasOverview=true] OK
rep=2 delay=999ms pid=70135 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=999ms hasOverview=true] HUNG
rep=2 delay=0ms pid=70829 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=0ms hasOverview=true] OK
rep=2 delay=100ms pid=71624 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=100ms hasOverview=true] OK
rep=2 delay=200ms pid=72416 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=200ms hasOverview=true] OK
rep=3 delay=999ms pid=73204 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=999ms hasOverview=true] HUNG
rep=3 delay=0ms pid=73897 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=0ms hasOverview=true] OK
rep=3 delay=100ms pid=74693 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=100ms hasOverview=true] OK
rep=3 delay=200ms pid=75471 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=200ms hasOverview=true] OK
rep=4 delay=999ms pid=76252 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=999ms hasOverview=true] HUNG
rep=4 delay=0ms pid=76951 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=0ms hasOverview=true] OK
rep=4 delay=100ms pid=77744 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=100ms hasOverview=true] OK
rep=4 delay=200ms pid=78535 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=200ms hasOverview=true] OK
rep=5 delay=999ms pid=79327 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=999ms hasOverview=true] HUNG
rep=5 delay=0ms pid=80020 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=0ms hasOverview=true] OK
rep=5 delay=100ms pid=80802 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=100ms hasOverview=true] OK
rep=5 delay=200ms pid=81605 gnome-shell=42.9-0ubuntu2.4 fired=1 [armed
delay=200ms hasOverview=true] OK
Jammy, with the patched package, delay=999 repeated 10 times (./run-
startup-relayout-lxd.sh "999" 10):
rep=1 delay=999ms pid=118404 gnome-shell=42.9-0ubuntu2.6+ppa fired=1 [armed
delay=999ms hasOverview=true] OK
rep=2 delay=999ms pid=119189 gnome-shell=42.9-0ubuntu2.6+ppa fired=1 [armed
delay=999ms hasOverview=true] OK
rep=3 delay=999ms pid=119994 gnome-shell=42.9-0ubuntu2.6+ppa fired=1 [armed
delay=999ms hasOverview=true] OK
rep=4 delay=999ms pid=120777 gnome-shell=42.9-0ubuntu2.6+ppa fired=1 [armed
delay=999ms hasOverview=true] OK
rep=5 delay=999ms pid=122115 gnome-shell=42.9-0ubuntu2.6+ppa fired=1 [armed
delay=999ms hasOverview=true] OK
rep=6 delay=999ms pid=122919 gnome-shell=42.9-0ubuntu2.6+ppa fired=1 [armed
delay=999ms hasOverview=true] OK
rep=7 delay=999ms pid=123718 gnome-shell=42.9-0ubuntu2.6+ppa fired=1 [armed
delay=999ms hasOverview=true] OK
rep=8 delay=999ms pid=124506 gnome-shell=42.9-0ubuntu2.6+ppa fired=1 [armed
delay=999ms hasOverview=true] OK
rep=9 delay=999ms pid=125287 gnome-shell=42.9-0ubuntu2.6+ppa fired=1 [armed
delay=999ms hasOverview=true] OK
rep=10 delay=999ms pid=126093 gnome-shell=42.9-0ubuntu2.6+ppa fired=1
[armed delay=999ms hasOverview=true] OK
Noble, with the current package, default delays, 3 repeats (./run-
startup-relayout-lxd.sh "0 100 200 300" 3):
rep=1 delay=0ms pid=3113 gnome-shell=46.0-0ubuntu6~24.04.17 fired=1 [armed
delay=0ms hasOverview=true] HUNG
rep=1 delay=100ms pid=4068 gnome-shell=46.0-0ubuntu6~24.04.17 fired=1
[armed delay=100ms hasOverview=true] OK
rep=1 delay=200ms pid=5037 gnome-shell=46.0-0ubuntu6~24.04.17 fired=1
[armed delay=200ms hasOverview=true] OK
rep=1 delay=300ms pid=6021 gnome-shell=46.0-0ubuntu6~24.04.17 fired=1
[armed delay=300ms hasOverview=true] OK
rep=2 delay=0ms pid=7001 gnome-shell=46.0-0ubuntu6~24.04.17 fired=1 [armed
delay=0ms hasOverview=true] HUNG
rep=2 delay=100ms pid=7937 gnome-shell=46.0-0ubuntu6~24.04.17 fired=1
[armed delay=100ms hasOverview=true] OK
rep=2 delay=200ms pid=8895 gnome-shell=46.0-0ubuntu6~24.04.17 fired=1
[armed delay=200ms hasOverview=true] OK
rep=2 delay=300ms pid=9891 gnome-shell=46.0-0ubuntu6~24.04.17 fired=1
[armed delay=300ms hasOverview=true] OK
rep=3 delay=0ms pid=10866 gnome-shell=46.0-0ubuntu6~24.04.17 fired=1 [armed
delay=0ms hasOverview=true] HUNG
rep=3 delay=100ms pid=11808 gnome-shell=46.0-0ubuntu6~24.04.17 fired=1
[armed delay=100ms hasOverview=true] HUNG
rep=3 delay=200ms pid=12748 gnome-shell=46.0-0ubuntu6~24.04.17 fired=1
[armed delay=200ms hasOverview=true] OK
rep=3 delay=300ms pid=13735 gnome-shell=46.0-0ubuntu6~24.04.17 fired=1
[armed delay=300ms hasOverview=true] OK
Noble, with the patched package, delay=0ms repeated 10 times (./run-
startup-relayout-lxd.sh "0" 10):
rep=1 delay=0ms pid=45023 gnome-shell=46.0-0ubuntu6~24.04.18+ppa fired=1
[armed delay=0ms hasOverview=true] OK
rep=2 delay=0ms pid=46013 gnome-shell=46.0-0ubuntu6~24.04.18+ppa fired=1
[armed delay=0ms hasOverview=true] OK
rep=3 delay=0ms pid=46992 gnome-shell=46.0-0ubuntu6~24.04.18+ppa fired=1
[armed delay=0ms hasOverview=true] OK
rep=4 delay=0ms pid=47967 gnome-shell=46.0-0ubuntu6~24.04.18+ppa fired=1
[armed delay=0ms hasOverview=true] OK
rep=5 delay=0ms pid=48943 gnome-shell=46.0-0ubuntu6~24.04.18+ppa fired=1
[armed delay=0ms hasOverview=true] OK
rep=6 delay=0ms pid=49917 gnome-shell=46.0-0ubuntu6~24.04.18+ppa fired=1
[armed delay=0ms hasOverview=true] OK
rep=7 delay=0ms pid=50874 gnome-shell=46.0-0ubuntu6~24.04.18+ppa fired=1
[armed delay=0ms hasOverview=true] OK
rep=8 delay=0ms pid=51841 gnome-shell=46.0-0ubuntu6~24.04.18+ppa fired=1
[armed delay=0ms hasOverview=true] OK
rep=9 delay=0ms pid=52830 gnome-shell=46.0-0ubuntu6~24.04.18+ppa fired=1
[armed delay=0ms hasOverview=true] OK
rep=10 delay=0ms pid=53793 gnome-shell=46.0-0ubuntu6~24.04.18+ppa fired=1
[armed delay=0ms hasOverview=true] OK
Resolute, with the current package, default delays, 5 repeats (./run-
startup-relayout-lxd.sh "0 50 100 150" 5). All 17 runs where the signal
fired hung:
rep=1 delay=0ms pid=65719 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=1 delay=50ms pid=67134 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=50ms hasOverview=true startInOverview=true] HUNG
rep=1 delay=100ms pid=68536 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=100ms hasOverview=true startInOverview=true] HUNG
rep=1 delay=150ms pid=69950 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=150ms hasOverview=true startInOverview=true] HUNG
rep=2 delay=0ms pid=71342 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=2 delay=50ms pid=72737 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=50ms hasOverview=true startInOverview=true] HUNG
rep=2 delay=100ms pid=74150 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=100ms hasOverview=true startInOverview=true] HUNG
rep=2 delay=150ms pid=75588 gnome-shell=50.1-0ubuntu1.5 fired=0 [armed
delay=150ms hasOverview=true startInOverview=true] OK(not-fired)
rep=3 delay=0ms pid=76725 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=3 delay=50ms pid=78080 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=50ms hasOverview=true startInOverview=true] HUNG
rep=3 delay=100ms pid=79477 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=100ms hasOverview=true startInOverview=true] HUNG
rep=3 delay=150ms pid=80871 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=150ms hasOverview=true startInOverview=true] HUNG
rep=4 delay=0ms pid=82268 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=4 delay=50ms pid=83656 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=50ms hasOverview=true startInOverview=true] HUNG
rep=4 delay=100ms pid=85053 gnome-shell=50.1-0ubuntu1.5 fired=0 [armed
delay=100ms hasOverview=true startInOverview=true] OK(not-fired)
rep=4 delay=150ms pid=86195 gnome-shell=50.1-0ubuntu1.5 fired=0 [armed
delay=150ms hasOverview=true startInOverview=true] OK(not-fired)
rep=5 delay=0ms pid=87290 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=5 delay=50ms pid=88687 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=50ms hasOverview=true startInOverview=true] HUNG
rep=5 delay=100ms pid=90098 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=100ms hasOverview=true startInOverview=true] HUNG
rep=5 delay=150ms pid=91490 gnome-shell=50.1-0ubuntu1.5 fired=1 [armed
delay=150ms hasOverview=true startInOverview=true] HUNG
Resolute, with the patched package, delay=0ms repeated 10 times (./run-
startup-relayout-lxd.sh "0" 10):
rep=1 delay=0ms pid=93685 gnome-shell=50.1-0ubuntu1.5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=2 delay=0ms pid=97678 gnome-shell=50.1-0ubuntu1.5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK relogin=1
rep=3 delay=0ms pid=98871 gnome-shell=50.1-0ubuntu1.5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=4 delay=0ms pid=99951 gnome-shell=50.1-0ubuntu1.5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=5 delay=0ms pid=101195 gnome-shell=50.1-0ubuntu1.5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=6 delay=0ms pid=105122 gnome-shell=50.1-0ubuntu1.5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK relogin=1
rep=7 delay=0ms pid=106280 gnome-shell=50.1-0ubuntu1.5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=8 delay=0ms pid=107368 gnome-shell=50.1-0ubuntu1.5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=9 delay=0ms pid=108516 gnome-shell=50.1-0ubuntu1.5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=10 delay=0ms pid=109588 gnome-shell=50.1-0ubuntu1.5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
Stonking, with the current package, delay=0ms repeated 10 times (./run-
startup-relayout-lxd.sh "0" 10):
rep=1 delay=0ms pid=31488 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=2 delay=0ms pid=32898 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=3 delay=0ms pid=34289 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=4 delay=0ms pid=35700 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=5 delay=0ms pid=37100 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=6 delay=0ms pid=38510 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=7 delay=0ms pid=39904 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=8 delay=0ms pid=41299 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=9 delay=0ms pid=42696 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
rep=10 delay=0ms pid=44087 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
Stonking, with the patched package, delay=0ms repeated 10 times (./run-
startup-relayout-lxd.sh "0" 10):
rep=1 delay=0ms pid=4047 gnome-shell=51.0-2ubuntu3.2+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=2 delay=0ms pid=5259 gnome-shell=51.0-2ubuntu3.2+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=3 delay=0ms pid=6093 gnome-shell=51.0-2ubuntu3.2+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=4 delay=0ms pid=10079 gnome-shell=51.0-2ubuntu3.2+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK relogin=1
rep=5 delay=0ms pid=11301 gnome-shell=51.0-2ubuntu3.2+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=6 delay=0ms pid=12501 gnome-shell=51.0-2ubuntu3.2+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=7 delay=0ms pid=13678 gnome-shell=51.0-2ubuntu3.2+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=8 delay=0ms pid=14954 gnome-shell=51.0-2ubuntu3.2+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=9 delay=0ms pid=16047 gnome-shell=51.0-2ubuntu3.2+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=10 delay=0ms pid=19866 gnome-shell=51.0-2ubuntu3.2+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK relogin=1
Tenacious, with the current package, on a VM upgraded from Stonking,
delay=0ms repeated 10 times (./run-startup-relayout-lxd.sh "0" 10):
- rep=1 delay=0ms pid=3563 gnome-shell=51.0-2ubuntu3 fired=1 [armed delay=0ms
hasOverview=true startInOverview=true] HUNG
- rep=2 delay=0ms pid=5025 gnome-shell=51.0-2ubuntu3 fired=1 [armed delay=0ms
hasOverview=true startInOverview=true] HUNG
- rep=3 delay=0ms pid=6399 gnome-shell=51.0-2ubuntu3 fired=1 [armed delay=0ms
hasOverview=true startInOverview=true] HUNG
- rep=4 delay=0ms pid=7797 gnome-shell=51.0-2ubuntu3 fired=1 [armed delay=0ms
hasOverview=true startInOverview=true] HUNG
- rep=5 delay=0ms pid=9173 gnome-shell=51.0-2ubuntu3 fired=1 [armed delay=0ms
hasOverview=true startInOverview=true] HUNG
- rep=6 delay=0ms pid=10541 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
- rep=7 delay=0ms pid=11929 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
- rep=8 delay=0ms pid=13308 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
- rep=9 delay=0ms pid=14696 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
- rep=10 delay=0ms pid=16066 gnome-shell=51.0-2ubuntu3 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
+ rep=1 delay=0ms pid=3074 gnome-shell=51.0-2ubuntu4 fired=1 [armed delay=0ms
hasOverview=true startInOverview=true] HUNG
+ rep=2 delay=0ms pid=4436 gnome-shell=51.0-2ubuntu4 fired=1 [armed delay=0ms
hasOverview=true startInOverview=true] HUNG
+ rep=3 delay=0ms pid=5938 gnome-shell=51.0-2ubuntu4 fired=1 [armed delay=0ms
hasOverview=true startInOverview=true] HUNG
+ rep=4 delay=0ms pid=7310 gnome-shell=51.0-2ubuntu4 fired=1 [armed delay=0ms
hasOverview=true startInOverview=true] HUNG
+ rep=5 delay=0ms pid=8716 gnome-shell=51.0-2ubuntu4 fired=1 [armed delay=0ms
hasOverview=true startInOverview=true] HUNG
+ rep=6 delay=0ms pid=10120 gnome-shell=51.0-2ubuntu4 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
+ rep=7 delay=0ms pid=11511 gnome-shell=51.0-2ubuntu4 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
+ rep=8 delay=0ms pid=12906 gnome-shell=51.0-2ubuntu4 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
+ rep=9 delay=0ms pid=14276 gnome-shell=51.0-2ubuntu4 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
+ rep=10 delay=0ms pid=15661 gnome-shell=51.0-2ubuntu4 fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] HUNG
Tenacious, with the patched package, delay=0ms repeated 10 times (./run-
startup-relayout-lxd.sh "0" 10):
rep=1 delay=0ms pid=4091 gnome-shell=51.0-2ubuntu5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=2 delay=0ms pid=5306 gnome-shell=51.0-2ubuntu5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=3 delay=0ms pid=6453 gnome-shell=51.0-2ubuntu5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=4 delay=0ms pid=7635 gnome-shell=51.0-2ubuntu5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=5 delay=0ms pid=8904 gnome-shell=51.0-2ubuntu5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=6 delay=0ms pid=10074 gnome-shell=51.0-2ubuntu5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=7 delay=0ms pid=11251 gnome-shell=51.0-2ubuntu5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=8 delay=0ms pid=12488 gnome-shell=51.0-2ubuntu5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=9 delay=0ms pid=13664 gnome-shell=51.0-2ubuntu5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
rep=10 delay=0ms pid=14829 gnome-shell=51.0-2ubuntu5+ppa fired=1 [armed
delay=0ms hasOverview=true startInOverview=true] OK
[ Where problems could occur ]
- Overview Behaviour After Startup:
-
- With !4455 the overview no longer closes when the monitor layout
- changes, it stays open and the workspace views rebuild themselves. A
- mistake here could leave the overview with stale or misplaced workspace
- views after a hotplug or resolution change while it is open.
-
- Startup Animation Completion:
-
- On Noble and Jammy, with 93b33cf3 the startup callback runs when the
- dash transition stops for any reason, not only when it finishes. If the
- transition were stopped early in a normal login, startup would complete
- before the dash animation finished.
-
- Extensions Relying on the Overview Hiding:
-
- Third-party extensions that expect the overview to hide on 'monitors-
- changed' would now see it stay open. None of the default Ubuntu
- extensions rely on this.
+ - The overview no longer closes when a monitor is connected,
+ disconnected or resized. A mistake in this change could leave the
+ overview showing outdated or misplaced workspace previews until it is
+ closed and reopened. Third-party extensions that expect the overview to
+ close on a monitor change could also behave differently.
[ Other Info ]
+ Root cause and fix:
+
+ During the overview startup animation, js/ui/overviewControls.js waits
+ for the overview's first layout allocation (ensureAllocation()) before
+ animating. A 'monitors-changed' signal makes Overview._relayout() hide
+ the overview; if that happens before the first allocation, the hidden
+ overview is never allocated, the wait never ends, and the input-blocking
+ cover pane stays on screen. Upstream MR !4455 stops the overview from
+ hiding on monitor changes (9a753aa9) and updates the per-monitor
+ workspace views instead (ce10cb67).
+
Upstream References:
- 93b33cf314c1cab980d0221ce33cf8b574e4b8ee overviewControls: Make sure startup
animation completes (MR !3422, first released in GNOME 47.0)
ce10cb6761e514aef2e69ec44156c6c116d49302 workspacesView: Update views on
monitor changes (MR !4455, merged to main 2026-10-29, not yet released)
9a753aa969709d351632dbefd23333681cc5b3c2 overview: Stop hiding on monitor
changes (MR !4455, merged to main 2026-10-29, not yet released)
- https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3422
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4455
-
- Deviation From Upstream:
-
- The three commits apply to the Noble 46.0 source without changes or
- fuzz, and to the Jammy 42.9 source with line offsets only. Resolute,
- Stonking and Tenacious take only ce10cb67 and 9a753aa9, which apply to
- 50.1 and 51.0 without changes; 93b33cf3 is not included because 50.1 and
- 51.0 already contain it.
-
- Relationship to LP #2173589:
-
- LP #2173589 fixes an earlier startup hang, where a monitor change while
- backgrounds are loading can leave GNOME Shell waiting indefinitely. The
- overview startup hang described here was reproduced on Noble and Jammy
- without the fix for LP #2173589, so it is not a regression introduced by
- that fix.
-
- The earlier fix can let a session that would have hung during background
- loading proceed to the overview startup animation. A subsequent monitor
- change during that animation could then trigger this separate hang,
- leaving the same unresponsive gray screen. This is possible based on the
- startup sequence, but testing did not establish whether the earlier fix
- makes the overview hang more frequent.
Testing on a Cloud Virtual Desktop:
The fix was also tested on cloud-hosted virtual desktops, where the
remote display client changes the monitor layout as the session
connects. These tests used a variant of the reproducer described above.
For each run, a script restarted GDM to start a fresh session via
automatic login. A GNOME Shell extension then simulated a monitor layout
change during the overview startup animation, and the script checked
whether startup completed.
- - Noble (X11): without the patches, 1 of 12 logins completed; with all
three patches, 12 of 12. Each change alone was not enough: 93b33cf3 alone gave
9 of 15 and !4455 alone 2 of 15, against 15 of 15 with all three. With real
screen mode changes during startup instead of the reproducer, 7 of 9 logins
hung without the patches, and 24 of 24 completed with them.
- - Jammy (X11): only a layout change emitted from the overview's 'showing'
handler (the 999 case) hung (0 of 3 without the patches, 3 of 3 with all
three). Changes 0-200 ms later did not hang.
+ - Noble (X11): without the patches, 1 of 12 logins completed; with the
fixes for both bugs, 12 of 12. Each fix alone was not enough: 93b33cf3 (LP
#2175432) alone gave 9 of 15 and !4455 alone 2 of 15, against 15 of 15 with
both. With real screen mode changes during startup instead of the reproducer, 7
of 9 logins hung without the patches, and 24 of 24 completed with them.
+ - Jammy (X11): only a layout change emitted from the overview's 'showing'
handler (the 999 case) hung (0 of 3 without the patches, 3 of 3 with the fixes
for both bugs). Changes 0-200 ms later did not hang.
- Resolute (Wayland, start-in-overview=true): counting only logins where
the reproducer fired, 0 of 18 completed without the patches and 14 of 14 with
them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2174851
Title:
gnome-shell startup stuck forever when monitor layout changes during
the overview startup animation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2174851/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs