Fcitx deletes final letter of previous word when hit space and then disable command

[Swarup Dev]

Fcitx is an Input Method for typing many languages using scripts other than latin. It works well in many regards, but there is one serious issue. It is a problem that occurs with Fcitx in any app I've used it in-- gedit, TB, Libre Office. The issue is that when Fcitx is enabled and one is typing, then as we know, sometimes the need arises to disable Fcitx to type a few English words, and then again enable Fcitx to resume typing the other language. Well, what happens is that when one has typed a word in Fcitx which ends in a consonant, and then hits space to create a separation between the last word and the next word, then if at that point one does ctrl-space to disable Fcitx, the final letter of the previous word gets erased.

The reason I see this happening is that up to that moment, the line underneath the previous word's last letter is still there, indicating that although I've hit the space bar, Fcitx still hasn't let go of the previous word's last letter-- and so when I do ctrl-space, that last letter gets deleted. It doesn't happen with all words; if the last word ends in what is called an inherent "a"--which is very often the case in Hindi, Bengali, and Sanskrit-- then it happens. So for example if I type "arjun" and then hit space, by hitting space the keymap adds an inherent "a" to the end so it becomes "arjuna" whithout having to have typed the last "a". In that situation, having typed "arjun" and then hit space, if I then do ctrl-space to disable fcitx, the letter "n" of "arjun" gets deleted. This never happened when I was using scim, and it doesn't happen in ibus-- so I suspect it is an issue in Fcitx. Scim and ibus are not working properly in Ubuntu 14.04, so I have switched to Fcitx. This bug affects many users and needs to be repaired.

Thanks,
Swarup

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: fcitx-bin 1:4.2.8.3-3
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 13 14:03:56 2014
ExecutablePath: /usr/bin/fcitx
InstallationDate: Installed on 2014-04-24 (18 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: fcitx
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Aron Xu (happyaron)]

Let's ask upstream to have a look.

[Gunnar Hjalmarsson (gunnarhj)]

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.