On 2021-05-17 22:19, Vincent Lefevre wrote:
On 2021-05-17 21:11:16 +0200, Gunnar Hjalmarsson wrote:
I think it's too much to ask from a simple Xsession plugin such as
im-config that it should be responsible for preventing any kind of
possible conflicts.
Then it should not be started by default. If it is so important,
desktop environments could depend on it and enable it on their side.
If you run "apt rdepends ibus" on a Debian system you see that basically
only input method packages depend on ibus. (gnome-shell recommends it,
which is a special case.) But the output is free of random applications
which depend on ibus.
Well, not in your case, since you installed zoom. I can't tell why they
made zoom depend on ibus, but I'm pretty sure it's a rare exception.
So whatever you think about it, your case is special. ibus was installed
for you even if you didn't really ask for it, and since it pulled
im-config, ibus is configured and launched automatically by default. On
top of that you have an advanced keyboard configuration using an xkbcomp
call in ~/.xsession, and somehow those things don't play well together.
The im-config behavior is based on the assumption that if you install an
input method framework such as ibus or fcitx, you want to use it. It's a
reasonable assumption and it makes it easier for input method users.
Actually im-config checks the XDG_CURRENT_DESKTOP environment variable,
and theoretically it wouldn't be very difficult to disable it by default
if that variable is unset/empty. But personally I would not like to see
such a change. The interest of input method users carries greater weight
IMO.
Maybe somebody comes up with a clever solution which makes everybody
happy. Short of such a solution and for now, please just disable or
remove im-config and move on.
--
Regards,
Gunnar Hjalmarsson
