[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#581756: keyboard-configuration: XKBOPTIONS does not properly propagate to xserver-xorg

On Sat, May 15, 2010 at 17:56:33 +0200, Petr Baudis wrote:

> On Sat, May 15, 2010 at 05:48:03PM +0200, Julien Cristau wrote:
> > On Sat, May 15, 2010 at 17:10:14 +0200, Petr Baudis wrote:
> > 
> > > > # 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..
> (I hope my config file is up to date, but I think it should be.)
> > 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.
> Thanks! Reboot is not a trivial matter for me on this machine,
> but the udevadm incantation did the trick nicely!
> So I suppose updating the comment in the config file and modifying the
> configuration script to do this after updating the configuration should
> be enough to fix the bug?
Just updating the comment.  Triggering udev from keyboard-configuration
doesn't really make sense (it's a layering violation;
keyboard-configuration shouldn't need to know what the users for this
configuration file are, whether X is installed, etc), so I think I'd
change the comment to recommend rebooting instead.  The X keyboard
layout can easily be changed at runtime with setxkbmap anyway, and the
udevadm incantation won't change the layout at the console.
Modifications of /etc/default/keyboard are probably not a routine task,
so I think it's ok to have them only take effect at the next boot.

> On Sat, May 15, 2010 at 05:51:25PM +0200, Cyril Brulebois wrote:
> > Petr Baudis <pasky@ucw.cz> (15/05/2010):
> > > And sure enough, I cannot use ctrl-alt-bksp in my X session to zap
> > > the X server, a rather important functionality.
> > 
> > You need to turn off the DontZap option, see xorg.conf(5).
> I do that already.  However, isn't that the default again now that xkb
> does not set the terminate option by default anymore?  If not, I think
> that's another bug - why would you still keep DontZap at on at this
> point?  And the keyboard-configuration setup would be highly misleading,
> not mentioning this requirement during the terminate option setup.
Yeah, DontZap is off by default, so no need to change this.


Attachment: signature.asc
Description: Digital signature

Reply to: