Bug 2279679

Summary: Slight pause after resume, before the unlock screen is shown
Product: [Fedora] Fedora Reporter: Bojan Smojver <bojan>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 40CC: gnome-sig, jadahl, mclasen, philip.wyett, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://bodhi.fedoraproject.org/updates/FEDORA-2024-b5624d3dd9
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-05-16 08:20:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journal for the boot when this message was logged, with some omissions none

Description Bojan Smojver 2024-05-07 23:32:16 UTC 
This is the problem that has been reported here:

https://bodhi.fedoraproject.org/updates/FEDORA-2024-b5624d3dd9

Intermittently, when the machine is resumed from suspend (in my case T450s), there is a longer than usual delay before the unlock screen is presented.

The tell sign appears to be a message like this in the logs:
-----
May 04 15:04:55 gdm[1137]: Gdm: Child process -1163 was already dead.
-----

Attaching the full log of that boot.

Reproducible: Sometimes

Steps to Reproduce:
1. Resume from suspend.
2. Wait for unlock screen.
Actual Results:  
Slight delay (a few seconds).

Expected Results:  
Generally, unlock screen appears almost immediately on resume.
Comment 1 Bojan Smojver 2024-05-07 23:34:32 UTC 
Created attachment 2032041 [details]
journal for the boot when this message was logged, with some omissions
Comment 2 Aoife Moloney 2025-04-25 10:38:53 UTC 
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 3 Aoife Moloney 2025-05-16 08:20:12 UTC 
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.