Package: xwayland
Version: 2:24.1.5-1
Severity: normal
Dear Maintainers,
Since a few days, I noticed that my Compose key (Multi_key) is not producing
diacritics characters anymore on some applications. Mainly Emacs, VSCode and
Discord.
I have to admit that I have absolutely no idea how this is handled in Wayland,
so I am posting here to try to sort out a bit this case. So, feel free to
redirect me to the proper package afterward !
I am using the GNOME desktop with mutter as graphical server and I use the usual
gnome-control-center application to set up the Compose key (in the 'Keyboard'
section).
It was working fine until last week but after my "Monday update" I noticed that
the Compose key was dysfunctional.
So, I would like to know if something has changed about the Compose key recently
and how it works (which data-buses are involved, what protocol, ...). Possibly,
what package could be related to this failure.
Thanks in advance !
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.15-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages xwayland depends on:
ii libc6 2.40-7
ii libdecor-0-0 0.2.2-2
ii libdrm2 2.4.123-1
ii libepoxy0 1.5.10-2
ii libgbm1 24.3.4-3
ii libgcrypt20 1.11.0-7
ii libgl1 1.7.0-1+b2
ii libpixman-1-0 0.44.0-3
ii libtirpc3t64 1.3.4+ds-1.3+b1
ii libwayland-client0 1.23.1-1
ii libxau6 1:1.0.11-1
ii libxcvt0 0.1.3-1
ii libxdmcp6 1:1.1.5-1
ii libxfont2 1:2.0.6-1+b3
ii libxshmfence1 1.3-1+b3
ii xserver-common 2:21.1.15-3
xwayland recommends no packages.
xwayland suggests no packages.
-- no debconf information
