194186 - GTK2: Mozilla often says Loading IM context type 'xim' failed gtk+2.0.6

Status: RESOLVED WONTFIX

(Core :: XUL, defect)

Description

[Masaki Katakai]

With GTK2 build with USE_XIM, Mozilla often shows the
following warnings and sometimes dumps core,

(<unknown>:6019): Gtk-WARNING **: Loading IM context type 'xim' failed

It seems that the way for creation of im context is not good.

Comment 1

[Masaki Katakai]

Currently Mozilla gtk2 tries to create im context
if mShell exists - all types of
eWindowType_dialog, eWindowType_popup and eWindowType_toplevel.

    if (mShell) {
        // init GtkIMContext for shell
        IMECreateContext(mShell->window);
    }

However, we don't need im context for eWindowType_popup.
After I changed not to create im context for the type,
the error messages could be fixed.

I'll try to make patch that will create im context
at getting input focus, which is the same way of
widget/src/gtk.

Comment 2

[Masaki Katakai]

It seems that this problem happens because of
gtk+2.0.6 of RedHat 8.0. I have seen the same
problem on gedit. I'm not seeing with gtk 2.2.1.
I have no idea to make xim codes work well
with gtk+2.0.6.

Actually creating ic for eWindowType_popup is
not correct, which causes focus probrem too.
I'll try to put the patch for changing ic creation
per eWindowType_dialog and eWindowType_toplevel
in bug 189880.

Comment 3

[Masaki Katakai]

No way to fix from Mozilla side. No problem with gtk+2.2.

Comment 4

[Roland Mainz]

Masaki Katakai wrote:
> No way to fix from Mozilla side. No problem with gtk+2.2.

What about making gtk+2.2 the minimum requirement when building with
--enable-default-toolkit=gtk2 ?

Comment 5

[Masaki Katakai]

Hi Roland,

Thank you for comment. Is that correct approach if we
see problem in other library side?

Comment 6

[Roland Mainz]

Masaki Katakai wrote:
> Thank you for comment. Is that correct approach if we
> see problem in other library side?

It depends on:
- which library
- which problem
- are workarounds available/usefull/wanted
etc.

Do you have any specific library/problem in mind ?

For GTK+v2 I've seen now more than one complaint/problem about GTK+v2.0 and I
think it may be - instead of stuffing Mozilla's code and release notes full with
lots of exceptions for GTK+v2.0 - wise to make GTK+V2.2 the minimum requirement
for the gtk2 port (however the port maintainer needs to make that decision -
feel free to file a bug for that, please).