Summary:
The Compose key is configured and works correctly across the system (terminal, editors, GTK apps, Firefox).
However, it does NOT work in Chromium when Chromium is running via Wayland.
If Chromium is forced to run under X11 (--ozone-platform=x11), Compose works immediately.
This indicates missing or incomplete compose / XIM / input method support in Chromium's Wayland input path.
System Environment:
- Hardware: Raspberry Pi 500
- OS: Raspberry Pi OS (Wayland session enabled)
- Desktop environment: default Wayfire / labwc
- Keyboard layout: US
- Compose key: Left Logo key (configured via "sudo raspi-config")
- Browser: Chromium (Pi OS default build, and tested with latest packages)
- Rendering backend: Wayland (default) and X11/XWayland (manual switch)
Compose configuration (~/.XCompose):
--------------------------------------------------
include "%L"
<Multi_key> <o>: "ö" U00F6
<Multi_key> <a>: "ä" U00E4
<Multi_key> <u>: "ü" U00FC
<Multi_key> <O>: "Ö" U00D6
<Multi_key> <A>: "Ä" U00C4
<Multi_key> <U>: "Ü" U00DC
<Multi_key> <s>: "ß" U00DF
--------------------------------------------------
Expected behavior:
Typing Compose + u should produce "ü" in all applications.
Observed behavior:
The Compose key works correctly in:
- terminals (xterm/kitty/gnome-terminal)
- editors
- GTK applications
- LibreOffice
- Visual Studio Code
- Firefox (Wayland) <-- works OK
- Any application running under X11
But in Chromium (Wayland):
- Compose sequences are ignored or generate incorrect characters.
Workaround:
When Chromium is forced to use X11, compose works immediately:
pkill chromium
chromium --ozone-platform=x11
This demonstrates that:
- The system Compose key configuration is correct
- XCompose is being processed correctly
- Chromium’s Wayland text input pipeline is bypassing or missing compose handling
Analysis:
Firefox implements text composition in a way that works under Wayland.
Chromium appears to bypass XCompose/XIM/compose tables when using Wayland text input.
This seems to be a Chromium Wayland IME / text input integration gap, not a distro config issue.
Request:
Please confirm whether Chromium on Wayland is intended to support compose key sequences,
and if so, whether the Wayland input method path can be aligned with Firefox / GTK behavior,
or whether a known workaround or environment configuration exists.
I can run tracing, debugging builds, or experiments if needed.
The Compose key is configured and works correctly across the system (terminal, editors, GTK apps, Firefox).
However, it does NOT work in Chromium when Chromium is running via Wayland.
If Chromium is forced to run under X11 (--ozone-platform=x11), Compose works immediately.
This indicates missing or incomplete compose / XIM / input method support in Chromium's Wayland input path.
System Environment:
- Hardware: Raspberry Pi 500
- OS: Raspberry Pi OS (Wayland session enabled)
- Desktop environment: default Wayfire / labwc
- Keyboard layout: US
- Compose key: Left Logo key (configured via "sudo raspi-config")
- Browser: Chromium (Pi OS default build, and tested with latest packages)
- Rendering backend: Wayland (default) and X11/XWayland (manual switch)
Compose configuration (~/.XCompose):
--------------------------------------------------
include "%L"
<Multi_key> <o>: "ö" U00F6
<Multi_key> <a>: "ä" U00E4
<Multi_key> <u>: "ü" U00FC
<Multi_key> <O>: "Ö" U00D6
<Multi_key> <A>: "Ä" U00C4
<Multi_key> <U>: "Ü" U00DC
<Multi_key> <s>: "ß" U00DF
--------------------------------------------------
Expected behavior:
Typing Compose + u should produce "ü" in all applications.
Observed behavior:
The Compose key works correctly in:
- terminals (xterm/kitty/gnome-terminal)
- editors
- GTK applications
- LibreOffice
- Visual Studio Code
- Firefox (Wayland) <-- works OK
- Any application running under X11
But in Chromium (Wayland):
- Compose sequences are ignored or generate incorrect characters.
Workaround:
When Chromium is forced to use X11, compose works immediately:
pkill chromium
chromium --ozone-platform=x11
This demonstrates that:
- The system Compose key configuration is correct
- XCompose is being processed correctly
- Chromium’s Wayland text input pipeline is bypassing or missing compose handling
Analysis:
Firefox implements text composition in a way that works under Wayland.
Chromium appears to bypass XCompose/XIM/compose tables when using Wayland text input.
This seems to be a Chromium Wayland IME / text input integration gap, not a distro config issue.
Request:
Please confirm whether Chromium on Wayland is intended to support compose key sequences,
and if so, whether the Wayland input method path can be aligned with Firefox / GTK behavior,
or whether a known workaround or environment configuration exists.
I can run tracing, debugging builds, or experiments if needed.
Statistics: Posted by mlehn — Sat Oct 25, 2025 10:25 pm