Bug 1680120
Summary: | Killing inactive user causes active session to fail | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Piyush Bhoot <pbhoot> | |
Component: | xorg-x11-server | Assignee: | Adam Jackson <ajax> | |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | high | |||
Version: | 7.7 | CC: | alanm, mboisver, rstrode, yferszt | |
Target Milestone: | rc | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | xorg-x11-server-1.20.4-6.el7 gdm-3.28.2-16.el7 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1719361 (view as bug list) | Environment: | ||
Last Closed: | 2019-08-06 12:42:44 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1719361 |
Description
Piyush Bhoot
2019-02-22 18:37:53 UTC
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 |