Still reproducible on Ubuntu 26.10 (stonking), GNOME Shell 51.0-2ubuntu3, Wayland, Linux 7.3.0-10-generic. Hardware: Lenovo ThinkBook 14 G6+ AHP, Ryzen 7 8845H / integrated Radeon 780M (amdgpu, no NVIDIA).
This may be a related variant rather than the original lock-delay issue. Here the session is configured for manual locking only: org.gnome.desktop.screensaver lock-enabled = true org.gnome.desktop.screensaver ubuntu-lock-on-suspend = false org.gnome.desktop.screensaver idle-activation-enabled = false org.gnome.desktop.screensaver lock-delay = uint32 0 org.gnome.desktop.lockdown disable-lock-screen = false Observed on 2026-11-11 (timestamps UTC+03:00): 20:16:16 logind: Lid closed; Suspending... 20:16:36 logind: Lid opened 20:16:46 logind: Delay lock is active (... gnome-shell) but inhibitor timeout is reached 20:16:46 kernel: PM: suspend entry (s2idle) 20:16:54 kernel: PM: suspend exit Thus, closing and then reopening the lid during the 30-second delay can cause the laptop to enter suspend after the lid has already been reopened. Before the workaround, systemd-inhibit --list showed a gnome-shell delay inhibitor with the reason "GNOME needs to lock the screen". Inspecting the screenShield.js resource shipped in /usr/lib/gnome-shell/libshell-51.so shows an apparent mismatch: - _syncInhibitor() treats lock-enabled OR ubuntu-lock-on-suspend as grounds to acquire the screen-lock delay inhibitor. - _prepareForSleep() only calls this.lock(true) when ubuntu-lock-on-suspend is true. With lock-enabled=true and ubuntu-lock-on-suspend=false, this appears to leave the inhibitor waiting for a lock that is not requested on suspend. Workaround tested: change ONLY gsettings set org.gnome.desktop.screensaver lock-enabled false while keeping ubuntu-lock-on-suspend=false and disable-lock-screen=false. The gnome-shell "GNOME needs to lock the screen" inhibitor immediately disappeared. A subsequent physical lid test confirmed: 20:24:58 lid closed AND PM: suspend entry (s2idle), in the same second 20:25:09 lid opened AND PM: suspend exit The user confirmed normal behaviour; there was no 30-second delay. Manual locking after this change has not been separately tested. This is a workaround for a manual-lock-only setup, not a fix to GNOME Shell. Please consider re-triaging for the supported Ubuntu release, or advise whether this specific inhibitor/settings mismatch should be filed separately. No global inhibitor timeout was reduced and no system services were restarted. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2106697 Title: Suspend waits 30 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2106697/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
