From: Alan Grimes <alonzotg@verizon.net>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] major problem with X keyborad.
Date: Sun, 9 Jun 2024 15:04:04 -0400 [thread overview]
Message-ID: <b5d88cc1-095e-da93-aa8e-6455e4239238@verizon.net> (raw)
In-Reply-To: b5d88cc1-095e-da93-aa8e-6455e4239238.ref@verizon.net
The standard control keys aren't working in X anymore, mainly the arrow
keys and normal edit buttons, workaround is to use the numpad. Keys are
functional as tested from normal linux console. Problem started when I
rebooted after the emptytree world build the other day due to the stupid
profile change....
I have to run this manually at x launch because xorg.conf stopped
honoring keymaps:
setxkbmap -layout us -variant dvorak
Once again, the penguins invent a new and innovative way to fail in a
way that I had not previously imagined possible....
--
You can't out-crazy a Democrat.
#EggCrisis #BlackWinter
White is the new Kulak.
Powers are not rights.
next parent reply other threads:[~2024-06-09 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b5d88cc1-095e-da93-aa8e-6455e4239238.ref@verizon.net>
2024-06-09 19:04 ` Alan Grimes [this message]
2024-06-09 22:23 ` [gentoo-user] major problem with X keyborad Michael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b5d88cc1-095e-da93-aa8e-6455e4239238@verizon.net \
--to=alonzotg@verizon.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox