Issues with Keyboard

PDA · 2025-10-22 02:18:15

I recently reinstalled Arch with KDE and even though the keyboard layout seems correct, typing "ç" gives me "ć" instead. It used to show up fine in the terminal, I had the "ç" there.

Then, while editing a file in Vim, quotes (") suddenly stopped working (which was weird, since they worked just a moment before). The same thing happened with “ã”, ê and “õ” — they just show the letters without any accent, as if those keys stopped existing in the terminal. (Edit: This problem I solved yesterday)

Now I have different problems in the terminal and the GUI, how could I solve this?

Last edited by PDA (2025-10-22 10:35:20)

seth · 2025-10-22 08:13:14

KDE on X11 or wayland?
Any https://wiki.archlinux.org/title/Input_method ?
*What* layout do you expect to be using?
(This is essentially/likely dead key composition? Or do you have those keys in your layout?)

LuxFerre · 2025-10-22 09:57:19

If I remember well, that would be the difference between one of the variants of "us" keyboard, I think between us altgr-intl and us intl. You probably want us intl.

PDA · 2025-10-22 10:40:06

Yes, I'm using the dead keys.

To make sure we are all in the same page, here is the setxkbmap -query command:

rules: evdev
model: pc105
layout: us

Wismill · 2025-10-22 10:47:05

@PDA If you are running a Wayland the setxkbmap command will not show you meaningful information. You should get the warning: “WARNING: Running setxkbmap against an Xwayland server”.

Can you provide your ~/.config/kxkbrc instead?

PDA · 2025-10-22 11:35:26

You are completely right, I get this warning.

[paulo@archlinux ~]$ cat ~/.config/kxkbrc
[Layout]
Use=true

seth · 2025-10-22 12:01:39

So assuming the setxkbmap output is (incomplete and) irrelevant but the deadkeys generally work but produce the wrong result:
Absent an IME this is (on X11) driven by the locale-sensitive XCompose table
Assuming KDE just uses that on wayland as well => check your locale (localectl; locale; locale -a) and see https://wiki.archlinux.org/title/KDE#Pl … e_settings

On top of that:

paulo@archlinux

Brazil? (And intending to use a Brazilian layout? There was some bug w/ the compose table a while ago…

Ceterum censeo: probably also test the behavior on X11 to rule out a bug in kwin_wayland

LuxFerre · 2025-10-22 13:07:12

PDA wrote:

Yes, I'm using the dead keys.
To make sure we are all in the same page, here is the setxkbmap -query command:
rules: evdev
model: pc105
layout: us

Try standard us intl instead of altgr(dead keys) intl.

seth · 2025-10-22 13:21:41

If you are running a Wayland the setxkbmap command will not show you meaningful information. You should get the warning: “WARNING: Running setxkbmap against an Xwayland server”.
You are completely right, I get this warning.

The setxkbmap output on wayland is borderline meaningless (but for xwayland clients) and the variant and options actually completely missing from that (partial?!) output.

PDA · 2025-10-22 13:57:41

Thanks for the pointers!

Yes, I’m in Brazil, but I’m using the us(intl) layout (I don’t use the br-abnt2 one). As I mentioned earlier, the dead keys work but produce the wrong characters (like ć instead of ç, though ã, á, and õ are fixed), so that is not the issue at all.

Now, I'm using the X11 and the "ç" is working fine, I'm with some issues now with lock screen but I'll take a look at the documentation to solve it.

Thanks guys!!

Wismill · 2025-10-22 14:22:30

This is really weird. I am not sure what’s wrong exactly, whether it’s Compose or the wrong layout.

What key sequences do you use to get the various characters you mentioned above?

Could you dump your keymap under X11 and Wayland:
- X11: xkbcomp -xkb $DISPLAY /tmp/x11.xkb
- Wayland: xkbcli dump-keymap --raw > /tmp/wayland.xkb (or wev -f wl_keyboard -M /tmp/wayland.xkb)

seth · 2025-10-22 14:41:33

Most US layouts have dead_cedilla on altgr+comma - are you using that or dead_acute (ie "´")?
Check your locale and

grep ç /usr/share/X11/locale/pt_BR.UTF-8/Compose

Edit: Brazilian stripes
https://bbs.archlinux.org/viewtopic.php?id=301265
https://bbs.archlinux.org/viewtopic.php?id=302112
https://bbs.archlinux.org/viewtopic.php?id=298417

Last edited by seth (2025-10-22 14:42:50)

PDA · 2025-10-24 12:27:47

As I mentioned in the previous message, I changed to the X11 and the ç worked fine

But when in Code-OSS or Firefox, the "ć" returned instead of "ç", I really don´t know how to do. I'm seriously considering buying another keyboard, but I'm afraid to have the same issues in specific apps.

In addition, X11 has lots of issues that even when I solve (screensaver bugs, low performance with almost no tasks, etc), they return in a system reboot (but it is a subject for another conversation)

seth · 2025-10-24 13:13:48

killall firefox; GTK_IM_MODULE=xim QT_IM_MODULE=xim firefox

better?
But we still don't know whether you're using an IM, whether your locale could be a problem and what input you expect to produce ç

Unless you start answering those questions, this is pretty much going nowhere.

LuxFerre · 2025-10-24 14:21:29

PDA wrote:

As I mentioned in the previous message, I changed to the X11 and the ç worked fine
But when in Code-OSS or Firefox, the "ć" returned instead of "ç", I really don´t know how to do. I'm seriously considering buying another keyboard, but I'm afraid to have the same issues in specific apps.
In addition, X11 has lots of issues that even when I solve (screensaver bugs, low performance with almost no tasks, etc), they return in a system reboot (but it is a subject for another conversation)

My vconsole.conf:

KEYMAP=us-acentos                                                                                                             
XKBLAYOUT=us                                                                                                                  
XKBMODEL=pc105                                                                                                                
XKBVARIANT=intl                                                                                                               
XKBOPTIONS=terminate:ctrl_alt_bksp

Altgr + , = ç.
' + c = ć.

seth · 2025-10-24 15:30:46

Altgr + , = ç.
' + c = ć.

is the us-intl + US locale behavior, but I suspect the OP is looking for '+c = ç what you'd get w/ https://gitlab.freedesktop.org/xorg/lib … type=heads

Arch Linux

#1 2025-10-22 02:18:15

Issues with Keyboard

#2 2025-10-22 08:13:14

Re: Issues with Keyboard

#3 2025-10-22 09:57:19

Re: Issues with Keyboard

#4 2025-10-22 10:40:06

Re: Issues with Keyboard

#5 2025-10-22 10:47:05

Re: Issues with Keyboard

#6 2025-10-22 11:35:26

Re: Issues with Keyboard

#7 2025-10-22 12:01:39

Re: Issues with Keyboard

#8 2025-10-22 13:07:12

Re: Issues with Keyboard

#9 2025-10-22 13:21:41

Re: Issues with Keyboard

#10 2025-10-22 13:57:41

Re: Issues with Keyboard

#11 2025-10-22 14:22:30

Re: Issues with Keyboard

#12 2025-10-22 14:41:33

Re: Issues with Keyboard

#13 2025-10-24 12:27:47

Re: Issues with Keyboard

#14 2025-10-24 13:13:48

Re: Issues with Keyboard

#15 2025-10-24 14:21:29

Re: Issues with Keyboard

#16 2025-10-24 15:30:46

Re: Issues with Keyboard

Board footer