From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] EMERGENCY: X11 KEYBOARD MAPPING STOPPED WORKING!!!!
Date: Sun, 18 Jun 2023 11:05:40 +0100 [thread overview]
Message-ID: <10291814.nUPlyArG6x@lenovo> (raw)
In-Reply-To: <703e33a5-80fe-476e-dbb5-763ea5b2b848@verizon.net>
[-- Attachment #1: Type: text/plain, Size: 2729 bytes --]
On Sunday, 18 June 2023 02:42:18 BST Alan Grimes wrote:
> having extreme trouble typing this, haven't had to type qwerty in
> fifteen years, keyboard mapping I need went poof during recent update,
> rebooted for kernel 6.3,
>
> X11 is NOT recording logs to /var/log since last year. Console seemed
> to be barfing about not knowing what a dvorak is even though it is the
> only other ISO standard keyboard mapping.
In a consile you could try:
# loadkeys dvorak
> No way to access console barf
> from within X11, no idea where logs are if they exist.
I think console related logs will be in your syslog or dmesg, if this involves
errors from interaction with the kernel. Not sure anything else would be
recorded by default.
If you use ssdm as a DM look for ~/.local/share/sddm/xorg-session.log for X
session logs.
> here are my configs, 2010 version has:
> drwxr-xr-x 2 root root 4096 Mar 7 2020 xorg.conf.d
> -rw-r--r-- 1 root root 2490 Oct 21 2010 xorg.conf.good
>
> Section "InputDevice"
> Identifier "Keyboard0"
> Driver "kbd"
> Option "XkbLayout" "dvorak"
> EndSection
>
> Since that was too simple and made too much sense, they had to make it
> uglier...
> current active config:
>
> Section "InputClass"
> Identifier "keyboard-layout"
> MatchIsKeyboard "on"
> Option "XkbLayout" "dvorak"
> Option "XkbModel" "pc104"
> # Option "XkbOptions" "grp:caps_toggle"
> EndSection
>
>
> atg@tortoise ~ $ setxkbmap
> Error loading new keyboard description
> atg@tortoise ~ $
Try this:
$ setxkbmap -print -verbose 10
> still have package x11-apps/xinput-1.6.3 installed even
> tho eclean-dist wants it gone, must be error because no clue how x11 is
> supposed to work without it. =(
There was a news item three years ago about this change:
https://www.gentoo.org/support/news-items/2020-04-03-deprecation-of-legacy-x11-input-drivers.html
Try to set your keyboard layout manually to minimise typing errors:
setxkbmap -layout us -variant ,dvorak
Set in your make.conf:
INPUT_DEVICES="libinput"
Then run:
emerge -uaNDv --with-bdeps=y @world
emerge --depclean -v -a
revdep-rebuild -v -- -a
to bring your packages up to date.
Finally, revisit your xorg.conf, these days the configuration is in seperate
files under /etc/X11/xorg.conf.d/40-libinput.conf. Something like this ought
to work:
Section "InputClass"
Identifier "libinput keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "libinput"
Option "XkbLayout" "us"
Option "XkbVariant" ",dvorak"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-18 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <703e33a5-80fe-476e-dbb5-763ea5b2b848.ref@verizon.net>
2023-06-18 1:42 ` [gentoo-user] EMERGENCY: X11 KEYBOARD MAPPING STOPPED WORKING!!!! Alan Grimes
2023-06-18 10:05 ` Michael [this message]
2023-07-05 20:42 ` Alan Grimes
2023-07-05 22:27 ` Jigme Datse
2023-07-06 3:59 ` Andreas Fink
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=10291814.nUPlyArG6x@lenovo \
--to=confabulate@kintzios.com \
--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