When resuming from suspension, Gnome shows the desktop before prompting user password

Sometimes (roughly 50% of the time, but I’m not able to say when exactly), when I resume from suspension, the screen shows for a fraction of second the desktop before suspension, and not the lock screen – which is shown correctly shortly thereafter.

I know it’s not a big deal, but I was curious to know if others have the same behaviour. Although this is mostly safe, it’s not ideal that someone opening up the lid can see (even for a fraction of seconds) the desktop without typing the password.

My system:

System:
  Kernel: 5.13.8-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.13-x86_64 
  root=UUID=e6c4e28c-1714-4aa0-8378-71e34489645d ro 
  cryptdevice=UUID=558055a3-e71d-4692-926f-516ae14a27c3:luks-558055a3-e71d-4692-926f-516ae14a27c3 
  root=/dev/mapper/luks-558055a3-e71d-4692-926f-516ae14a27c3 apparmor=1 
  security=apparmor udev.log_priority=3 enable_fbc=1 enable_psr=1 
  disable_power_well=0 mem_sleep_default=deep 
  resume=/dev/mapper/luks-558055a3-e71d-4692-926f-516ae14a27c3 
  resume_offset=65067008 
  Desktop: GNOME 40.3 tk: GTK 3.24.30 wm: gnome-shell dm: GDM 40.0 
  Distro: Manjaro Linux base: Arch Linux 
Machine:
  Type: Laptop System: Dell product: XPS 15 7590 v: N/A serial: <filter> 
  Chassis: type: 10 serial: <filter> 
  Mobo: Dell model: 018W12 v: A06 serial: <filter> UEFI: Dell v: 1.12.0 
  date: 06/10/2021 
Battery:
  ID-1: BAT0 charge: 80.2 Wh (83.6%) condition: 95.9/97.0 Wh (98.8%) 
  volts: 12.9 min: 11.4 model: LGC-LGC8.33 DELL 5XJ280A type: Li-ion 
  serial: <filter> status: Charging 
CPU:
  Info: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP 
  arch: Kaby Lake note: check family: 6 model-id: 9E (158) stepping: A (10) 
  microcode: EA cache: L2: 12 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 62431 
  Speed: 800 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 800 2: 2999 
  3: 3245 4: 1066 5: 1156 6: 1254 7: 2873 8: 1487 9: 2145 10: 1409 11: 1854 
  12: 1718 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Dell 
  driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300 
  Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo 
  bus-ID: 1-12:4 chip-ID: 0c45:6723 class-ID: 0e02 
  Display: x11 server: X.org 1.20.13 compositor: gnome-shell driver: 
  loaded: modesetting resolution: <missing: xdpyinfo> 
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 21.1.6 
  direct render: Yes 
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel 
  v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 
  chip-ID: 8086:a348 class-ID: 0403 
  Sound Server-1: ALSA v: k5.13.8-1-MANJARO running: yes 
  Sound Server-2: JACK v: 1.9.19 running: no 
  Sound Server-3: PulseAudio v: 15.0 running: yes 
  Sound Server-4: PipeWire v: 0.3.33 running: no 
Network:
  Device-1: Intel Wi-Fi 6 AX200 vendor: Rivet Networks Killer™ 
  driver: iwlwifi v: kernel port: efa0 bus-ID: 3b:00.0 chip-ID: 8086:2723 
  class-ID: 0280 
  IF: wlp59s0 state: up mac: <filter> 
  IF-ID-1: virbr0 state: down mac: <filter> 
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 
  bus-ID: 1-4:10 chip-ID: 8087:0029 class-ID: e001 
  Report: rfkill ID: hci0 rfk-id: 7 state: down bt-service: enabled,running 
  rfk-block: hardware: no software: yes address: see --recommends 
Drives:
  Local Storage: total: 476.94 GiB used: 193.49 GiB (40.6%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital 
  model: PC SN730 NVMe WDC 512GB size: 476.94 GiB block-size: physical: 512 B 
  logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> 
  rev: 11150012 temp: 33.9 C scheme: GPT 
Partition:
  ID-1: / raw-size: 355.94 GiB size: 349.36 GiB (98.15%) 
  used: 193.49 GiB (55.4%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0 
  mapped: luks-558055a3-e71d-4692-926f-516ae14a27c3 
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) 
  used: 500 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p7 maj-min: 259:7 
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) 
  ID-1: swap-1 type: file size: 15 GiB used: 0 KiB (0.0%) priority: -2 
  file: /swapfile 
Sensors:
  System Temperatures: cpu: 52.0 C mobo: N/A 
  Fan Speeds (RPM): cpu: 2396 fan-2: 2416 
Info:
  Processes: 422 Uptime: 18h 38m wakeups: 14 Memory: 15.27 GiB 
  used: 5.7 GiB (37.3%) Init: systemd v: 249 tool: systemctl Compilers: 
  gcc: 11.1.0 clang: 12.0.1 Packages: 1773 pacman: 1756 lib: 483 flatpak: 13 
  snap: 4 Shell: Zsh v: 5.8 running-in: gnome-terminal inxi: 3.3.06 

With the disclaimer that I’m not a GNOME user and that I also never suspend or hibernate my system ─ this is a desktop, not a laptop ─ the issue you are reporting has been reported here before, and I’m afraid it’s an upstream bug in GNOME. It was already around in GNOME 3.38 and it has apparently managed to sneak into the GNOME 4.0 code as well.

:man_shrugging:

1 Like

Well, in that case… I’ll wait :man_shrugging:t3:

Seems a know issue:

Also on KDE:
https://bugs.kde.org/show_bug.cgi?id=316734

2 Likes

I’ve marked this answer as the solution to your question as it is by far the best answer you’ll get.

However, if you disagree with my choice, please feel free to take any other answer as the solution to your question or even remove the solution altogether: You are in control! (If you disagree with my choice, just send me a personal message and explain why I shouldn’t have done this or :heart: or :+1: if you agree)

:innocent:
P.S. In the future, please don’t forget to come back and click the 3 dots below the answer to mark a solution like this below the answer that helped you most:
Solution
so that the next person that has the exact same problem you just had will benefit from your post as well as your question will now be in the “solved” status.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.