Bug 1719361

Summary: Killing inactive user causes active session to fail [rhel-7.6.z]
Product: Red Hat Enterprise Linux 7 Reporter: RAD team bot copy to z-stream <autobot-eus-copy>
Component: xorg-x11-serverAssignee: Adam Jackson <ajax>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.7CC: ajax, alanm, jfindysz, mboisver, pbhoot, rstrode, yferszt
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1680120 Environment:
Last Closed: 2019-07-29 15:16:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1680120    
Bug Blocks:    

Description RAD team bot copy to z-stream 2019-06-11 15:19:06 UTC
This bug has been copied from bug #1680120 and has been proposed to be backported to 7.6 z-stream (EUS).

Comment 5 Ray Strode [halfline] 2019-06-14 16:07:35 UTC
I've put a signed hotfix up available here:

https://people.redhat.com/rstrode/1719361/

which should address the problem detailed in this case.  These builds are likely to be the same builds used in the next 7.6 z-stream batch update. 

The easiest way to install these packages is to do:

# wget https://people.redhat.com/rstrode/1719361/1719361.repo
# yum update 'xorg-x11-*' 'gdm*'

then reboot.

Comment 6 Ray Strode [halfline] 2019-06-14 16:09:11 UTC
I forgot one step in my instructions. Before doing anything else:

# cd /etc/yum.repos.d

Comment 7 Michael Boisvert 2019-06-17 15:20:22 UTC
Verified on gdm-3.28.2-12.el7_6.2 and xorg-x11-server-1.20.1-5.4.el7.

Comment 9 errata-xmlrpc 2019-07-29 15:16:32 UTC
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/RHBA-2019:1893