Hi Osamu!

On 2017-09-30 15:36, Osamu Aoki wrote:
If ibus is started outside of im-config, it may be better to
automatically set im-config to set to "REMOVE".

Since Ubuntu 17.10 is switching from Unity go GNOME, and the default DM will be GDM (which always starts IBus), we have just been struggling with a couple of im-config issues.

One thing we found motivated was a tiny change in /usr/share/im-config/data/21_ibus.rc.

This:

if [ "$IM_CONFIG_PHASE" = 2 ]; then
# start IBus daemon

was changed to:

if [ "$IM_CONFIG_PHASE" = 2 -a "$(cat /etc/X11/default-display-manager)" != '/usr/sbin/gdm3' ]; then
# start IBus daemon

But we still let im-config set the variables. If we hadn't done that, GNOME would have set only:

QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus

Possibly that would have been sufficient, but we chose to let im-config do its thing as regards the variables.

But more importantly: The fact that GDM always starts ibus-daemon does not in itself prevent the user from selecting some other IM framework via im-config and use related input methods for typing. So testing whether ibus-daemon is started or not seems not to be a good idea.

(Wayland misses Fcitx support at this time, though.)

Since Debian needs to support not only GNOME and KDE but also all classic DESKTOP environments. Since I don't have good exposure to
what are involved, I am placing wishlist bug to get this situation
tamed via public discussion.  Also, I am wondering if all wayland
based environment get started after executing /etc/X11/Xsession.d/*
... especially  it's confusing how dbus etc. work.  Maybe this kind
of hook script is not needed any more.  Maybe we should also place
hook code at some other place to be compatible with the new situation
such as wayland.

For a while we have used a systemd service in Ubuntu:

/usr/lib/systemd/user/im-config.service

However, there is an issue in Ubuntu 17.10 which prevents it from running, so to compensate for that we added a temporary equivalent in /etc/profile.d.

If I understand it correctly - and I'm not sure here - the systemd service will serve its purpose again in Ubuntu 18.04.

--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

Reply via email to