Inhibitors don't seem to change based on lock-delay:
$ gsettings set org.gnome.desktop.screensaver lock-delay 1
$ systemd-inhibit --list
WHO UID USER PID COMM WHAT >
ModemManager 0 root 2020 ModemManager sleep >
NetworkManager 0 root 1977 NetworkManager sleep >
UPower 0 root 2712 upowerd sleep >
Unattended Upgrades Shutdown 0 root 2286 unattended-upgr shutdown >
GNOME Shell 1000 heel 3405 gnome-shell sleep >
heel 1000 heel 3502 gsd-media-keys handle-power-key:ha>
heel 1000 heel 3502 gsd-media-keys sleep >
heel 1000 heel 3506 gsd-power sleep >
8 inhibitors listed.
$ gsettings set org.gnome.desktop.screensaver lock-delay 0
$ systemd-inhibit --list
WHO UID USER PID COMM WHAT
>
ModemManager 0 root 2020 ModemManager sleep
>
NetworkManager 0 root 1977 NetworkManager sleep
>
UPower 0 root 2712 upowerd sleep
>
Unattended Upgrades Shutdown 0 root 2286 unattended-upgr shutdown
>
GNOME Shell 1000 heel 3405 gnome-shell sleep
>
heel 1000 heel 3502 gsd-media-keys
handle-power-key:handle-s>
heel 1000 heel 3502 gsd-media-keys sleep
>
heel 1000 heel 3506 gsd-power sleep
>
8 inhibitors listed.
And yes I only see this on my machine with an nvidia card so at first I
was suspecting weirdness with that driver as there are other suspend
issues that seems to be connected to running certain wine apps. But at
least in terms of this 30s delay it seems to come down to the screen
locking mechanism.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2106697
Title:
Suspend waits 30 seconds
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Suspend is delayed by 30 seconds likely due to GNOME Shell's screen
lock inhibitor not being released properly when lock-delay is set to
0.
Steps to reproduce:
Use Ubuntu 25.04 with GNOME Shell 48, login and start an application
like browser (the issue doesn't reproduce if you attempt suspend
immediately after login).
Trigger suspend via UI or systemctl suspend.
Expected result:
Screen locks and system suspends within a couple of seconds.
Actual result:
System waits exactly 30 seconds before suspending.
gsettings set org.gnome.desktop.screensaver lock-delay 1
causes GNOME to release the inhibitor promptly, and suspend happens
quickly.
An alternative is disabling screen lock (both idle and suspend) in the
security settings in which case suspend also happens quickly.
Conclusion:
This suggests that GNOME Shell registers a delay inhibitor for locking the
screen, but does not properly release it when lock-delay = 0. Instead, systemd
has to wait the full 30-second timeout before suspending.
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: gnome-shell 48.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0
Uname: Linux 6.14.0-13-generic x86_64
ApportVersion: 2.32.0-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 10 14:04:35 2025
DisplayManager: gdm3
InstallationDate: Installed on 2025-04-01 (9 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250331)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 48.1-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2106697/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
