You are not logged in.
Hello,
For the past two weeks, I've been having a problem with the greater and less symbols on my keyboard.
My 00-keyboard.conf generated with localectl file in the xorg.conf.d contains two layouts:
latam (spanish) layout with deadtilde variant and ara (arabic) layout
Previously I could type these two symbols by holding the right_alt+shift+z and right_alt+shift+x.
Running xmodmap -pke return that the x and z keys are assigned to the unicode characters U2039 and U2032 which are the left and right pointing angle quotation marks, and the unicode codes for the greater and less symbols are U003e and U2264
I've tried to create a .Xmodmap and modify these two keys and it works to a point. The problem is that with this file it adds the us layout alongside the other two layouts, which I don't want to.
I booted into a fresh debian installation on a virtual machine and everything works as expected
Is there any recent change in the keycode and keysyms in Arch?
Last edited by hisham.ahai (2021-10-26 14:34:35)
Offline
Online
As I expected
Offline
If you intend to "fix" this locally (idk what's right or wrong here at all)
I've tried to create a .Xmodmap and modify these two keys and it works to a point. The problem is that with this file it adds the us layout alongside the other two layouts, which I don't want to.
You mean xmodmap added another xkb layout??
Please post
setxkbmap -print -query, the used .Xmodmap and elaborate on how you invoke it (xinitrc etc.)
Online
Here is how xmodmap is set in my .xinitrc
usermodmap=$HOME/.Xmodmap
...
...
if [ -f $usermodmap ]; then
xmodmap $sysmodmap
fiRight now I don't have it set here is the output of
setxkbmap -print -query xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+latam+ara:2+inet(evdev)+group(alt_shift_toggle)" };
xkb_geometry { include "pc(pc105)" };
};
rules: evdev
model: pc105
layout: latam,ara
variant: deadtilde
options: grp:alt_shift_toggleLast edited by hisham.ahai (2021-10-25 21:31:55)
Offline
Sorry, I missed the last post.
Does xmodmap still presumingly add a layout?
Please still add a resulting setxkbmap -print -query and your xmodmap.
Also
if [ -f $usermodmap ]; then
xmodmap $sysmodmap
fi
is probably wrong. You're not loading the usermodmap when it exists, but the system modmap (or nothing at all, I suspect that to reset the keyboard)
Online
To be honest, I don't know if the problem still exist or no, because I manually edited the X keyboard layout to revert the commit as it is permanent between reboots and different keyboards. I guess it is not a perfect solution because I have to edit the file each time it recieves an update but soon I'll get a keyboard with a proper ISO layout
Offline
Okey, same issue but for me the option to get another keyboard is more or less what I have avoided for years. I do not wanto to carry a keyboard and the laptop everywhere.
Moyocoyani, Tloque Nahuaque.
Offline
Well, his immediate solution was to revert the "offending" patch (see #2, disc: I've no idea whether that change was right or wrong or a good or bad idea)
The last couple of posts revolved around "xmodmap created a 3rd keyboard layout" what seemed a bit odd, but is irrelevant to the original question.
Online
A few weeks ago, a Merge Request was created and merged, which reverts the previous changes about Less and Greater symbols being replaced with U2039 and U203A respectively. So, building and installing the xkeyboard-config repository should fix this issue. See how to do it here: https://gitlab.freedesktop.org/xkeyboar … transition
On Linux systems, the xkeyboard-config path is commonly /usr/share/X11/xkb, so when building you would need to specify the prefix to /usr (it defaults to /usr/local) with:
meson setup -D prefix=/usr buildand then install:
sudo ninja -C build installIt's recommended to save a backup of your current xekyboard-config path if something goes wrong.
Then, just set xkbmap to latam.
Offline