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 675014 - Can't activate input method in Awesome window manager
Can't activate input method in Awesome window manager
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Input Methods
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-04-28 08:33 UTC by lilydjwg
Modified: 2018-02-10 03:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description lilydjwg 2012-04-28 08:33:13 UTC
I can hardly activate my input method in gnome-terminal in Awesome WM. When the gnome-terminal window gets the focus, for most of the time I can't activate IM by all means (Ctrl-Space, clicking the IM's icon, using fcitx-remote). Sometimes it works, but I have no idea if it'll still work if I switch to another window and switch back again.

I remember it once worked. And it seems that after I update gnome-terminal from 3.2.1 to 3.4.1.1 it becomes harder to get it work.

Tested IMs include fcitx and ibus.
Comment 1 Weng Xuetian 2012-04-28 10:32:37 UTC
One possible problem might be gnome-terminal doesn't set focus correctly (might due to gnome-terminal it self or awesome) to im module.

Since all key is passed to gnome-terminal directly, and fcitx and ibus are both using gtk key snooper to grab the key, seems no way for key not being processed once by im module.
Comment 2 Christian Persch 2012-04-28 18:55:47 UTC
Please test if this is reproducible with either gnome-shell or metacity (latest versions from gnome 3.4) in click-to-focus mode. Anything else is entirely unsupported.
Comment 3 Weng Xuetian 2012-05-02 13:50:37 UTC
It happens sometimes when gnome-shell restart.

I wonder gnome-terminal missing some case for gtk_im_context_focus_in, or it's some gtk3 change break this.
Comment 4 Christian Persch 2012-05-02 14:44:37 UTC
OK. So this could be either a gtk 3.4.x problem, or a gnome-shell one. (Since it one worked according to comment 0, and there haven't been any IM related changes in vte or g-t, I don't think it's a bug in either of these.)

Trying -> gtk+.
Comment 5 Fermat 2012-07-21 02:08:41 UTC
This is reproducible in GNOME3.
Comment 6 Fermat 2012-08-14 15:28:16 UTC
This is especially easy to reproduce when there are two gnome-terminal windows in Gnome 3 (gnome-shell).
Comment 7 SuperCat 2012-08-14 15:31:54 UTC
I also met this bug using iBus in GNOME Terminal on both GNOME3 and Xfce4. But this bug occurs rarely.
Comment 8 Matthias Clasen 2018-02-10 03:37:30 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.