System Settings > Keyboard > Virtual Keyboard: IBus Wayland selected
There are three input methods (European languages), but the Next input method shortcuts work with stops and hitches; I’ve no idea how to describe it better. So far I tried Super+Space and Shift+Space, no difference.
I have experience with IBus and KDE on X11; one has to know how to start IBus there, but the shortcuts give no problem.
I also know that on Wayland only Gnome is trouble free concerning IBus. But this can’t be forever, I hope. Please, share your experience. I searched everywhere, found next to nothing.
+1
I want to use ibus (typing booster or maybe iee) but honestly, after a few weeks trying, and a couple of bug reports, I decided it’s just not ready yet, and put it in the queue.
I am not using Ibus but with fcitx5 I had problem of conflicting shortcuts with main plasma one: in particular Super+Space is used by xkb to switch keyboard layout , it could also be set to some other action/app (very demanded shortcut !).
Have you tried to test others completly different like Ctrl+Shift+f8 or else test?
Note: It may not be what you want but fcitx5 has better kde /wayland support and as an m17n module.
The shortcuts shouldn’t be an issue, because on the same KDE under X11 they are good enough.
This isn’t a question about IBus replacement; I just want IBus working . Seriously, I’m mystified about an obvious, showstopper bug which persists for more than one year. There should be a reason.
But did you try other shortcuts ? It is a matter of test to find from where the problem come. For the fact that it work on X, well wayland change the way input is manage so there could be conflict not present in X.
The shortcut builder is a tab on the IBus settings app. Surely at least the default one should work? Besides, those in the know should have corrected me by now. They’ve had more than one year
It is not whether the default one should work, more if something else elsewhere interfer.
Since I am curious, I installed ibus (and ibus-m17n) and do the test. I had to unset some environnement variable and relogin but then everything seems in order. It works on GTK app, QT app (kate, Libreoffice QT6), GLFW app (kitty), it even work on flatpak (LibreOffice on flatpak). For kitty, Arch wiki ask to set GLFW_IM_MODULE=ibus but I have it not set and it works. Right now only Chromium doesn’t get it, but its electron … On Arch wiki there’s mention of a parameter for chromium in the case of fcitx5 maybe it would be needed also for ibus (-wayland-text-input-version=3).
So I don’t see what append on your side.
For my personal use case, Ibus lacks support for custom xkb layout (some others) so I have to use fcitx5. Ibus is simpler though.
Edit: to be clear the environement variables QT_IM_MODULE and GTK_IM_MODULE should not be set, if they are, ibus will not work in the corresponding apps then ibus complain (notification) at start if they are not empty. On the Arch wiki it said to set them as QT_IM_MODULE=ibus but it seems an outdated requirement.
Also to help you can give some precision regarding your system : show output of kinfo in terminal or systemsettings>System also the version of ibus.
There is the fact that ibus run in X so on wayland it run in Xwayland (at least on my system) so it could maybe explain problem present in wayland not there in X.
For the environement variable, the one I mentioned ine the previous post QT_IM_MODULE GTK_IM_MODULE GLFW_IM_MODULE
for example what this give you:
printenv | grep IM_
I had to unset them because I had set then to fcitx for my setup but if you don’t set them in one of the conf file they may not be set.
On the Arch wiki it is not about wayland just that they advice setting these envvars:
but I have seen elsewhere not to do that so I supposed it is an outdated advice. For example you have to tell Kwin which IME to use in systemesettings > keyboard > Virtual keyboard and then I guess kwin/plasma handle everythings. You can try to set them as per the wiki though maybe it help, just that it send a notification by ibus/kwin that ask to unset them.
For the wayland support, I supposed it is not supported because on my system it run in X and I think I have seen that somewhere. Also if you look at ibus package in Arch https://archlinux.org/packages/extra/x86_64/ibus/
you can see in the dependancies that it depend on libx11 but not wayland.
To verify if ibus is running in X (or any program) you can install xlsclients (xorg-xlsclients on Arch) and run it. It will list process running on X (Xwayland).
Finallly if the problem you have is the shortcut (Ctrl+Space) not working it may not really be a problem with ibus or X, but just the fact that the same shortcut may be used for something else. If you don’t want to test things to narrow the problem there is nothing anyone can do. For example you can disable (uncheck) xkb layout config in systemsettings > keyboard > keyboard wich tend to use that same shortcut which then collied with ibus settings
Looking at ibus github it seems ibus should have wayland support for recent version.
Edit: So by looking a little more, ibus run in wayland (for exemple ibus-setup the config tool), but there is part that run in X (ibus-x11 and ibus-ui-gtk3) maybe for compatibility with apps not wayland capable.
I have tested ibus on an Arch system and it wok as expected (it is necessary to uninstall fcitx5 if previously installed though because kde seems to prefer it and launch it everytime if found).
I had quite some trouble making it work on Arch. For example I got an error when launching ibus-setup
The shortcut is Shift+Space; checked with the Keyboard Settings, no such thing. Always used it on KDE X11 without any trouble. On Wayland it requires extra key press after the shortcut to actualize, and there’s no autorepeat when any key is held.
Checked with Alacritty, Konsole and Console. Sometimes it seems that the behavior is a bit different, but it’s never good enough.
Yes, the ibus-setup starts a bit weirdly, but it starts after all. So far as I understand, all the checks are good. The behavior’s just as bad as always. What else could I try?
For ibus-setup, it was a conflict with python on my system.
For the rest I can’t help you after that libs resolve ibus is working fine on my side. I didn’t test on those apps. Did you test no QT (other than konsole) app , GTK .
But as I said, I don’t understand why you don’t want to test other shortcut. I had a similar problem when I config fcitx5 and I tested with different shortcut in order isolate the problem and then I could set it like I want.
As for the shortcut kde shortcut config is in ~/.config/kdeglobals and ~/.config/kglobalshortcutsrc then there each apps (include kde apps) can set shortcut in different places for exemple konsole put them in ~/.local/share/kxmlgui5/konsole/sessionui.rc
Finally others ,who add the same problem with ibus+kde+wayland , post a ticket on ibus github not long ago . I also see that some work is done on ibus toward implementing more recent wayland protocol. But since I have no problem with ibus on my side (on 2 devices with an Arch system and a KDE Neon/Ubuntu one) I think the problem is on your config.
As I think of it one thing you can do to test (something I do when I want to eliminate my config to the equation) is to create a new user and test on it. You start fresh and then you can just set ibus as ime in systemsettings and your layouts and see how it work.
For the rest I can’t help you after that libs resolve ibus is working fine on my side.
What libs? I’m not sure.
Concerning different shortcuts: I tried Alt+Shift+Space. It’s worse I also keep my KDE shortcuts to defaults.
What’s the shortcut you use? Just let me try it.
I’ve been trying IBus + Wayland + KDE for more than a year, on different boxes, always Arch derivatives, like Manjaro or EndeavourOS. The outcome is always the same. So my little something is always the same, and it remains unknown…
lib=python (i installed a different version than distro which confict with ibus-setup) when I remove the faulty install, ibus-setup started without problem. I precise that because at that moment I thought the Arch install of ibus was the problem (since no problem on Ubuntu) but it is not and my arch ibus install works fine (Endeavour OS actually but it use Arch repo).
I think I share on lenght with my experience. Are you familiar with github? You can search on the github repo of ibus, for that particular ticket (about shortcut on ibus+wayland+kde) there have been no response so It of no help for resolving your problem now.
You can look at logs journalctl -r (and then search for ibus with /) or journalctl -f (and deactivate/activate ibus). You also can start ibus from terminal and see what comes ibus start --type kde-wayland --verbose (after stoping ibus with ibus exit or killall ibus).
Edit: To use ibus in chromium, we need to enable chromium’s experimental text-input-v3 implementation using chrome://flags/#wayland-text-input-v3, assuming chromium’s ozone/wayland backend is used. I still get some issue with some chromium extensions (vimium).
Edit2: btw, default shortcut config uses Meta+Space for xkb (layout switching) , I change that to something like Meta+\ (you can change it using systemsettings interface for keyboard layout config).
Funny enough, the last of them was closed while we had this conversation. I feel like the author was watching
Wayland native support is new, too. I will have to give it another try soon .
. Seriously, I’m mystified about an obvious, showstopper bug which persists for more than one year. There should be a reason.