Bug 1861836
Summary: | Polyinstantiation is ignored/bypassed in GNOME sessions | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Carlos Santos <casantos> |
Component: | systemd | Assignee: | Jacek Migacz <jmigacz> |
Status: | CLOSED ERRATA | QA Contact: | Frantisek Sumsal <fsumsal> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.2 | CC: | aboscatt, bnocera, ipedrosa, jamacku, lvrabec, mkolbas, mmalik, msekleta, pbhoot, pbrezina, pkoncity, plautrba, rmetrich, sbarcomb, systemd-maint-list, systemd-maint |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | sync-to-jira | ||
Fixed In Version: | systemd-239-72.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-05-16 09:07:15 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
Carlos Santos
2020-07-29 17:08:23 UTC
This issue seems to be somewhere between gdm, pam and systemd. Switching the component for systemd folks for their take on this. selinux-policy does not seem to be involved. Tested on RHEL9. I can confirm there is no poly-instantiation when login graphically. The pam_namespace module needs to be loaded somewhere by /etc/pam.d/systemd-user. Trying to add it as below makes gnome-shell crash: ~~~ ... session required pam_loginuid.so session required pam_namespace.so session include system-auth ~~~ Crash: ~~~ Jun 24 11:25:50 vm-poly9 gnome-shell[14801]: Failed to start X Wayland: Directory "/tmp/.X11-unix" is not writable Jun 24 11:25:50 vm-poly9 kernel: traps: gnome-shell[14801] trap int3 ip:7fa8e94e283f sp:7fffb950fa70 error:0 in libglib-2.0.so.0.6800.4[7fa8e94a6000+90000] Jun 24 11:25:50 vm-poly9 systemd[1]: Started Process Core Dump (PID 14836/UID 0). Jun 24 11:25:50 vm-poly9 systemd-coredump[14838]: Resource limits disable core dumping for process 14801 (gnome-shell). Jun 24 11:25:50 vm-poly9 systemd-coredump[14838]: [🡕] Process 14801 (gnome-shell) of user 1000 dumped core. Jun 24 11:25:50 vm-poly9 systemd[14693]: org.gnome.Shell: Main process exited, code=dumped, status=5/TRAP ~~~ However if I disable Wayland, it works fine, I get the polyinstantiation. So I would say the issue in on both sides: - systemd (for systemd-user PAM) - wayland (for the crash) (In reply to Renaud Métrich from comment #9) > However if I disable Wayland, it works fine, I get the polyinstantiation. > > So I would say the issue in on both sides: > - systemd (for systemd-user PAM) > - wayland (for the crash) FWIW, Wayland isn't a piece of software, it's a protocol implemented by a number of compositors, one of them being gnome-shell. The crash seems to happen in gnome-shell. I don't know if the crash is caused by it not being able to instantiate XWayland, but it would be nice to have a backtrace with debugging symbols from that (coredumpctl can help there). X Wayland is a X11 server that runs on top of Wayland compositors, so is not strictly required. fix merged to github main branch -> https://github.com/redhat-plumbers/systemd-rhel8/pull/354 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 (systemd 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:2985 |