Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This bug was initially created as a copy of Bug #1861836
I am copying this bug because:
The same issue is present on RHEL9
Description of problem:
When polyinstantiation is enabled and a user logs in via GDM, applications that
are started via systemd (e.g. gnome-terminal) do not run in the same namespace
of gnome-shell and therefore bypass the polyinstantiation.
Version-Release number of selected component (if applicable):
- gdm-3.28.3-29.el8.x86_64
- gnome-shell-3.32.2-14.el8.x86_64
- pam-1.3.1-8.el8.x86_64
- selinux-policy-3.14.3-41.el8_2.5.noarch
- gnome-session-3.28.1-8.el8.x86_64
- gnome-session-wayland-session-3.28.1-8.el8.x86_64
- gnome-session-xsession-3.28.1-8.el8.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Enable Wayland in /etc/gdm/custom.conf; optionally log in choosing a "X11
display server" session, in step 6.
2. Ensure that /etc/pam.d/gdm-* use pam_namespace.so
session required pam_namespace.so
3. Enable polyinstantiation of /tmp and $HOME in /etc/security/namespace.conf
$HOME $HOME/$USER.inst/ level
4. If SELinux is in use, enable polyinstantiation
# setsebool -P allow_polyinstantiation 1
5. Restart gdm
# systemctl restart gdm.service
6. Try to log in as an ordinary user. If Wayland was not disabled in step 1,
log in choosing a "X11 display server" session.
7. Open a gnome-terminal window and run
$ ps -eo pid,user,mntns,command --sort mntns | fgrep " $(id -nu) " | fgrep -e gnome-terminal-server -e gnome-session-binary -e 'systemd --user'
Actual results:
The namespace inode numbers of gnome-session-binary and gnome-terminal-server
are not the same. Example:
106296 casantos 4026531840 /usr/lib/systemd/systemd --user
106979 casantos 4026531840 /usr/libexec/gnome-terminal-server
106375 casantos 4026532604 /usr/libexec/gnome-session-binary
Expected results:
The namespace inode numbers of gnome-session-binary and gnome-terminal-server
should be the same. Example:
108479 casantos 4026531840 /usr/lib/systemd/systemd --user
108559 casantos 4026532604 /usr/libexec/gnome-session-binary
109178 casantos 4026532604 /usr/libexec/gnome-terminal-server
Since the processes started by systemd --user do dot run in the same namespace
of gnome-session-binary, the polyinstantiation of $HOME does not have effect.
Additional info:
The problem can be circumvented by adding a session init script that updates
the DBUS_SESSION_BUS_ADDRESS and DBUS_SESSION_BUS_PID environment variables.
Example:
# cat /etc/X11/xinit/xinitrc.d/99-override-message-bus.sh
eval $(dbus-launch --sh-syntax --exit-with-session)
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:6640