Bug 2065901
| Summary: | gdm not landing the user in the new GNOME session after first login after a boot | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Ian Laurie <nixuser> | ||||
| Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Michael Boisvert <mboisver> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | CentOS Stream | CC: | bstinson, hdegoede, jwboyer, pekopec, pvlasin, rstrode, tpelka | ||||
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | gdm-40.1-13.el9_0.2 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 2068040 (view as bug list) | Environment: | |||||
| Last Closed: | 2022-05-17 12:47:25 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 2068040 | ||||||
| Attachments: |
|
||||||
|
Description
Ian Laurie
2022-03-19 07:01:16 UTC
OK I've done a bit of testing: I downgraded gdm from gdm-40.1-13.el9.x86_64 to gdm-40.1-12.el9.x86_64 and the problem went away. I upgraded back to gdm-40.1-13.el9.x86_64 and the problem came back. I once again downgraded to gdm-40.1-12.el9.x86_64 and the problem went away again. If you wait say 30 seconds after boot and then log in, does the problem still happen? It would also be useful if you could set Enable=true in the [debug] section of /etc/gdm/custom.conf , reboot, reproduce, and then post the output of # journalctl -b > full-unfiltered-journal-log.txt Created attachment 1867344 [details]
Log from last boot
To answer the first question, waitng a period of time, even 10 minutes, doesn't fix the issue.
Here is the rquested log file.
Thanks, so it looks like something in the login process is leading to a uevent getting triggered.
I think something like this should fix it:
@@ -712,2 +712,6 @@ udev_is_settled (GdmLocalDisplayFactory *factory)
g_list_free_full (devices, g_object_unref);
+
+ if (is_settled)
+ g_clear_signal_handler (&factory->uevent_handler_id, factory->gudev_client);
+
return is_settled;
I've posted an upstream fix here: https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/175
I've got a centos9 stream merge request here: https://gitlab.com/redhat/centos-stream/rpms/gdm/-/merge_requests/18
and a scratch build here: http://people.redhat.com/rstrode/2065901/
Can you give it a try and confirm it addresses the issue?
The scratch build gdm-40.1-14.el9.x86_64 has fixed the issue for me, thanks. I realize it is a much older version of gdm, but could this be related to BZ #2014820 by any chance? Ian, thanks for the confirmation. bug 2014820 is unrelated, though, I'll take a quick look at it, too. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (new packages: gdm), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:2393 *** Bug 2094924 has been marked as a duplicate of this bug. *** |