#1137086 Wayland: Spanish layout loads without dead keys in all Qt/KDE apps (Konsole, Dolphin, Telegram), but works in Firefox.

Package:
systemd
Source:
systemd
Description:
system and service manager
Submitter:
Santiago José López Borrazás
Date:
2026-05-19 15:15:01 UTC
Severity:
normal
#1137086#5
Date:
2026-05-19 10:37:56 UTC
From:
To:
Dear Maintainer,

Summary:

systemd-localed does not correctly apply the X11 keyboard layout under Wayland on Debian SID.
As a result, KDE Plasma 6 applications (Qt6, Qt5, XWayland) receive a keyboard layout without dead keys, even when the configured layout is es with no variant.
Firefox and Thunderbird (native Wayland) work correctly.

This strongly suggests that systemd-localed is not providing the correct layout information to the compositor (KWin/Wayland), or that the layout is not being exported through the usual interfaces (org.freedesktop.locale1).

Description

On Debian SID, using KDE Plasma 6.6.5 under Wayland, the Spanish keyboard layout (es) is not applied correctly by systemd-localed.
Although the system locale is correct (es_ES.UTF-8) and localectl status reports the expected layout, all Qt/KDE applications behave as if the layout variant were nodeadkeys.

This affects:

    Konsole (Qt6)

    Dolphin (Qt6)

    Kate (Qt6)

    Telegram Desktop (Qt5/XWayland)

    Any Qt or XWayland application

However:

    Firefox (Wayland native)

    Thunderbird (Wayland native)

receive dead keys correctly.

This indicates that the issue is not KDE-specific, but rather that systemd-localed is not exporting the correct keyboard layout to the Wayland session.

Steps to reproduce

    Install Debian SID with KDE Plasma 6.6.x.

    Log into a Wayland session.

    Configure keyboard layout:

        Only one layout: Spanish (es)

        No variant

    Restart the session.

    Open any Qt/KDE application (Konsole, Dolphin, Kate).

    Try typing accented characters: á, é, í, ó, ú.

Actual result

Dead keys do not work in Qt/KDE/XWayland applications.
They do work in Firefox and Thunderbird.

System information

Locale:

LANG=es_ES.UTF-8
LANGUAGE=es
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=

localectl:

System Locale: LANG=es_ES.UTF-8
VC Keymap: (unset)
X11 Layout: es
X11 Model: pc105

systemd-localed logs:

systemd-localed.service: Deactivated successfully.
(no errors)

kxkbrc:

[Layout]
LayoutList=es
Use=true

Additional notes:

systemd-localed starts and stops cleanly, but does not appear to apply the keyboard layout to the Wayland session.

Removing kxkbrc, regenerating layouts, reinstalling systemd, and resetting Polkit rules does not fix the issue.

The issue persists across reboots and new user accounts.

This behavior does not occur under X11.

This behavior does not occur in Firefox/Thunderbird, which bypass systemd-localed.

Conclusion:

systemd-localed appears to fail to export or apply the correct keyboard layout under Wayland on Debian SID.
This results in KDE Plasma 6 receiving a layout without dead keys, even though the system configuration is correct.

This issue affects all Qt/KDE/XWayland applications and is reproducible on a clean Debian SID installation.

Cheers!

This means the layout is not being applied correctly through systemd-localed to the compositor.

#1137086#10
Date:
2026-05-19 15:13:36 UTC
From:
To:
The problem is solved. Is regenerate locale and directory of locales.

Is solved.