On Sat, May 15, 2010 at 17:10:14 +0200, Petr Baudis wrote: > There seems to be a problem in propagation of XKBOPTIONS setup from > keyboard-configuration to Xorg. My /etc/default/keyboard is (not in sync > with debconf since I have slightly complex xkb setup): > > > # If you change any of the following variables and HAL and X are > > # configured to use this file, then the changes will become visible to > > # X only if HAL is restarted. In Debian you need to run > > # /etc/init.d/hal restart > > The above comment is wrong nowadays..
> > # The following variables describe your keyboard and can have the same > > # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options > > # in /etc/X11/xorg.conf. > > > > XKBMODEL="pc105" > > XKBLAYOUT="us,cz" > > XKBVARIANT=",ucw" > > XKBOPTIONS="grp:caps_switch,terminate:ctrl_alt_bksp" > > > > # If you don't want to use the XKB layout on the console, you can > > # specify an alternative keymap. Make sure it will be accessible > > # before /usr is mounted. > > # KMAP=/etc/console-setup/defkeymap.kmap.gz > > However, Xorg.log shows: > > > (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" > > (type: KEYBOARD) > > (**) Option "xkb_rules" "evdev" > > (**) Option "xkb_model" "pc105" > > (**) Option "xkb_layout" "us,cz" > > (**) Option "xkb_variant" ",ucw" > > (**) Option "xkb_options" "grp:caps_switch" > > And sure enough, I cannot use ctrl-alt-bksp in my X session to zap > the X server, a rather important functionality. > Did you reboot after changing /etc/default/keyboard? That file is read by /lib/udev/rules.d/64-xorg-xkb.rules on boot (or keyboard hotplug). 'udevadm trigger --subsystem-match=input --action=change' might be enough to trigger an event and re-read the configuration. Cheers, Julien
signature.asc
Description: Digital signature
