Summary: | Xorg should use a more unlikely key combination than Control-Alt-Backspace as the server zap key | ||
---|---|---|---|
Product: | xorg | Reporter: | Jason Spiro <jasonspiro4> |
Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED WORKSFORME | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | daniel, polyprograms, shirishag75 |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Jason Spiro
2007-04-02 14:06:39 UTC
I'm confirming requesting pressing twice or (even better) three times on Ctrl + Alt + Backspace to kill the server would do no harm to those seeing it as an emergency exit function, and would probably save most people from activating it by error. _Trying_ (when X isn't crashed) to show a modal box to explain the user what he did the first time and what will happen if he insists pressing these keys, with a cancel button or whatever would be _really nice_. Please, think about it. Distros can decide if C-A-BS is too easy, and make the "DontZap" option in xorg.conf the default behavior, as can admins. OpenSUSE has already done it. Please don't change the current keystroke combination that kills X. Now that Xorg trunk has server zapping disabled by default, distributors will probably package Xorg and leave zapping disabled by default. If they do so, then there will no longer be any need to fix this bug. On Sun, Oct 19, 2008 at 09:42:57AM -0700, bugzilla-daemon@freedesktop.org wrote: > Now that Xorg trunk has server zapping disabled by default -> WFM Please revert this change. I expect C-Alt-BS to work, so does everybody else who has ever used it. (In reply to comment #5) > Please revert this change. http://lists.freedesktop.org/archives/xorg-devel/2009-April/000626.html > I expect C-Alt-BS to work, so does everybody else who has ever used it. please, please, do not infer other peoples opinion from your personal opinion. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.