Bug 2192784
| Summary: | GDM (X in general) requires processes to be part of user's sessions (set up by pam_systemd) to be functional | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Renaud Métrich <rmetrich> |
| Component: | systemd | Assignee: | Michal Sekletar <msekleta> |
| Status: | CLOSED MIGRATED | QA Contact: | Frantisek Sumsal <fsumsal> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.7 | CC: | bwelterl, hdegoede, msekleta, rstrode, systemd-maint-list |
| Target Milestone: | rc | Keywords: | MigratedToJIRA, Reopened |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-21 12:28:46 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: | |||
|
Description
Renaud Métrich
2023-05-03 06:21:46 UTC
no pam_systemd / logind registration isn't optional for our shipped desktop environment. That's definitely not going to change. See also https://bugzilla.redhat.com/show_bug.cgi?id=1643928 Hi Ray, Assuming pam_systemd is not optional for Graphical User Interface, still, I wouldn't expect all graphical sessions to die when systemd-logind dies or restarts. Can we harden this? Renaud. well the error message in comment 0 is: systemd-logind: ReleaseControl failed: You are not in control of this session This suggests when logind is restarted, it forgot who the session controller is. So that would need to be fixed first. It's possible mutter and Xorg will need follow up fixes as well, not sure. GDM shouldn't need any changes at all. To be honest, I'm not sure trying to make the system resilient to important system services getting killed or otherwise becoming dysfunctional is that worthwhile an endeavor. There are a million ways an admin can kill or perturb things and make the system break. Having said that, I do believe logind heavily serializes its state, so there could be acting counter to its design here. We'll see what the systemd crew says. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |