Bug 1924079
| Summary: | GdmDisplay: Session never registered, failing | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Michal Odehnal <modehnal> | ||||
| Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Michal Odehnal <modehnal> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 8.4 | CC: | apjagtap, hdegoede, nate.johnston, rstrode, tpelka, tpopela | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | gdm-40.0-26.el8 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-05-16 08:27:13 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: | |||||||
| Deadline: | 2023-02-27 | ||||||
| Attachments: |
|
||||||
|
Description
Michal Odehnal
2021-02-02 14:48:44 UTC
It seems it was not fixed together with the 2004170, the 'Gdm: GdmDisplay: Session never registered, failing' is still there: [test@zalman1-vm6-c-01 ~]$ date Mon Oct 18 17:16:38 CEST 2021 [test@zalman1-vm6-c-01 ~]$ systemctl start gdm [test@zalman1-vm6-c-01 ~]$ systemctl stop gdm [test@zalman1-vm6-c-01 ~]$ systemctl status gdm ● gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled) Active: inactive (dead) since Mon 2021-10-18 17:16:54 CEST; 3s ago Process: 86812 ExecStopPost=/usr/bin/bash -c for f in /run/systemd/sessions/*; do [ -f $f ] && /usr/bin/fgrep -q SERVICE=gdm $f && loginctl terminate-session $(basename $f); done (code=exited, status=0/SUCCES> Process: 86246 ExecStart=/usr/sbin/gdm (code=exited, status=0/SUCCESS) Main PID: 86246 (code=exited, status=0/SUCCESS) Oct 18 17:16:47 zalman1-vm6-c-01.tpb.lab.eng.brq.redhat.com systemd[1]: Starting GNOME Display Manager... Oct 18 17:16:47 zalman1-vm6-c-01.tpb.lab.eng.brq.redhat.com systemd[1]: Started GNOME Display Manager. Oct 18 17:16:54 zalman1-vm6-c-01.tpb.lab.eng.brq.redhat.com systemd[1]: Stopping GNOME Display Manager... Oct 18 17:16:54 zalman1-vm6-c-01.tpb.lab.eng.brq.redhat.com gdm[86246]: Gdm: GdmDisplay: Session never registered, failing Oct 18 17:16:54 zalman1-vm6-c-01.tpb.lab.eng.brq.redhat.com systemd[1]: gdm.service: Succeeded. Oct 18 17:16:54 zalman1-vm6-c-01.tpb.lab.eng.brq.redhat.com systemd[1]: Stopped GNOME Display Manager. [test@zalman1-vm6-c-01 ~]$ rpm -q gdm gdm-40.0-15.el8.x86_64 Created attachment 1932117 [details]
fix for the issue
this should fix the warning issue. I think the hash table problem was fixed a while back already, IIRC.
Setting ITM to the end of the non-exception period. Feel free to reign it in as required... 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 (gdm bug fix and enhancement update), 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-2023:2779 |