You are not logged in.
Dead keys don't work in Plasma Wayland. It happens with Qt applications in general, with LibreOffice, with Telegram... However they work in Firefox, Typora, Brave, Spotify, Obsidian...
It used to work fine, but I don't know if the problems started with the move to Plasma 6 (and Wayland) or later.
/etc/X11/xorg.conf.d/00-keyboard.conf
# Written by systemd-localed(8), read by systemd-localed and Xorg. It's
# probably wise not to edit this file manually. Use localectl(1) to
# update this file.
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "es"
EndSection
localectl
System Locale: LANG=es_ES.UTF.8
VC Keymap: es
X11 Layout: es
setxkbmap -print -verbose 10
Setting verbose level to 10
WARNING: Running setxkbmap against an Xwayland server
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: pc105
layout: es
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+es+inet(evdev)
geometry: pc(pc105)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+es+inet(evdev)" };
xkb_geometry { include "pc(pc105)" };
};
Last edited by sosonok (2024-04-13 15:13:41)
Offline
as far as i know if you use wayland you need to change keyboard layout in -> Plasma Settings - Keyboard
Offline
Yes, my language and layout are set there, too (same as before upgrading to Plasma 6 / Wayland).
Last edited by sosonok (2024-04-12 14:38:34)
Offline
I don't know if the problems started with the move to Plasma 6 (and Wayland) or later.
Have you been running plasma 5 on wayland or X11?
locale is C
localectl
The dead_keys themselve are part of the keyboard layout (no idea how to test for that on kwin_wayland, xev is proably insignificant …) but the dead key composition is locale dependent.
When you enter "`", does that immediately print the glyph or can you just not get to à this way (ie. `+a just prints a)?
Online
Hi, seth.
Yes, I've been running Plasma 5 on X11.
When I press "´" nothing happens, so yes: ´+a just prints a.
Offline
So the keymap is correct but the composition doesn't work what makes you locale settings very relevant.
localectl
locale
locale -a
Or it could just be a plasma/wayland bug
Online
Here it goes:
localectl
System Locale: LANG=es_ES.UTF.8
VC Keymap: es
X11 Layout: es
locale
LANG=es_ES.UTF.8
LC_CTYPE="es_ES.UTF.8"
LC_NUMERIC="es_ES.UTF.8"
LC_TIME="es_ES.UTF.8"
LC_COLLATE="es_ES.UTF.8"
LC_MONETARY="es_ES.UTF.8"
LC_MESSAGES="es_ES.UTF.8"
LC_PAPER="es_ES.UTF.8"
LC_NAME="es_ES.UTF.8"
LC_ADDRESS="es_ES.UTF.8"
LC_TELEPHONE="es_ES.UTF.8"
LC_MEASUREMENT="es_ES.UTF.8"
LC_IDENTIFICATION="es_ES.UTF.8"
LC_ALL=
locale -a
C
C.utf8
en_US.utf8
es_ES.utf8
POSIX
Offline
Ok, so the locale is completely unsuspicious.
Are you using a limited IM?
https://wiki.archlinux.org/title/Input_method
printenv | grep -E '(_IM|XMOD)'
I assume they work for Plasma/X11?
There's https://www.reddit.com/r/kde/comments/1 … t_working/
Does it help to
export XCOMPOSEFILE=/usr/share/X11/locale/es_ES.UTF-8/Compose
https://wiki.archlinux.org/title/Xorg/K … ompose_key
For
Qt applications in general, with LibreOffice, with Telegram... However they work in Firefox, Typora, Brave, Spotify, Obsidian
the most likely scenario is that gtk just uses ibus and side-steps the XIM failure (LibreOffice isn't exactly a Qt client) and exporting "GTK_IM_MODULE=xim" to them makes them fail on deadkeys likewise?
Online
Well... I'll try to keep it short...
Apparently I didn't have any input method configured / installed (is that possible?). The thing is that
printenv | grep -E '(_IM|XMOD)'
didn't return any result, so I installed ibus and configured it from Plasma Systemsettings, and now it works. So I've probably been using KDE like this for months and didn't notice it before because I don't usually write in Spanish in any of the affected applications.
But now I'm curious... I noticed that there is no such directory in my system:
/usr/share/X11/locale/es_ES.UTF-8/
Anyway, I'm marking the thread as solved. Thank you very much for your help.
Offline
There indeed isn't a spanish locale in https://archlinux.org/packages/extra/x86_64/libx11/
The default US Compose map would (still) provide that, so my theory is that w/o ~/.XCompose or XCOMPOSEFILE X1 just falls back to the US variant but plasma/wayland doesn't?
(If you're curious and since you've the locale installed … AHHHHHHH
LANG=es_ES.UTF.8
isn't a valid locale!
es_ES.UTF-8 is!
So your locale was broken all along.
Online
:facepalm:
Now it is really solved.
Thanks again.
Offline