Public bug reported:
**Summary**
On Ubuntu 26.10 / GNOME 51, I can reproducibly end up with an unlocked
user session after suspend, even though locking on suspend is explicitly
enabled.
org.gnome.desktop.screensaver lock-enabled is true and
org.gnome.desktop.screensaver ubuntu-lock-on-suspend is true.
Initiating Suspend immediately shows the lock screen, but the machine does not
enter suspend right away and there is no clear indication that the suspend
request is still pending.
If I unlock and return to the desktop during this delay, I naturally
assume that the suspend attempt did not complete. I then explicitly
choose Suspend again.
At that point, however, the original suspend operation is still active,
so the second suspend request fails with
`org.freedesktop.login1.OperationInProgress`.
After the delay-inhibitor timeout expires, the original suspend
operation eventually continues and the machine enters suspend.
This can also leave USB devices such as my Wi-Fi or Bluetooth adapters
in a broken state after resume, requiring them to be physically
unplugged and reconnected.
**Steps to reproduce**
1. Log into a normal GNOME Wayland session.
2. Choose Suspend from the GNOME system menu.
3. The lock screen appears immediately, but the machine does not actually
suspend yet.
4. Unlock the session and return to the desktop.
5. Because there is no visible indication that a suspend operation is still
pending, choose Suspend again.
6. Wait.
**Actual result**
After waking the machine, the session is not locked. Pressing a key
wakes the machine and I am immediately back in my logged-in desktop
session without authentication.
This defeats the configured lock-on-suspend behavior and is a security
issue: a machine left unattended after suspend can resume directly into
the user's unlocked session.
Seems that the second suspend request collides with the still-running
first suspend operation.
The journal shows:
`gnome-session-service: Failed to call Suspend():
GDBus.Error:org.freedesktop.login1.OperationInProgress: Action suspend
already in progress`
Approximately 30 seconds after the original request:
`systemd-logind: Delay lock is active (... PID .../gnome-shell) but
inhibitor timeout is reached.`
The original suspend operation then proceeds and the machine enters
suspend.
After resume I have also observed USB devices failing to reconnect.
During this reproduction the kernel logged:
`usb usb3-port3: device 3-3 not suspended yet`
**Expected result**
Once the user unlocks and returns to the desktop during the pre-suspend
delay, the system should either:
- cancel the pending suspend operation, or
- clearly indicate that suspend is still in progress and prevent a second
conflicting suspend request.
The current behavior makes it appear that the first suspend attempt was
cancelled or failed, while it is actually still pending in the
background.
**Additional information**
`org.gnome.desktop.screensaver lock-enabled` is `true`.
`org.gnome.desktop.screensaver ubuntu-lock-on-suspend` is `true`.
`org.gnome.desktop.lockdown disable-lock-screen` is `false`.
The issue is reproducible.
ProblemType: Bug
DistroRelease: Ubuntu 26.10
Package: gnome-shell 51.0-2ubuntu3
ProcVersionSignature: Ubuntu 7.3.0-9.9-generic 7.3.0-rc6
Uname: Linux 7.3.0-9-generic x86_64
ApportVersion: 2.36.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 25 18:22:44 2026
DisplayManager: gdm3
InstallationDate: Installed on 2026-09-21 (34 days ago)
InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64
(20260826)
ProcEnviron:
LANG=hu_HU.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to stonking on 2026-10-20 (5 days ago)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug stonking third-party-packages wayland-session
** Attachment added: "jounalctl and lsusb logs"
https://bugs.launchpad.net/bugs/2172178/+attachment/6012529/+files/suspend-lock-bug.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2172178
Title:
unlocked user session after suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2172178/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
