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.

Description of problem:
Killing inactive session with 

loginctl kill-session

causes active user to fail.

Version-Release number of selected component (if applicable):
gdm-3.28.2-11.el7.x86_64.rpm
systemd-219-62.el7_6.5.x86_64.rpm

How reproducible:
Always


Steps to Reproduce:
1) RHEL system with installed GNOME desktop (default installation, no special settings) 
2) please ensure, that you have two users - lets say tom und ben
3) log in in the desktop environment as user tom
4) switch desktop user to the user ben (the session of the user tom becomes inactive and runs further in the background)
5) please list the desktop sessions now with the following command:

loginctl list-sessions

6) please kill now the inactive desktop session of the user tom (the active desktop user is ben, the session of the user tom runs in the background)

loginctl kill-session 2 (where 2 is the id of the now inactive session of the user tom)

Actual results:
Active session gets stopped

Expected results:
Active session remain unaffected

Additional info:
On side note: I have noticed ssh session as well failing, but not everytime

I did a scratch build here: 

Task info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=21537234

with the above patch added.  didn't even need any backporting.

confirmed it fixes the problem.

mboisvert, can we get a qa ack?

so this is actually going to need a GDM side fix too.

the problem is that GDM will start a new login scree when it detects the user session exiting, even if the user session exits in the background.

We need to add some code to handle the background death case.

When testing this before, I must have mixed up which session number I was killing, and killed a non-graphical session in the background (or something)

Verified on: xorg-x11-server-1.20.4-6.el7 and gdm-3.28.2-16.el7. With two sessions, I was able to kill the "inactive" session without any interruption.

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, 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/RHSA-2019:2079