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


Groups > linux.debian.user > #226330 > unrolled thread

keyboard configuration stops working

Started byHenning Follmann <hfollmann@itcfollmann.com>
First post2020-08-20 15:20 +0200
Last post2020-09-08 15:30 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.debian.user


Contents

  keyboard configuration stops working Henning Follmann <hfollmann@itcfollmann.com> - 2020-08-20 15:20 +0200
    Re: keyboard configuration stops working David Wright <deblis@lionunicorn.co.uk> - 2020-09-08 05:40 +0200
      Re: keyboard configuration stops working Henning Follmann <hfollmann@itcfollmann.com> - 2020-09-08 15:30 +0200

#226330 — keyboard configuration stops working

FromHenning Follmann <hfollmann@itcfollmann.com>
Date2020-08-20 15:20 +0200
Subjectkeyboard configuration stops working
Message-ID<AFSE1-8qu-3@gated-at.bofh.it>
Hello,

I have a strange one here.
I do have in my /etc/default/keyboard this option line:

XKBOPTIONS="lv3:menu_switch,compose:ralt,terminate:ctrl_alt_bksp,ctrl:nocaps"

for some time this works fine. I am talking about the last option.
I do not want the caps lock, so I mapped it to ctrl.

But it forgets. I cannot describe it any other way.
Then I do a dpk-reconfigure again (say "no" when it comes to
if I want to keep the options), go edit the /etc/default/keyboard
to add ctrl:nocaps, and it works again. ... for a while.
Then it doesn't. I have ABSOLUTELY no idea why.

-H


-- 
Henning Follmann           | hfollmann@itcfollmann.com

[toc] | [next] | [standalone]


#226778

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2020-09-08 05:40 +0200
Message-ID<AMCE9-6aA-11@gated-at.bofh.it>
In reply to#226330
On Thu 20 Aug 2020 at 09:17:08 (-0400), Henning Follmann wrote:
> 
> I have a strange one here.
> I do have in my /etc/default/keyboard this option line:
> 
> XKBOPTIONS="lv3:menu_switch,compose:ralt,terminate:ctrl_alt_bksp,ctrl:nocaps"
> 
> for some time this works fine. I am talking about the last option.
> I do not want the caps lock, so I mapped it to ctrl.
> 
> But it forgets. I cannot describe it any other way.
> Then I do a dpk-reconfigure again (say "no" when it comes to
> if I want to keep the options), go edit the /etc/default/keyboard
> to add ctrl:nocaps, and it works again. ... for a while.
> Then it doesn't. I have ABSOLUTELY no idea why.

I'm not sure why you're doing things in that order.

You should edit /etc/default/keyboard to include the options
you want (which you can't get from the questions Debian asks,
then run   dpkg-reconfigure keyboard   and say YES.
After all, if you don't want to keep them, why bother to
type them in?)

Then, it's recommended that you reboot.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#226790

FromHenning Follmann <hfollmann@itcfollmann.com>
Date2020-09-08 15:30 +0200
Message-ID<AMLR8-4bE-5@gated-at.bofh.it>
In reply to#226778
On Mon, Sep 07, 2020 at 10:24:52PM -0500, David Wright wrote:
> On Thu 20 Aug 2020 at 09:17:08 (-0400), Henning Follmann wrote:
> > 
> > I have a strange one here.
> > I do have in my /etc/default/keyboard this option line:
> > 
> > XKBOPTIONS="lv3:menu_switch,compose:ralt,terminate:ctrl_alt_bksp,ctrl:nocaps"
> > 
> > for some time this works fine. I am talking about the last option.
> > I do not want the caps lock, so I mapped it to ctrl.
> > 
> > But it forgets. I cannot describe it any other way.
> > Then I do a dpk-reconfigure again (say "no" when it comes to
> > if I want to keep the options), go edit the /etc/default/keyboard
> > to add ctrl:nocaps, and it works again. ... for a while.
> > Then it doesn't. I have ABSOLUTELY no idea why.
> 
> I'm not sure why you're doing things in that order.

it really doesn't matter, does it?
You always end up with the same configuration file.

> 
> You should edit /etc/default/keyboard to include the options
> you want (which you can't get from the questions Debian asks,
> then run   dpkg-reconfigure keyboard   and say YES.
> After all, if you don't want to keep them, why bother to
> type them in?)
> 
> Then, it's recommended that you reboot.

That actually got me a bit further.
You really do not have to reboot. But you should run
setupcon

And here seems to be the inconsistency. It looks like
setup con is not always executed during boot or
when you login.

After i run setupcon manually everything is like I
expect it. I just don't know why it is not allways
called.

-H

-- 
Henning Follmann           | hfollmann@itcfollmann.com

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web