It’s turned off by default in a lot of distros these days but it can be turned back on. It used to be that editing /etc/X11/xorg.conf was recommended but because file inclusions are a thing these days, it makes more sense to create a new file /etc/X11/xorg.conf.d/enable-killing-xserver.conf:
Then restart the X server (which, these days, is pretty much a reboot). Or, going through the x.org documentation archives, it looks like you could dispense with the config files and run setxkbmap -option"terminate:ctrl_alt_bksp" in a terminal session and that’ll do the same thing.
On Linux, if a graphical app does not crash from this, that is a rare exception.
On windows, if a graphical app crashes from that, that is an exception.
There used to exist a hotkey CTRL-ALT-BKSP for restarting your current X-Session, don’t know if this still exists
It’s turned off by default in a lot of distros these days but it can be turned back on. It used to be that editing /etc/X11/xorg.conf was recommended but because file inclusions are a thing these days, it makes more sense to create a new file /etc/X11/xorg.conf.d/enable-killing-xserver.conf:
Section "ServerFlags" Option "DontZap" "false" EndSection Section "InputClass" Identifier "Keyboard Defaults" MatchIsKeyboard "yes" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSectionThen restart the X server (which, these days, is pretty much a reboot). Or, going through the x.org documentation archives, it looks like you could dispense with the config files and run
setxkbmap -option "terminate:ctrl_alt_bksp"in a terminal session and that’ll do the same thing.I was thinking of that when I read this and was like. windows has something like this???
That is not an equivalent.
On Linux, if a graphical app does not crash from this, that is a rare exception.
On windows, if a graphical app crashes from that, that is an exception.