Dear Maintainer, Let me tell you about a bug I found in debian 13 in case you are nor aware: WPS Office needs IBus in order to write accents, then, I have enabled Ibus wayland in *Preferences → Virtual Keyboard → Ibus Wayland.* Following Debian’s instructions,I have deactivated IBus in im-config, then I do the following: im-config → *do not activate any IM from im-config and use desktop default.* However, when I open WPS Office to write a .docx, it doesn't type accented characters (Spanish language). Same behavior in X11. For it to work, I have to* activate Ibus in im-config*, but then I receive a KDE desktop notification every time I start Debian 13 telling me that I*Bus shouldn't be activated in im-config. * Let me know in case you need more information,
Hi Boyuan. Maybe we need coordinated action for Plasma 6 migration between ibus and im- config but I don't have ready solution nor resources on my hand (see below). What is your thought? Hi, David I see 2 similar/related bug reports by you. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108187 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108206 I don't understand why you filed 2 similar separate bugs with somewhat vague description except for your suffering with key inputs. I understand this is quite annoying for you. As I see BTS, I see very interesting bug report related to xkb: Debian Bug report logs - #1108040 ibus: FTBFS: FAIL: xkb-latin-layouts https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108040 This indicates currently available ibus suffers issues for xkb under some weird test condition. So your issue may be solved when an updated package is uploaded addressing the root cause. When im-config is installed, ibus is configured mostly by im-config. I understand that the update of ibus and im-config should be coordinated. So your issue may require update of im-config. Unfortunately, recent KDE's migration to Plasma6 has not been addressed yet. See: Debian Bug report logs - #1052005 KDE Plasma with IBus: im-config changes needed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052005 Debian Bug report logs - #1099858 im-config: Fctix5 environment variable is not set correctly in KDE Plasma 6 Wayland https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099858 Regards, Osamu
*I send again again the email because I forget to include to 1108206@bugs.debian.org <1108206@bugs.debian.org> and Boyuan Yang <byang@debian.org <byang@debian.org>* Hello Osamu, Sorry for the two tickets, I am new in linux and I didn't know the best way to create a ticket so I tried two different ways. Sorry also for my vague description. Were you able to reproduce the bug? When I say in my bug report that I am not able to write accents, here are some examples what i am referring to: if I try to write "camión", "ladrón" or "avión" as you can see, the word "ò" has a small accent. Then, If i select *ibus wayland *in virtual keyboard, and open wps office or openoffice and write these words, then the result is the following: "camin", "ladrn" and "avin", as you can see the word "ó" is not written. To solve this I have to go to *im-config* and select* ibus*, but then I receive the notification that im-config should not be used" Sorry for not being able to provide more technical information, but if you ask me what information you need I will try to do my best to help, Thanks and regards from Spain ;) El vie, 27 jun 2025 a las 3:33, Osamu Aoki (<osamu@debian.org>) escribió:
(CC-ing coucouf because of https://bugs.debian.org/1052005#18 ) Hi, 在 2025-06-29日的 07:25 +0200，David Conesa写道： is a headache. (1) If you want a suboptimal yet working solution: Go back to im-config and explicitly select ibus. Ignore the pop-up notification each time saying that im-config should not be used. (2) Or you can break the combination of tools. For example: -> Do not use WPS Office anymore. -> Go back to X11 instead of using Wayland. -> Do not use IBus, but use fcitx5 instead. (3) If you want a proper solution: I don't know any as of now. Personally I am of east-Asian background and have little knowledge about accents. However: the upstream ibus Wiki mentioned some important setup at https://github.com/ibus/ibus/wiki/WaylandDesktop#plasma-wayland-desktop-environment-kde-1 , and you may want to follow it and see if your issue could be solved. That page seems to be mentioning the explicit set up of Compose Key. Will that solve your problem? Please let me know. If not, you may have to go back to use solution (1) above. I don't think your issue can be easily solved out-of-box from the ibus package side or the im-config package side, since you are using a rare combination of tools. I hope these information can be helpful. Do let me know if you have any other questions. I think it will be hard as we don't have a good, unified IM (Input Method) solution towards Wayland, no matter ibus/fcitx5, or GNOME/KDE. And we are late in the release cycle. IBus Wayland guide: https://github.com/ibus/ibus/wiki/WaylandDesktop Fcitx5 Wayland guide: https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland (No other IM framework provides wayland support so we are not including them.) As you may see from the pages, the solution to different combinations (GTK2/3/4/Qt4/5/6, GNOME/KDE/others, ibus/fcitx5) is: -> scattered: environment variable, ~/.config/gtk-*/settings.ini, etc. Can im-config do modification for GTK-specific settings files? -> often unable to be automated and needs manual intervention: the proper config of ibus + wayland + plasma combination needs configuration in KDE systemsettings. Even if automated, Compose Key must be manually set. -> and even sometimes contradictory: X11/Qt4 Apps needs environment variables, but Apps with good native Wayland support (GTK4/Qt6) do not want them. Asking users to set per-App environment variable (as proposed by fcitx5 upstream) is unrealistic. I haven't even looked into Wayland desktop environments other than GNOME and Plasma. The failsafe status quo of setting environment variables (*_IM_MODULE=fcitx/ibus) is ugly under wayland scenario, but it will guarantee things to be working (albeit UI glitches may occur, like https://fcitx-im.org/wiki/FAQ#Candidate_window_is_blinking_under_wayland_with_Fcitx_5 ). The downside to UI is the pop-up window from IM framework saying that these environment variables should be unset. Personally I would propose patching ibus/fcitx5, and modify repeated pop-up window from IM framework in the current release cycle. This is ugly. If you have any other suggestions, please let me know. Thanks, Boyuan Yang
Hi,
It's more than an issue about WPS office, but another "non-GNOME not supported well" one. It would be better to reduce user confusion, like blacklisting IBus in some cases for example, but I believe it's not what ibus package can provide. Anyway there exist workarounds, so the issue is closed.