I could reproduce this issue in Ubuntu impish by simply adding:
export XDG_CACHE_HOME=/tmp/mycache
to ~/.profile and relogin.
Then, as James Henstridge suggested, I tried starting it like this:
IBUS_USE_PORTAL=1 chromium
Unfortunately that did not help.
I made one observation, though, which might be useful as a workaround: If I set the XDG_CACHE_HOME variable to "/tmp" (instead of "/tmp/mycache"), typing within the Chromium snap, including inputting with an IBus engine, worked as expected. Possibly the explanation is that /tmp is used as a fallback, sort of, to deal with BSD systems.
I could reproduce this issue in Ubuntu impish by simply adding:
export XDG_CACHE_ HOME=/tmp/ mycache
to ~/.profile and relogin.
Then, as James Henstridge suggested, I tried starting it like this:
IBUS_USE_PORTAL=1 chromium
Unfortunately that did not help.
I made one observation, though, which might be useful as a workaround: If I set the XDG_CACHE_HOME variable to "/tmp" (instead of "/tmp/mycache"), typing within the Chromium snap, including inputting with an IBus engine, worked as expected. Possibly the explanation is that /tmp is used as a fallback, sort of, to deal with BSD systems.
https:/ /github. com/ibus/ ibus/blob/ master/ bus/server. c