Well, upstream claims that the issue is fixed in fcitx 4.2.8.4 with fcitx-m17n 0.2.3, while we have 4.2.8.3 respective 0.2.1 in Ubuntu/Debian.
https://github.com/fcitx/fcitx/issues/153
Seems like an upgrade to latest upstream versions would fix this bug.
Well, upstream claims that the issue is fixed in fcitx 4.2.8.4 with fcitx-m17n 0.2.3, while we have 4.2.8.3 respective 0.2.1 in Ubuntu/Debian.
https:/ /github. com/fcitx/ fcitx/issues/ 153
Seems like an upgrade to latest upstream versions would fix this bug.