On Wed, 08 May 2024 at 03:48:21 +0000, unfathomabl...@protonmail.com wrote: > Latest upgrade from 2.74.6-2 to 2.74.6-2+deb12u1 broke input of Japanese > characters GTK programs (such as firefox, gedit etc).
For users of testing/unstable, this will be fixed as soon as I can, probably by version 2.80.1-1. Each GLib build takes around an hour, plus the time required for testing, so it is not possible to fix this instantaneously. For users of Debian 12 'bookworm', a test-build of a fix for this regression is available here: https://people.debian.org/~smcv/bug1070730/ (amd64 + i386 + source) I've contacted the security team about releasing this regression fix officially as 2.74.6-2+deb12u2, but that cannot be done without their permission. Debian 11 'bullseye' is in the same situation as Debian 12 'bookworm'. A test-build for that release is not yet available. I'll upload one when available, if the security team doesn't get back to me first. On Wed, 08 May 2024 at 10:10:48 +0200, Arne Nordmark wrote: > Another thing that might well be the same underlying problem: > > Using version 2.74.6-2+deb12u1, a Compose sequence like 'Compose " a' enters > nothing in gnome-terminal and emacs. > > Using version 2.74.6-2, the same sequence enters an "ä". All non-trivial input methods in GNOME involve ibus, so the Compose key and dead keys will also be affected by this regression. smcv
