Bug 604018

Summary: CTRL-ALT-BACKSPACE broken
Product: [openSUSE] openSUSE 11.3 Reporter: Harald Koenig <koenig>
Component: X.OrgAssignee: Forgotten User Wum0mkMcd8 <forgotten_Wum0mkMcd8>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Factory   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Harald Koenig 2010-05-08 10:30:10 UTC
using CTRL-ALT-BACKSPACE to kill the Xserver is broken in serveral way (of course with Option       "DontZap"  "off"):

with these xorg.conf settings (german keyboard) it works
  Option       "XkbModel" "microsoftpro"
  Option       "XkbLayout" "de"
  Option       "XkbVariant" "nodeadkeys"

but with us keyboard it doesn't:
  Option       "XkbModel" "pc104"
  Option       "XkbLayout" "us"
  Option       "XkbVariant" "basic"


running "setxkbmap us" and/or "setxkbmap both" will stop C-A-D working.


running "xkbcomp :0 - > outfile" shows the difference:  

working (default de settings):

    key <BKSP> {
        type= "CTRL+ALT",
        symbols[Group1]= [       BackSpace, Terminate_Server ]
    };

non-working (e.g. after "setxkbmap de"):

    key <BKSP> {         [       BackSpace ] };



as a workaround I'm using the following option in xorg.conf right now which makes C-A-D work in *any* case, even after any "setxkbmap ..." : 

  Option       "XkbOptions"    "terminate:ctrl_alt_bksp"


but it would be nice if the xkb rules would get fixed ;-)
Comment 1 Stefan Dirsch 2010-05-08 13:36:52 UTC
> as a workaround I'm using the following option in xorg.conf right now which
> makes C-A-D work in *any* case, even after any "setxkbmap ..." : 
>
>  Option       "XkbOptions"    "terminate:ctrl_alt_bksp"

This is what we're now using as well (in /etc/X11/xorg.conf.d/90-keytable.conf).

> but it would be nice if the xkb rules would get fixed ;-)

In case you have a fix, please let me know. :-)

*** This bug has been marked as a duplicate of bug 576481 ***