Created attachment 1759336 [details]
Ibus-panel vs "plasma keyboard layout"

> In Plasma(wayland) im-chooser/emoji start by default(not start in X11)changing layout CZ to US works for a while and then change back it self.
> ...
> Expected results:
> dont start ibus-emoji in wayland session by default, like in X11 session

What do you mean with "im-chooser/emoji" and "ibus-emoji"? I don't have these processes in my Plasma Wayland session on F34.
These are all the processes I see:

  |   |   |   \_ /usr/bin/ibus-daemon -r --xim
  |   |   |       \_ /usr/libexec/ibus-dconf
  |   |   |       \_ /usr/libexec/ibus-ui-gtk3
  |   |   |       \_ /usr/libexec/ibus-extension-gtk3
  |   |   |       \_ /usr/libexec/ibus-engine-mozc --ibus
  |   |   |       \_ /usr/libexec/ibus-engine-simple
  \_ /usr/libexec/ibus-x11 --kill-daemon
  \_ /usr/libexec/ibus-portal

I have /usr/libexec/ibus-ui-emojier, but it isn't running.

Another question: is QT_IM_MODULE set in your session?

Fedora 34 sets QT_IM_MODULE from /etc/X11/xinit/xinput.d/ibus.conf, which (afaict) won't run in the Plasma Wayland session.

by default its installed package im-chooser (/usr/share/applications/im-chooser.desktop)
remove this package make keyboard layout united for all applications.

in X11 plasma session its just one keyboard menu from KDE in systray (with white font "CZ")
in wayland seasson starts the second keyboard menu(with blue font "EN" on picture).

I'm not well-versed in how all this works, anyone who knows more, can you offer concrete suggestions on how best to address issues raised in this bug?

So far, I see these:
1.  set QT_IM_MODULE env somehow.  I'd argue this should be done in ibus packaging (somehow), the existing xinit snippet is less that ideal (and obviously only works for X sessions).  Alternatives include:
* (plasma-specific) sh snippet under /etc/xdg/plasma-workspace/env/
* sh snippet under /etc/profile.d/  (unfortunately, that will set if for all login shells, not just GUI, not sure if that's bad or not)

2.  remove im-chooser.  pros/cons?

I have this workaround in my profile:

  # temporary for F34 Plasma Wayland
  QT_IM_MODULE=ibus
  IBUS_USE_PORTAL=1
  export QT_IM_MODULE IBUS_USE_PORTAL

The ibus package could set these two vars from /usr/lib/environment.d/10-ibus.conf. This should be executed by the systemd user session for both X11 and Wayland, both GNOME and KDE.


> 2.  remove im-chooser.  pros/cons?

im-chooser could still override the im module by writing to ~/.config/environment.d/*.conf.

I believe ibus is currently the only input method which works well in Wayland for both GNOME and KDE.
So im-chooser should probably be removed from the default install avoid confusion for users (and imsettings-qt should stop depending on it).