Comment 3 for bug 1425510

Hi, Aron. Thanks for looking into this bug for me.

I acknowledge what you're saying that it's someone else's fault, but without more detail about what you actually think is going on, this may be misinterpreted. I personally have no idea what is going on, and can't contribute to resolving this through other projects' bugtrackers without your contribution. What 'kind' of bug is in the applications, that means an im-config change can workaround it?

Recently, keyboard input problems, including loss of responsiveness and loss of individual key events, seem to apply to almost all of my applications actually (even incredibly simple ones like Geany and Terminal), so if all of these applications have the same problem, I doubt whether it's an individual application developer at fault.

Regarding the Chrome bug, when you say "you have to get GTK2 IM Module installed" that is not a package name, so I can't install it.

Are you implying that the fault is in not having any IM Module installed? (I have to read between the lines as your comment was very terse) I already have both ibus and scim installed, (and ibus was selected under Preferences>Language Support>Keyboard Input Method System), so this is not the case on my system.

I also can't file an upstream bug to get anyone to package it (either Chrome OR Chromium - where Ubuntu maintainers can control packaging). Do you have one or more package names from Ubuntu repositories that your suggestion might relate to.

For reference, those others experiencing a problem, I've found a workaround right now (on Lubuntu) is to entirely disable international input support, by going to Preferences>Language Support>Keyboard Input Method System and selecting 'none', then restarting the system.