Arch Linux

Hylass

Member

Registered: 2024-02-23

Posts: 6

[SOLVED]Dead keys suddenly started to not work on specific apps on KDE

[SOLUTION]: As below post said, i had a second layout/configuration that I was not aware of, I deleted it and it works now!
I want to remark that I have found several posts from multiple forums addressing the same issue. However, none of the fixes given there did work, including this arch forum post: the link
System: Arch linux, Wayland, KDE plasma.

In simple terms, dead keys are a keyboard layout feature for writing accented letters. ' + e = é, ` + e = è etc. I have been using this feature for months on my neovim. But for some reason, I am unable to to this now on some specific apps like alacritty, kitty (terminals), dolphin, KeepassXC and so on. However firefox works fine.

Issue:
When I try to write an accent symbol, such as ', on my terminal, nothing happens.
Expected result:
There should be a small indicator which shows dead key is being used. Pressing space gives the symbol itself, pressing a letter would give accented version of it.
There is still "something" there, since pressing enter once does nothing (for example spamming enter key on terminal with no commands given would give lines of [user@user]$, I don't know how to explain this). I was using this feature like just yesterday. I don't remember what I did exactly, (probably pacman -Syu and reboot), but it doesn't work now.

Here is output of

 xev - event keyboard 

after pressing ' and e.

KeyPress event, serial 28, synthetic NO, window 0x1200001,
    root 0x4f0, subw 0x0, time 6276936, (131,20), root:(1001,484),
    state 0x2000, keycode 48 (keysym 0xfe51, dead_acute), same_screen YES,
    XKeysymToKeycode returns keycode: 47
    XLookupString gives 2 bytes: (c2 b4) "´"
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: True

KeyRelease event, serial 28, synthetic NO, window 0x1200001,
    root 0x4f0, subw 0x0, time 6277024, (131,20), root:(1001,484),
    state 0x2000, keycode 48 (keysym 0xfe51, dead_acute), same_screen YES,
    XKeysymToKeycode returns keycode: 47
    XLookupString gives 2 bytes: (c2 b4) "´"
    XFilterEvent returns: False

KeyPress event, serial 28, synthetic NO, window 0x1200001,
    root 0x4f0, subw 0x0, time 6277590, (131,20), root:(1001,484),
    state 0x2000, keycode 26 (keysym 0x65, e), same_screen YES,
    XLookupString gives 1 bytes: (65) "e"
    XmbLookupString gives 1 bytes: (65) "e"
    XFilterEvent returns: True

KeyRelease event, serial 28, synthetic NO, window 0x1200001,
    root 0x4f0, subw 0x0, time 6277715, (131,20), root:(1001,484),
    state 0x2000, keycode 26 (keysym 0x65, e), same_screen YES,
    XLookupString gives 1 bytes: (65) "e"
    XFilterEvent returns: False

I want to note that, in a normal keyboard layout with no dead keys, pressing ' gives " ' " with 1 bytes, While in  one with dead key gives (See above) " ´ "  with 2 bytes. Which indicates that dead keys are there, since the symbol ' outputs as ´ .
I am not even sure if the above stuff would help debugging the issue.
How can I fix this? Can someone help me please? Thanks.

Last edited by Hylass (2024-11-03 12:16:18)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,933

Re: [SOLVED]Dead keys suddenly started to not work on specific apps on KDE

not work on some specific apps on KDE

I am unable to to this now on some specific apps like alacritty, kitty (terminals), dolphin, KeepassXC and so on. However firefox works fine.

System: Arch linux, Wayland, KDE plasma.

Does FF run a native wayland client or via xwayland?

Though the xev output lacks

KeyPress event, serial 28, synthetic NO, window 0x1200001,
    root 0x4f0, subw 0x0, time 6277590, (131,20), root:(1001,484),
    state 0x2000, keycode 0 ((keysym 0xe9, eacute), same_screen YES,
    XLookupString gives 0 bytes:  
    XmbLookupString gives 2 bytes: (c3 a9) "é"
    XFilterEvent returns: False

between press and release of the "e" what suggests it's rather not gonna work w/ xwayland.

1. is this also an issue in an X11 session?
2. setxbmap -print -query
3. https://wiki.archlinux.org/title/Xorg/K … tion_files

I asked that in the other thread but do you use some https://wiki.archlinux.org/title/Input_method ?

Last thing:
"state 0x2000" means this is a multi-layout setup and you're currently in the second layout - is that intended?
(We'll cross-reference that w/ the setxkbmap output)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc