Recurred again on 2026-05-28 (~23:52 local), same session, still no deterministic trigger. Logout/login was again the only recovery. Noting the timestamp to build a recurrence timeline (uptime, suspend/resume cycles) for trigger-hunting.
Also improved the diagnostics for future occurrences. wmctrl/xdotool only see XWayland windows, and on GNOME Shell 49 both org.gnome.Shell.Introspect.GetWindows and Eval are access-denied, so per-workspace occupancy can't be read from outside the compositor. I've added a small local GNOME Shell extension that runs inside gnome-shell and exposes a D-Bus method dumping live workspace state as JSON—n_workspaces, active_index, a dynamic_invariant_ok flag, stranded_empty_indices, and per-window detail (title, wm_class, pid, monitor, sticky/skip-taskbar). On the next recurrence I'll attach a snapshot with hard per-workspace occupancy, which should pin down exactly which part of the dynamic-workspace re-flow is wedged. Still single-reporter; still only logout/login recovers it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2154487 Title: mutter: dynamic-workspaces stops spawning the trailing empty workspace after some uptime (only logout clears it) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2154487/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
