A recent IBus notification is more verbose (but still, outdated):
IBus should be called from the desktop session in Wayland. For KDE, you can launch ‘systemsettings5’ utility and go to “Input Devices” → “Virtual Keyboard” section and select “IBus Wayland” icon and click “Apply” button to configure IBus in Wayland. For other desktop sessions, you can copy the ‘Exec=’ line in org.freedesktop.IBus.Panel.Wayland.Gtk3.desktop file to a configuration file of the session. Please refer each document about the “Wayland input method” configuration. Before you configure the “Wayland input method”, you should make sure that QT_IM_MODULE and GTK_IM_MODULE environment variables are unset in the desktop session.
Use a simple ~/.xinputrc file that detects the session type (X11 or Wayland) automatically.
# ~/.xinputrc
# Detect session type (Wayland or X11)
if [ "$XDG_SESSION_TYPE" = "wayland" ]; then
# For Wayland (KDE, GNOME, etc.), no need to force GTK_IM_MODULE or QT_IM_MODULE
export XMODIFIERS="@im=ibus"
else
# For X11 (XFCE, MATE, LXDE, etc.), force compatibility
export GTK_IM_MODULE=ibus
export QT_IM_MODULE=ibus
export XMODIFIERS="@im=ibus"
fi
Important Notes:
If ~/.xinputrc is present, it’s automatically used by im-config.
This overrides im-config’s automatic setup.
Works seamlessly across X11/Wayland without errors on KDE Plasma 6.
This approach ensures maximum compatibility without manual intervention.
become root or use sudo to open your favourite editor, thus emacs
open this file:
/usr/share/im-config/data/21_ibus.rc
Just comment out the variables. They won’t be set so that you won’t need to unset them.
Here’s how it looks like on my KDE neon 6.3 (Ubuntu 24.04):
# start IBus
# vim: set sts=4 expandtab:
# hands off to set up IM if listed in $DESKTOP_SETUP_IBUS
if find_match "$IM_CONFIG_CURRENT_DESKTOP" "$DESKTOP_SETUP_IBUS" ; then
# ibus set up is owned by desktop --> do the same as "none"
return
fi
if [ "$IM_CONFIG_PHASE" = 2 ]; then
# start IBus daemon and IM panel
IBUS_ENABLE_SYNC_MODE=0 /usr/bin/ibus-daemon --daemonize --xim
fi
if [ "$IM_CONFIG_PHASE" = 1 ]; then
# set variables for the plain XIM
XMODIFIERS=@im=ibus
# Let's assume all required modules are installed
# GTK_IM_MODULE=ibus
# QT_IM_MODULE=ibus
# CLUTTER_IM_MODULE=ibus
# See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008481#40
# why ibus skips SDL_IM_MODULE while fcitx5 list it
fi
Shouldn’t this actually be reported as a bug ?
Looks pretty annoying and it seems to recur every now and then after updates.
Thanks, the solution helped me get rid of the problem. Installing zoom is what created the problem. It important to know which install created the problem and it was zoom for me.
After further testing, this issue seems to appear on the new Debian 13 release when Plasma is installed alongside any other DE based on GNOME. I tried using the large “complete” ISO to install Plasma alone without allowing any GNOME components to install, and I never received any of these warning messages. However, further testing shows that you will consistently receive these error messages if you install a GNOME based DE alongside Plasma. So another “solution” if you will, could be to simply make sure Plasma is the only desktop environment you install assuming you have no need for the other options.
Ubuntu Studio 25.10
I had one more thing on top of everything else that was preventing the message from going away and the IME from functioning on reboot. A probably redundant Autostart for ibus-daemon. Removing it fixed it for me.
Oh dear. betzalel75’s solution did work. I finally noticed that the filename I used was .inputrc and because I was using wayland missed the X. Using the file name .xinputrc solved my problem. I am puzzled as to why the no key sequence termination went away but that is another lesson.
Important Notes:
No issues found.