no input window with ibus-1.4.1 and ibus-1.4.2

[Adam]

I got this error after an update to by emerge on my gentoo-box.
ibus-1.4.1 was working pretty well.

Here are some details about my environment.

distro: Funtoo.org
ibus-version: app-i18n/ibus-1.4.2 app-i18n/ibus-1.4.1
desktop: openbox 3.5.0
dbus-version: 1.6.4
installed IM: ibus-anthy, ibus-pinyin

I'd like to dig into this issue if you guys could give me some guide
how to get debugging info like logfile and others.

Do you have some similar issues about the brand new version of 1.4.2?

[Ma Xiaojun]

AFAIK, after 1.4.1 is released, the IBus developers move to the work
of IBus 1.5 (1.4.99).

However, some bugs of 1.4.1 are found and some fixings are committed
into git. At some point, 1.4.2 is released, including all the commits.

https://github.com/ibus/ibus/commits/1.4.y

If you can make sure that 1.4.2 contains regression (rather than
configuration of your system is broken).
Can you spot a commit to blame?
Actually I feel that these commits are rather trivial. They should not
cause serious regression.

[Adam]

2012年10月6日土曜日 0時34分44秒 UTC+9 Ma Xiaojun:

AFAIK, after 1.4.1 is released, the IBus developers move to the work
of IBus 1.5 (1.4.99).

However, some bugs of 1.4.1 are found and some fixings are committed
into git. At some point, 1.4.2 is released, including all the commits.

https://github.com/ibus/ibus/commits/1.4.y

If you can make sure that 1.4.2 contains regression (rather than
configuration of your system is broken).
Can you spot a commit to blame?

Thanks for your reply.

Because the issue happens to both ibus-1.4.1 and ibus-1.4.2. Mostly likely, it is an issue with my configuration.
 

Actually I feel that these commits are rather trivial. They should not
cause serious regression.

I have no idea about what is exactly going wrong with this issue. The phenomena is about the 'No input window' message, but, I can not get any further information about it. Would you please give me some guide on how to get verbose/diagnosis messages with ibus-daemon?

[Ma Xiaojun]

On Mon, Oct 8, 2012 at 8:18 PM, Adam <jiang...@gmail.com> wrote:
> I have no idea about what is exactly going wrong with this issue. The
> phenomena is about the 'No input window' message, but, I can not get any
> further information about it. Would you please give me some guide on how to
> get verbose/diagnosis messages with ibus-daemon?

ibus-daemon --help

[Adam]

2012年10月9日火曜日 10時46分08秒 UTC+9 Ma Xiaojun:

Surely, I gave it a shot several days ago. It seems the following command line gave me nothing

ibus-daemon -x -d --verbose

nor this

ibus-daemon -x --verbose

Any idea?

[Adam]

2012年10月6日土曜日 0時34分44秒 UTC+9 Ma Xiaojun:

AFAIK, after 1.4.1 is released, the IBus developers move to the work

Tried to skim the code.

The occurrence of the error is there in ui/gtk/panel.py, looks like

class Panel(ibus.PanelBase):
      __gtype_name__ = "IBusPanel"
    def __init__(self, bus):
        super(Panel, self).__init__(bus)
        self.__bus = bus
...
        def focus_in(self, ic):
        self.reset()
        self.__focus_ic = ibus.InputContext(self.__bus, ic)
...
    def __status_icon_activate_cb(self, status_icon):
        if not self.__focus_ic:
            menu = gtk.Menu()
            item = gtk.ImageMenuItem(_("No input window"))
            size = gtk.icon_size_lookup(gtk.ICON_SIZE_MENU)
            item.set_image(_icon.IconWidget("gtk-dialog-info", size[0]))
            menu.add(item)
            menu.show_all()
        else:
            menu = self.__create_im_menu()
            self.__language_bar.create_im_menu(menu)
        menu.popup(None, None,
                gtk.status_icon_position_menu,
                0,
                gtk.get_current_event_time(),
                self.__status_icon)
...

The reason why the 'No input window' should be caused by no __focus_ic fetched properly. It seems InputContext is not initialized. Since I am using openbox-session but not Gnome/KDE, this is susceptible for some sub code for python in X is going wrong.

Could you please give some hints if you were familiar with this porting? Thanks a lot.

[Ma Xiaojun]

On Mon, Oct 8, 2012 at 9:16 PM, Adam <jiang...@gmail.com> wrote:
> The reason why the 'No input window' should be caused by no __focus_ic
> fetched properly. It seems InputContext is not initialized. Since I am using
> openbox-session but not Gnome/KDE, this is susceptible for some sub code for
> python in X is going wrong.

I think you are probably right.

> Could you please give some hints if you were familiar with this porting?
> Thanks a lot.

I don't. Let me CC the main developers of IBus core for you.

[Adam]

2012年10月9日火曜日 11時21分08秒 UTC+9 Ma Xiaojun:

Thank you, Xiaojun.

How could I follow this question? Or shall I report a bug on google code page?

[Ma Xiaojun]

On Mon, Oct 8, 2012 at 10:13 PM, Adam <jiang...@gmail.com> wrote:
You are welcomed to add an issue to the existing 200+ issues list.
From time to time, I would randomly pick an issue and try to solve it.

[Adam]

Issue reported

http://code.google.com/p/ibus/issues/detail?id=1517&thanks=1517&ts=1349761969

Please let me know if you want more details on this issue. I will try to follow up with you guys.

2012年10月9日火曜日 12時40分23秒 UTC+9 Ma Xiaojun:

[Ma Xiaojun]

What's the values of the following environment variables in your
machine: GTK_IM_MODULE
QT_IM_MODULE
XMODIFIERS

[Adam]

2012年10月9日火曜日 15時38分29秒 UTC+9 Ma Xiaojun:

Here is my ~/.xprofile

export XMODIFIERS="@im=ibus"
export GTK_IM_MODULE="ibus"
export QT_IM_MODULE="xim"
ibus-daemon -d -x

I also checked these values in procfs by "cat /proc/`pidof openbox`/env*". They are there as I set.

/Adam