[Pkg-ime-devel] Bug#716945: fcitx starts on KDE4/GNOME3 despite im-config settings

[Osamu Aoki]

Hi,

On Fri, Aug 09, 2013 at 02:51:52PM +0800, Aron Xu wrote:
> On Mon, Jul 15, 2013 at 3:48 PM, Osamu Aoki <osamu at debian.org> wrote:
...
> >
> > It seems fcitx has special autostart using dbus.  When fcitx was started
> > unintentionally, I saw it was initiated by dbus via "ps aux".  Is this
> > the right approach to start IM?
> 
> It is because fcitx installs an xdg autostart file, so that if a
> desktop environment supports this mechanism, a script under
> /usr/bin/fcitx-autostart is executed. There is a mechanism to detect
> if there is already an fcitx instance running, or another application
> is holding XIM (i.e. ibus). If it believes no others is running, fcitx
> will continue to initialize.

Yes, I see it now.

> I think this is because we still don't have xdg autostart support in
> im-config?

When implementing im-config/im-switch, this XDG autostart was not used
intentionally to ensure older environment not following freedesktop
standard can also get proper IM support.

I installed fcitx and used it with im-config with:
 * /etc/xdg/fcitx.desktop removed manually.
 * im-config sets IM to fcitx

fcitx starts nicely in sid/GNOME3.

Please let me know the advantage over current start method.  I mean what
does fcitx loose if it were started from im-config hook script?

If there is any advantage, I will add support.
(But without advantage, there is no reason to make things more
complicated than needed.)

> > If such autostart mechanism is loaded, it should be selectable among
> > ibus fcitx scim.

If we see advantage of using XDG autostart, this is what is needed.  And
that is why I mentioned.

Even then, please note fcitx should not place file at
/etc/xdg/fcitx.desktop.  

It should be im-config placing file there.  Then that starts selector
script based in im-config setting.

This is relatively simple to implement. 

If we do this, we need to disable current im-launch script for all XDG
compliant DM.

Osamu