Problem at typing latest letter.

Bug #840823 reported by Jinkyu Yi
126
This bug affects 24 people
Affects Status Importance Assigned to Milestone
Unity
Confirmed
Undecided
Unassigned
ibus (Ubuntu)
Confirmed
Unknown
ibus-hangul (Ubuntu)
Confirmed
Undecided
Unassigned
unity (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

There are 2 bugs.

First, When typing hangul, latest typing letter didn't blocked(I mean, not in the black box).

Second, it seems latest typing letter following right left side of cursor.
ex 1)press space(shown [ ]) after type.
가나다[ ] > 가나[ ] 다
ex 2)press left arrow key(shown <-) after type
가나다<- > 가다나

It was not happened at previous versions.
The version making this bug is : IBus 1.3.99.20110818, ibus-hangul 1.2.99(package info)

Revision history for this message
Keechang Kim (keechang) wrote :

I also experience this problem since I upgraded to Oneiric (Beta).

When a space is pressed while inputting Korean, the space appears just "before" the last character (it should appear after the last character).

Changed in ibus-hangul (Ubuntu):
status: New → Confirmed
Revision history for this message
rnsmith2 (rnsmith2) wrote :

This not only effects typing in Korean through ibus, but also typing in Esperanto.

Example attempting to type in Esperanto (plena - m17 method) the word `ĉielo', I get `iĉleo', where both c and e allow for changes based on the following letter, the next letter after that letter has been selected ends up to the left of the start point.

Revision history for this message
cocoon (sckang0722) wrote :

 i have same problem.
Also IBus indicator does not show.
it's very critical problem for Korean.

Revision history for this message
HAN WONJOON (wonjoon-han) wrote :

i have same problem

'가나다[ ]' > '가나[ ]다'

Revision history for this message
Daniel Lee (gumgak) wrote :

I had the same problem before.
somehow I fixed the bug. but I can't remember how I did it.

few days ago Ubuntu was upgraded to 11.10, then the problem came back.

Revision history for this message
Seunghoon Park (pclove1) wrote :

It seems that this bug doesn't occur using 'Gnome' or 'Unity 2D' instead of 'Unity'.

reference:
http://myubuntu.tistory.com/654

Revision history for this message
Seunghoon Park (pclove1) wrote :

unity was confirmed since this bug occurs in other languages too.

reference:
https://bugs.launchpad.net/bugs/876364

Changed in unity:
status: New → Confirmed
Seunghoon Park (pclove1)
affects: unity → unity (Ubuntu)
affects: ibus → ibus (Ubuntu)
Revision history for this message
Jmadero (jmadero) wrote :

not sure if this is the same problem but I cannot even activate my language (Telugu) using the ibus properties, instead I can only enable it using the keyboard layout properties of unity which is not sufficient as there is no Telugu-itrans option which is the input method that I use. Should I report a new bug for this?

Revision history for this message
Kevin (kevinshlee) wrote :
Download full text (3.3 KiB)

Could anyone in charge of this bug please take it more seriously as now Ubuntu 11.10 is almost unusable by any people need to type Korean alphabet that is Hangul.

It's not only spacing issue but also the matter of positioning the last character of the word correctly.
Here are examples of what I mean by the last char positioning issue.
If I type
abc
then press the enter key, I expect to have
abc
<=The cursor appears here in the next line.
It's clear to everyone, and I get it correctly as I described.

Now I type some Korean characters
가나다
then press the enter key, I also expect to have
가나다
<=The cursor appears here.

However, what I actually get is different. The difference also differs depending on applications.

Firstly in gedit, it becomes
가나
다<=The last character appears in the next line.

In LibreOffice,
가나다
다<=The last character appears again in the next line in addition to the correctly positioned one in the first line. So I have one duplicate.

In Pidgin Internet Messenger,
가나<=These are correctly sent to the person with whom I'm chatting.
다<=The last character stays in the input box.
So it's like, if I type "hello" then press enter, my friend gets 'hell' instead.
I do of course not get it when I type English. It's just an example of what kind of situation I might have with the issue.

Apart from this issue, I also have spacing issue as already mentioned by the people above.
e.g.) typing 가나다 and pressing the spacebar key doesn't produce
'가나다 ' (가나다[ ] <- one space character at the end of the line).
but
'가나 다' (가나[ ]다 <- onc space character in between the last character and the second last one).

Obviously no one can live with these issues. I don't think anyone can. So I temporarily chose nabi as the input method to type Hangul. Well, it had worked fine at first but I discovered some issues with it too. Some people say that nabi doesn't work well with LibreOffice. I haven't tested it though. What I found is probably more serious. It doesn't work with the unity launcher. If I press the super key to get the launcher and type any alphabet character, nothing appears. To make it work, I have to quickly press the super key twice to make the launcher disappear and appear again. I can type after that, yet it doesn't completely solve the problem. Typing works but barely. I have to type the same character several times to have it. So, for instance, to have 'fire' to get 'firefox', I have to type like ffiiireeeee then I can get 'fire' appeared on the launcher.

Due to all the problems I mentioned above, Ubuntu 11.10 Oneiric is almost unusable by any people need to type Hangul, the Korean alphabet.

Yeah, you can use Unity 2D or GNOME Shell instead, but none of these is a proper solution to the issue. I rather format and re-install Ubuntu 11.04 Natty than using Unity 2D or GNOME Shell. I, at least, tried Unity 2D but it was terrible as I need a proper compiz support to have the productivity that Ubuntu offers.

So please take care of the issue or if it is hard to be solved any time soon, please let us have the old working version in Ubuntu Natty for the Oneiric users.

I understand that the issue might not be solved easily and definitely much more...

Read more...

Revision history for this message
Seunghoon Park (pclove1) wrote :

I agree with Kevin.

Changed in ibus (Ubuntu):
status: Unknown → Confirmed
Revision history for this message
PrasannaSP (prasannasp) wrote :

Having the same problem with Kannada language too. iBus cries to work with Unity..

Changed in unity:
status: New → Confirmed
Revision history for this message
Junise Safvan (junisesafvan-gmail) wrote :

I am also having the same problem with malayalam phonetic 'swanalekha'

Revision history for this message
David Gómez (dabisu) wrote :

Hi, i'm also having this problem. I was using hangul input in 11.10 without problems. But today i was trying to write some hangul in a message and noticed this "space" problem. As the bug reporter says, an unwanted space is added before the last typed hangul character, making it very difficult to type in hangul :(. This was no happening in 11.10 so i guess a recent ibus update caused this regression.

Revision history for this message
David Gómez (dabisu) wrote :

Sorry, i meant in my previous comment 11.04. That's is, after upgrading to 11.10 ibus-hangul doesn't works as expected.

Revision history for this message
Emanuel Rietveld (codehotter) wrote :

Temporary Workaround: unset IBUS_ENABLE_SYNC_MODE

Open ~/.bash_aliases in a text editor (create it if it doesn't exist)

add

unset IBUS_ENABLE_SYNC_MODE

to the bottom.

You have to log out and back in.

Revision history for this message
Emanuel Rietveld (codehotter) wrote :

And by ~/.bash_aliases in the previous comment I mean $HOME/.bash_profile
(sorry)

Revision history for this message
David Gómez (dabisu) wrote :

I just tested that workaround. Chrome and gedit don'have the unwanted space problem. But terminal emulator still shows the problem.

Revision history for this message
Kevin (kevinshlee) wrote :

Thanks Emanuel Rietveld.

I've just tested it. It works for gedit yet NOT for other ones like LibreOffice and Pidgin.
I don't have .bash_profile so added 'unset IBUS_ENABLE_SYNC_MODE' to the $HOME/.bashrc file.

Revision history for this message
Kevin (kevinshlee) wrote :

just tested again by creating .bash_profile although I didn't think it would make any difference.

No difference. LibreOffice and Pidgin still have the problem and as David Gómez said, the terminal has it too.

Revision history for this message
Kevin (kevinshlee) wrote :

It's weird. After I left the comment above, I turned off my PC and turned it on about 10 hours later and found even gedit has the problem. So I created .bash_profile again (I only left that workaround in the .bashrc file) then logged out and in. I opened the gedit and tested. It seemed fine so I closed gedit and opened firefox and tried to write in Korean. It has the problem (I didn't test it before so I'm not sure whether Emanuel's workaround solved it on Firefox or not). So I opened gedit again to write here and to copy & paste into the browser. This time gedit has the problem too.

Despite the fact that I really like Oneiric with its newly added features and its look, I feel like I should re-install Ubuntu 11.04 Natty.
This bug is so annoying. Is Oneiric designed for only those who speak English but no other languages? I don't think it is but it looks like it is.
How come unity on Oneiric is so unstable than Natty's?

Revision history for this message
David Gómez (dabisu) wrote :

One thing is for sure. They wrote in big letters "support for Asian languages in Unity" for the 11.10 release. But it seems nobody in Canonical did some basic testing with korean. A now we have a broken 11.10 for korean. And no fixes. For me this bug should be categorized as "Critical", but, what do i know? Still in "Undecided" state and nobody cares.

Wonder why Ubuntu is not popular in Korea? :(

Revision history for this message
Jinkyu Yi (jincreator) wrote :

This bug is happen when IBUS_ENABLE_SYNC_MODE is turned on.
I think using .bash* can't work because it looks like Unity turn on this variable, but not at system-wide.
So it affect when launch program using Unity.
If you open termianl with Ctrl+Alt+T or using another launcher and type env, there's no IBUS_ENABLE_SYNC_MODE.

I simply modify Unity to not set IBUS_ENABLE_SYNC_MODE(lp:jincreator/unity) and no problem at every application launched at Unity.
But turn off IBUS_ENABLE_SYNC_MODE makes problem at Unity Search Bar.
It looks just unset IBUS_ENABLE_SYNC_MODE is not a solution.

I think it's the problem of iBus, not Unity.
By the way, has anyone know what IBUS_ENABLE_SYNC_MODE is?

Revision history for this message
David Gómez (dabisu) wrote :

Please read the previous messages. Unsetting IBUS_ENABLE_SYNC_MODE solve the problem in some applications and some configurations. It doesn't seem to be deterministic at all.

An the reason i think it's a Unity problem in that IBus korean input in 11.10 under different window managers works ok (i have tested XFCE and Openbox).

Revision history for this message
Sergej Nikolaev (kinolaev) wrote :

This bug is fixed on fedora (https://bugzilla.redhat.com/show_bug.cgi?id=753781) with this patch:
https://github.com/fujiwarat/ibus/commit/a8c21dd867f4a9e1c37cae4f6509af1491c5fc96
How can I apply this in Ubuntu?
[sorry for my english]

Revision history for this message
Alex Lee (alexlee) wrote :

I submitted a report for what I think is the same bug:
https://bugs.launchpad.net/ubuntu/+source/ibus-m17n/+bug/886568

Even though this bug is marked a duplicate of https://bugs.launchpad.net/bugs/880876 I'm pretty sure it isn't just a Unity issue. I have been encountering this problem when using XFCE (Xubuntu 11.10).

Following Sergej's comment (#24), I decided to try out fujiwarat's change,
https://github.com/fujiwarat/ibus/commit/a8c21dd867f4a9e1c37cae4f6509af1491c5fc96

And to answer Sergej's question, here's how I did it (not sure if this is the best way but it worked):

# Fetch fujiwarat's latest code
~$ git clone https://github.com/fujiwarat/ibus.git

# Get the source (from Precise) and extract it
~$ wget http://archive.ubuntu.com/ubuntu/pool/main/i/ibus/ibus_1.4.0.orig.tar.gz
~$ wget http://archive.ubuntu.com/ubuntu/pool/main/i/ibus/ibus_1.4.0-1ubuntu2.debian.tar.gz
~$ tar -zxvf ibus_1.4.0.orig.tar.gz
~$ cd ibus-1.4.0
~/ibus-1.4.0$ tar -zxvf ../ibus_1.4.0-1ubuntu2.debian.tar.gz

# Copy in the updated client/x11/main.c and build
~/ibus-1.4.0$ cp ../ibus/client/x11/main.c ./client/x11/main.c
~/ibus-1.4.0$ sudo apt-get build-dep ibus
~/ibus-1.4.0$ dpkg-buildpackage -b -tc -us -uc

Assuming you have all the dependencies in place it should build ok. I installed all the generated deb files and logged out and back in. All the problems I had been encountering with ibus were then resolved (including a separate issue where the compose key had stopped working). So this seems to confirm that Sergej is right about the patch that fixes the bug.

Revision history for this message
Dominik Wujastyk (wujastyk) wrote :

Thanks, Alex (#25). I followed your procedure, and it seems to have fixed my ibus / m17n keyboarding too. Great!

Very grateful to you for the step-by step procedure.

Best,
Dominik

Revision history for this message
Dominik Wujastyk (wujastyk) wrote :

With one of my laptops, I applied ibus 1.4.0, as described in #25. I did so while logged in with a Gnome (gnome-shell) session. Then I logged out and logged back in, but chose Ubuntu (i.e., unity) straight away. The ibus input problem was still there. Very frustrating. But then I rebooted the machine, and logged back into unity, and the ibus input problem was gone.

So it appears that sometimes it isn't enough to just restart X, or logout-in, but one must actually reboot.

Dominik

Revision history for this message
David Gómez (dabisu) wrote :

Is fujiwarat code going upstream?

Revision history for this message
Dominik Wujastyk (wujastyk) wrote :

I was wondering the same thing. But I don't know how to nudge this process along.

Dominik

Revision history for this message
Kevin (kevinshlee) wrote :

It's weird. I followed Alex's instructions https://bugs.launchpad.net/ubuntu/+source/ibus-hangul/+bug/840823/comments/25 last night, and it worked fine after restarting Ubuntu. Later I checked it again and found that it does not work anymore. Does anyone have the same problem?

Revision history for this message
Dominik Wujastyk (wujastyk) wrote :

My experience of the #25 fix has been a bit erratic too. Some observations:
1. I have three machines, two laptops and a desktop. The deb files prepared on one would not work on another. Had to do the recipe on each machine separately.

2. See note #27 above.

3. With the #25 patch done, and using gnome-shell, I have reliable, stable systems on all three machines.

4. If I log in to Unity, I sometimes get the problem again.

5. Sometimes seems to start when I use a Unity and a Java program. Sometimes just in a terminal session, but not in a gedit file.

Revision history for this message
Kevin (kevinshlee) wrote :

I found the condition. It works fine until I use the Unity launcher. It means as soon as I use Unity launcher, all the ibus problems mentioned here are back again. It happens in Gedit, terminal, LibreOffice, Pidgin, etc. So I disabled the key to show the launcher and am using GNOME DO instead. Unity in 11.10 is so frustrating. The one in 11.04 was much better.

Revision history for this message
Kevin (kevinshlee) wrote :

By the way, thanks Alex Lee for helping us solve the issue.

Revision history for this message
Kevin (kevinshlee) wrote :

Unfortunately, the problems were not really solved. I found the real condition causing it.
If I open any application and close it, the problems happen again.

For instance, it works fine on gedit then I close all the gedit windows and open it again. Now all the problems are back. It doesn't matter what application I open and close. Even opening nautilus and close it causing it. Once it's done, it happens in any applications.

So if I open nautilus and close the nautilus window, the problems start happening in gedit, terminal, Pidgin, LibreOffice, etc.

I'm seriously considering reinstalling Ubuntu 11.04.

Revision history for this message
Dominik Wujastyk (wujastyk) wrote :

I have a patched iBus 1.4.0, as described in #25 above. Running gnome-shell. Ubuntu system up-to-date (3.0.0-15-generic-pae).

Yesterday and today, on my desktop that I thought was stable, I have this problem situation:

When I type in TeXStudio, iBus gives me the garbled input. TeXstudio is compiled with QT, if that's relevant.

When, in the same login session on the same machine, I type into Gedit or a terminal, iBus text entry is fine.

I've just tried having TeXstudio and Gedit open at the same time, and I still have the different behaviours: in TeXStudio on the left of my screen, iBus text entry is garbled, in Gedit on the right, iBus text entry is fine.

I've tried both with and without the iBus option "share the same input method among all applications." Makes no difference.

okay, here's a possible clue: I open a terminal session. iBus entry is fine. From the command line, I start texstudio, and then in TeXstudio, iBus entry is fine!

So iBus text entry in TeXstudio (but not gedit) goes wrong only when I start it from a gnome launch icon. If I start it from the command line, all is fine.

Damn this problem!

Revision history for this message
Dominik Wujastyk (wujastyk) wrote :

PS commenting on #34, I can open and close applications many times, and I don't see your behaviour. For example, iBus entry in Gedit is fine on this machine at this time, even if I open and close it repeatedly.

Revision history for this message
Dominik Wujastyk (wujastyk) wrote :

Drat. I've muddied the waters terribly with my comments above.

In comments #35 and #36 above, I was NOT using iBus 1.4.0 (fujiwarat). I thought I was, but when I checked the ibus version (in synaptic) it was 1.3.99.20110419-1ubuntu3 (oneiric) again.

I have absolutely no idea how or why my system reverted to 1.3.99 again.

Now I've reinstalled 1.4.0-1ubuntu2 (now), with fujiwarat patch, according to #25 above, logged out and in, and my system is fine. I can call TeXstudio from a gnome-shell icon, and it accepts iBus input without error.

Also fine are iBus input in terminal, gedit, and jabref (java), and in a Window program under Wine. At the moment, I can't find any problem.

So, currently my system appears to be stable and to have no iBus problem.

Apologies for all the false error reports in #35 and #36.

In case it's relevant, my .bashrc file ends:

# for ibus:
export XMODIFIERS=@im=ibus
export GTK_IM_MODULE=ibus
export XIM_PROGRAM="ibus-daemon -d"
export QT_IM_MODULE=ibus
export LC_ALL=$LANG
export CLUTTER_IM_MODULE=ibus
ibus-daemon -rxd

I've added the clutter line.

Dominik

Dominik

Revision history for this message
David Gómez (dabisu) wrote :

Glad to hear that, hope this patch is pushed upstream ASAP.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank everybody for the comments, could you use bug #880876 rather though since that one got marked as duplicate

The title on https://bugzilla.redhat.com/show_bug.cgi?id=753781 suggest that it's a XIM issue?

The redhat patch got commited upstream there:
http://codereview.appspot.com/5417044

Revision history for this message
Kevin (kevinshlee) wrote :

Dominik, you're using GNOME shell. I think the problem I described has something to do with Unity.

Revision history for this message
Kevin (kevinshlee) wrote :

Sure Sebastien. I will.

Could all the subscribers of this bug please also subscribe to bug #880876 so that we can discuss about the issue further?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.