FS#73332 - Firefox rejects XCompose input with a unicode conversion error
Attached to Project:
Arch Linux
Opened by Timo Wilken (twilk) - Tuesday, 11 January 2022, 12:05 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 07 February 2022, 07:23 GMT
Opened by Timo Wilken (twilk) - Tuesday, 11 January 2022, 12:05 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 07 February 2022, 07:23 GMT
|
Details
Description:
I can't use the Compose key to input accented characters in Firefox. See steps to reproduce below. Additional info: * package version: extra/firefox 95.0.2-1 * upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1749151, but I can't reproduce this issue with upstream Firefox Steps to reproduce: Environment: Arch Linux, Plasma (KDE) shell and i3 WM under Xorg. I have set MOZ_USE_XINPUT=1, but without that environment variable, the behaviour is the same. My system locale is en_GB.UTF-8 except for LC_{MONETARY,MEASUREMENT}=fr_FR.UTF-8, but I can also reproduce this bug when running Firefox with {LANG,LC_ALL}=en_US.UTF-8 or {LANG,LC_ALL}=C. To reproduce: in Firefox, focus the address bar or a text input field on a website. then try to use the Compose key to type an accented character, e.g. <Compose> " o to type an ö. Actual results: The resulting character (ö) does not appear in the address bar or in the focussed text input field. Firefox prints the following message to stdout: ** (firefox:133515): WARNING **: 20:11:55.216: Error converting text from IM to UTF-8: Invalid byte sequence in conversion input Expected results: Firefox should have accepted the ö character, and it should have appeared in the address bar or the text input field that had focus, like other text. No other programs on my computer have the same problem, independent of their graphics toolkit. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Monday, 07 February 2022, 07:23 GMT
Reason for closing: Fixed
Additional comments about closing: 2022-01-11: A task closure has been requested. Reason for request: Workaround/solution found (unsetting GTK_IM_MODULE)
Monday, 07 February 2022, 07:23 GMT
Reason for closing: Fixed
Additional comments about closing: 2022-01-11: A task closure has been requested. Reason for request: Workaround/solution found (unsetting GTK_IM_MODULE)
Unsetting GTK_IM_MODULE for firefox works fine. As xim is apparently old and unsupported by lots of other software, I'd consider this solved.