On 2021-05-17 10:10, Vincent Lefevre wrote:
I don't think that this is a special combo, at least when not used a desktop environment like GNOME. You can see other users doing the same thing: https://superuser.com/questions/644521/linux-mint-mate-use-xkbcomp-to-load-a-keyboard-layout-on-startup https://askubuntu.com/questions/437584/xkbcomp-command-at-startup-using-xinitrc
I see in the Mint example that they use sleep() to make it work without mentioning ibus or im-config. ;) That speaks for this being a general Xsession issue, which you happened to hit via ibus/im-config.
If the user has a .xsession file, that's what it is for.
Possibly a better option is to put the xkbcomp() call in a .desktop file in ~/.config/autostart.
Fortunately you were able to figure out the sleep() workaround.This was just for testing, but it is not an acceptable workaround, slowing down the startup, without any guarantee under machine load.
If you put it within parentheses as in the Mint example (i.e. start a separate sub process), it won't slow down or jeopardize the whole startup.
It is up to im-config to do its own synchronization before going on; that would be sufficient in my case, but...
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.
/ Gunnar