Bug 1659220 - Ctrl+Alt+Backspace kills X server at GDM login screen
Summary: Ctrl+Alt+Backspace kills X server at GDM login screen
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gdm
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-13 20:21 UTC by Joshua Hershey
Modified: 2021-03-15 07:32 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-15 07:32:33 UTC
Target Upstream Version:


Attachments (Terms of Use)
xorg.conf.d file that enables ctrl+alt+backspace (292 bytes, text/plain)
2018-12-13 20:21 UTC, Joshua Hershey
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.