Wow.. This is "interesting". Compare this with bug #2007379, where we work around the problem which the now reversed upstream g-s-d commit tries to address. (I wasn't aware of this upstream move.)
im-config 0.55-1 is already in lunar-release. Can the fact that im- config now sets GTK_IM_MODULE=ibus be the reason why the upstream commit didn't work out well? Would that g-s-d commit possibly work for us with GTK_IM_MODULE unset? I think this is worth to investigate. At least the g-s-d commit is the right idea. As regards the recent im-config change, I suppose it's motivated in both jammy and Debian 12. (And also in lunar unless we figure out how to avoid the regression you describe in this bug.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: xsettings ibus commit broke text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
