Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #222186

Re: /etc/default/keyboard not loaded at startup

From gwinship <gwinship@protonmail.com>
Newsgroups linux.debian.user
Subject Re: /etc/default/keyboard not loaded at startup
Date 2020-05-03 08:10 +0200
Message-ID <A2fZ8-2L2-7@gated-at.bofh.it> (permalink)
References <zZwtr-6B0-1@gated-at.bofh.it> <zZJAl-673-1@gated-at.bofh.it> <A0Alj-506-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Thank both of you for your support. However, the dpkg-reconfigure method doesn not fix the issue. I will still have to run the
udevadm trigger --subsystem-match=input --action=change
command each time I enter a new session.
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. I also checked whether the localectl might interfere, but running localectl status outputs

   System Locale: LANG=en_US.UTF-8
                  LANGUAGE=en_US:en
       VC Keymap: uk
      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.
Cheers,
Felix


-‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, April 28, 2020 5:20 PM, David Wright <deblis@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.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

/etc/default/keyboard not loaded at startup gwinship <gwinship@protonmail.com> - 2020-04-25 19:10 +0200
  Re: /etc/default/keyboard not loaded at startup David Wright <deblis@lionunicorn.co.uk> - 2020-04-25 22:40 +0200
  Re: /etc/default/keyboard not loaded at startup Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-26 09:10 +0200
    Re: /etc/default/keyboard not loaded at startup David Wright <deblis@lionunicorn.co.uk> - 2020-04-28 17:30 +0200
      Re: /etc/default/keyboard not loaded at startup gwinship <gwinship@protonmail.com> - 2020-05-03 08:10 +0200
        Re: /etc/default/keyboard not loaded at startup David Wright <deblis@lionunicorn.co.uk> - 2020-05-03 23:00 +0200
        Re: /etc/default/keyboard not loaded at startup Celejar <celejar@gmail.com> - 2020-05-04 03:20 +0200

csiph-web