On Sun 03 May 2020 at 06:06:37 (+0000), gwinship wrote:
> Thank both of you for your support. However, the dpkg-reconfigure method 
> doesn not fix the issue.

I'm not certain what the issue is, beyond what is in the subject line.

> I will still have to run the
> udevadm trigger --subsystem-match=input --action=change
> command each time I enter a new session.

By session, I suppose you mean something to do with a Display Manager,
which I don't know anything about.

> I am aware that in the config it says that the /etc/default/keyboard settings 
> are applied. Nevertheless, each start-up I will have the US layout used on 
> all applications and terminal emulators.

Perhaps your DM immediately contradicts the settings; I don't know.

> I also checked whether the localectl might interfere, but running localectl 
> status outputs
> 
>    System Locale: LANG=en_US.UTF-8
>                   LANGUAGE=en_US:en

I've never had cause to set that. I'm not even certain what the main
dialect of English is. I presume you think it's en_GB.

>        VC Keymap: uk

I only see n/a here. Perhaps this is because Debian has its keyboard
configurations unified between VCs and X. "uk" looks suspect anyway.
Perhaps this is the cause of your XKBVARIANT diagnostic reported earlier.

>       X11 Layout: gb,de
>        X11 Model: pc105
>      X11 Options: grp:win_space_toggle
> before executing the udev command.
> I'd be very glad if there are any other suggestions on how to apply the 
> configuration at startup without restarting the kernel input system each time.

Perhaps if you explain what you actually want, someone here may help
you configure it.

> On Tuesday, April 28, 2020 5:20 PM, David Wright <deb...@lionunicorn.co.uk> 
> wrote:
> > On Sun 26 Apr 2020 at 10:00:37 (+0300), Andrei POPESCU wrote:
> > > On Sb, 25 apr 20, 16:39:24, gwinship wrote:
> > >
> > > > I added following configuration to my /etc/default/keyboard
> > >
> > > Hint: you can use 'dpkg-reconfigure keyboard-configuration' to get a
> > > text-mode wizard.
> >
> > I've found that odd things can happen if X is running when you use
> > this command. I can only suppose it's to do with how the system
> > switches between graphics and text modes. That's why I suggested
> > booting into a text-only system.
> >
> > > > XKBMODEL="pc105"
> > > > XKBLAYOUT="gb,de"
> > > > XKBVARIANT=""
> > > > XKBOPTIONS="grp:win_space_toggle"
> > > > BACKSPACE="guess"
> > > > however. This does not load at boot.
> > >
> > > What is "this" that doesn't load at boot? How do you check?
> > > As per your Xorg.log below the configuration is applied.
> > > [...]
> > >
> > > > The /var/log/Xorg.log is
> > > > [ 268.781] () Option "xkb_model" "pc105"
> > > > [ 268.781] () Option "xkb_layout" "gb,de"[ 268.781] (WW) Option 
> > > > "xkb_variant" requires a string value
> > > > [ 268.781] (**) Option "xkb_options" "grp:win_shift_toggle"
> >
> > All my /etc/default/keyboard files contain the line
> > XKBVARIANT=""
> > but I've never seen that warning. In fact, I have never seen the
> > Option "xkb_variant" line reflected in the Xorg log, presumably
> > because, on my systems, it's always empty. That goes for squeeze,
> > wheezy, jessie, stretch and buster.
> >
> > What I expect to see from:
> >
> > XKBMODEL="pc105"
> > XKBLAYOUT="us"
> > XKBVARIANT=""
> > XKBOPTIONS="lv3:ralt_switch,compose:caps,terminate:ctrl_alt_bksp"
> >
> > BACKSPACE="guess"
> >
> > is, for two keyboards:
> >
> > (II) config/udev: Adding input device DELL DELL USB Keyboard 
> > (/dev/input/event0)
> > () DELL DELL USB Keyboard: Applying InputClass "libinput keyboard catchall"
> > (II) Using input driver 'libinput' for 'DELL DELL USB Keyboard'
> > (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 31 paused 0
> > () DELL DELL USB Keyboard: always reports core events() Option "Device" 
> > "/dev/input/event0"
> > () Option "_source" "server/udev"(II) event0 - DELL DELL USB Keyboard: is 
> > tagged by udev as: Keyboard
> > (II) event0 - DELL DELL USB Keyboard: device is a keyboard
> > (II) event0 - DELL DELL USB Keyboard: device removed
> > () Option "config_info" 
> > "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:413C:2005.0001/input/input3/event0"
> > (II) XINPUT: Adding extended input device "DELL DELL USB Keyboard" (type: 
> > KEYBOARD, id 11)
> > () Option "xkb_model" "pc105"() Option "xkb_layout" "us"
> > () Option "xkb_options" 
> > "lv3:ralt_switch,compose:caps,terminate:ctrl_alt_bksp"
> >
> > and:
> >
> > () Logitech K520: Applying InputClass "libinput keyboard catchall"
> > (II) Using input driver 'libinput' for 'Logitech K520'
> > (II) systemd-logind: returning pre-existing fd for /dev/input/event12 13:76
> > () Logitech K520: always reports core events() Option "Device" 
> > "/dev/input/event12"
> > () Option "_source" "_driver/libinput"(II) libinput: Logitech K520: is a 
> > virtual subdevice
> > () Option "config_info" 
> > "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.2/0003:046D:C52B.0005/0003:046D:2011.0007/input/input25/event12"
> > (II) XINPUT: Adding extended input device "Logitech K520" (type: KEYBOARD, 
> > id 17)
> > () Option "xkb_model" "pc105"() Option "xkb_layout" "us"
> > () Option "xkb_options" 
> > "lv3:ralt_switch,compose:caps,terminate:ctrl_alt_bksp"

Cheers,
David.

Reply via email to