Bug 1659220

Summary: Ctrl+Alt+Backspace kills X server at GDM login screen
Product: Red Hat Enterprise Linux 7 Reporter: Joshua Hershey <joshua.hershey>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-15 07:32:33 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:
Attachments:
Description Flags
xorg.conf.d file that enables ctrl+alt+backspace none

Description Joshua Hershey 2018-12-13 20:21:50 UTC
Created attachment 1514189 [details]
xorg.conf.d file that enables ctrl+alt+backspace

Description of problem: 
After configuring Ctrl+Alt+Backspace to restart the X server, if you are at the GDM login screen it will terminate X instead of restarting X. The only way to resolve this issue is to login and do "sudo systemctl restart gdm"

Version-Release number of selected component (if applicable):
gdm-3.28.2-10.el7


How reproducible: If you have Ctrl+Alt+Backspace configured correctly, you can use it from GNOME or KDE to bring you back to the GDM login screen, but if you perform this action from GDM it will kill the X server but GDM will continue to be running.


Steps to Reproduce:
1. Copy the attached file into /etc/X11/xorg.conf.d/
2. Restart GDM
3. After you are at GDM, press Ctrl+Alt+Backspace to attempt to restart the X server, you will be presented with a black screen in which X will terminate.

Actual results:
the X server will crash and not automatically restart.

Expected results:
the X server will restart and you will be back at the GDM login screen.

Additional info:

Comment 4 RHEL Program Management 2021-03-15 07:32:33 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.