After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 731230 - Input methods problem
Input methods problem
Status: RESOLVED OBSOLETE
Product: vte
Classification: Core
Component: general
0.37.x
Other Linux
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-06-04 18:22 UTC by Egmont Koblinger
Modified: 2018-02-17 10:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Egmont Koblinger 2014-06-04 18:22:28 UTC 
I've found this report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736342

I have also experienced similar issues.  I have GTK_IM_MODULE=ibus (Ubuntu's default).

Sometimes Ctrl+Shift+U doesn't do anything.
Sometimes it falls back to GTK's version of entering a Unicode codepoint rather than ibus's version (you can tell this by the bug https://code.google.com/p/ibus/issues/detail?id=1715 being gone).
Sometimes the input hangs in one of the g-t tabs, but keeps working in the other ones.
Sometimes Ctrl+Shift+U emits the correct character by the hex code, except that there's no visible feedback, I need to type the digits blindly.

No reproducible test case yet, but switching between g-t windows, tabs, firefox, xterm, and using Ctrl+Shift+U often triggers one of these in a couple of minutes.
Comment 1 Christian Persch 2014-06-04 18:37:21 UTC 
You could check the GtkSetting gtk-im-module property; print to console on startup and when it changes. My guess would be that this property is changing...
Comment 2 Christian Persch 2014-06-29 09:35:38 UTC 
AFAIK gnome-settings-demon is setting the xsetting for which input method to use depending on which input sources are configures, and the only possible values are 'simple' and 'ibus'. So setting the env variables to anything else conflicts with that, and makes this bug INVALID/NOTABUG, IMHO.
Comment 3 Egmont Koblinger 2014-06-29 10:58:08 UTC 
(In reply to comment #2)
> So setting the env variables to anything else

My env vars are not "anything else", but "one of these" (GTK_IM_MODULE=ibus).  I never touch this, never touch the kbd settings (I have two layouts configured: us and hu(101_qwerty_whatever) with Alt+Shift toggle).  All I do is I very often switch between the layouts.  The bug occurs relatively frequently.  I can't tell if it's related to layout switches, or would even occur without that.

So there is definitely a bug – albeit might not reside in VTE, not sure.  Let's keep this open until we can further investigate and reassign if necessary.
Comment 4 Christian Persch 2014-06-29 11:03:48 UTC 
Right. (The downstream bug linked in comment 0 has GTK_IM_MODULE=xim.)
Comment 5 Egmont Koblinger 2016-11-23 22:04:39 UTC 
I can't recall facing this bug for a year or so now. I guess it used to be a bug in Gtk+ which is fixed now.
Comment 6 Christian Persch 2018-02-17 10:54:21 UTC 
Let's call this obsolete then.