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 763853 - 'direction-changed' signal is forever fired when using bidi keyboard
'direction-changed' signal is forever fired when using bidi keyboard
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: X11
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-03-18 07:53 UTC by Makoto Kato
Modified: 2018-04-15 00:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
sample source code (571 bytes, text/plain)
2016-03-18 07:53 UTC, Makoto Kato
Details

Description Makoto Kato 2016-03-18 07:53:48 UTC
Created attachment 324234 [details]
sample source code

Env
===
GTK 3.18.9 (X11 backend)

Step
====
1. Install Arabic language keyboard
2. Run Attached sample
3. Change your keyboard to 1.'s Arabic language keybaord

Result
=====
'direction-changed' signal is forever fired per event until switching to non-bidi keyboard


Notes
====
X11 backend uses a cache for Bidi info.  But this cache seems to be invalid.
Comment 1 Matthias Clasen 2016-03-18 12:41:30 UTC
Thanks for the testcase. But what you are describing is not happening here. Maybe I'm missing some detail of your reproduction instructions.
Comment 2 Karl Tomlinson 2016-03-21 03:06:29 UTC
https://bugzilla.mozilla.org/show_bug.cgi?id=1033483#c11 said that ibus was in use.

Could you test, please, to see whether you see the same behavior when that input method is disabled.  IIRC GTK_IM_MODULE=gtk-im-context-simple in the environment should be sufficient.
Comment 3 Makoto Kato 2016-03-24 04:26:41 UTC
(In reply to Matthias Clasen from comment #1)
> Thanks for the testcase. But what you are describing is not happening here.
> Maybe I'm missing some detail of your reproduction instructions.

If using uim (default of Debian/sid), this doesn't occur.
If using ibus, this occurs.
Comment 4 Matthias Clasen 2016-03-25 01:08:09 UTC
(In reply to Karl Tomlinson from comment #2)
> https://bugzilla.mozilla.org/show_bug.cgi?id=1033483#c11 said that ibus was
> in use.
> 
> Could you test, please, to see whether you see the same behavior when that
> input method is disabled.  IIRC GTK_IM_MODULE=gtk-im-context-simple in the
> environment should be sufficient.

No change. I get a single direction-changed signal every time I switch between en and ar layouts.
Comment 5 Makoto Kato 2016-03-28 04:50:01 UTC
(In reply to Matthias Clasen from comment #4)
> (In reply to Karl Tomlinson from comment #2)
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1033483#c11 said that ibus was
> > in use.
> > 
> > Could you test, please, to see whether you see the same behavior when that
> > input method is disabled.  IIRC GTK_IM_MODULE=gtk-im-context-simple in the
> > environment should be sufficient.
> 
> No change. I get a single direction-changed signal every time I switch
> between en and ar layouts.

If using debian and ibus, could you add ibus-mozc too?
Comment 6 Matthias Clasen 2016-04-02 16:23:32 UTC
Not using debian
Comment 7 Karl Tomlinson 2016-04-03 21:16:28 UTC
It may be more helpful to report this with ibus, because it seems the issue happens only with ibus, and ibus developers may know what is triggering keyboard changes.  https://github.com/ibus/ibus/wiki/BugReport
Comment 8 Matthias Clasen 2018-02-10 04:57:08 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 9 Matthias Clasen 2018-04-15 00:03:07 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new