Shift+Backspace Kill X

[Lukas Sabota]

I'm running the latest Dapper x86.
If a remember correctly, the keystroke to kill X was alt-ctrl-backspace. If I press shift-backspace, X is killed. This is VERY frustrating, as those keys are easy to press on accident. This is my third attempt at filing this bug, because the last two times I tried to file it, I accidently killed my X server.

The keystroke to restart X should be alt-ctrl-backspace, and not shift-backspace.

PS: Is there any workaround in the meantime to disable keystrokes that kill X completely? I'm going crazy, I can't get anything done!

[Simon Law (sfllaw)]

The DontZap option for /etc/xorg.conf is supposed to disable that.
Please see the xorg.conf(5x) manpage.

Does that also stop S-Backspace from killing your system?

[Dennis Kaarsemaker (dennis)]

I'm 99% sure you're running XGL. This is an XGL feature. (Feature from
hell if you ask me, but it's a feature)

 status Rejected

[Lukas Sabota (punkrockguy318)]

Yes, I was running XGL. I had no idea, I changed my /etc/X11/X to Xgl and forgot to change it back. Sorry!

[Daniele Cruciani (daniele-smartango)]

not using xgl and I have this problem

[Daniele Cruciani (daniele-smartango)]

problem now exists

[Daniele Cruciani (daniele-smartango)]

I found this
http://gentoo-wiki.com/HOWTO_XGL/Troubleshooting#Shift_backspace
is a solution

[Bryce Harrington (bryce)]

Shift-Backspace is an XGL "feature", not an xorg bug, so closing as invalid.

[Martin Th. Fei (nimoth)]

I do think this is a bug because it has suddenly been enabled on my machine after upgrading from 9.04 to 9.10. I do not really have an idea of what XGL is but as far as I know I am using X. I have never actively installed XGL. Why is the shortcut suddenly enabled?

[Martin Th. Fei (nimoth)]

The easiest solution is xmodmap -e "keycode 22 = BackSpace BackSpace Terminate_Server" as explained here: http://ubuntuforums.org/showthread.php?t=202654&page=2

[Bryce Harrington (bryce)]

Martin, rather than reopen an old bug (which is almost certainly unrelated), you should file a new bug.