Hi, this is just FYI. Upcoming "IBus in a Plasma (Wayland) session" is interesting topic.
Since it may be related, let me quote interesting links from my previous post at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054622#25 * Input Method Hub -- good overview https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/39 * Wayland and input methods -- wayland-protocol description https://dorotac.eu/posts/input_method/ * Using Fcitx 5 on Wayland -- view by fcitx community https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland * about Input Method wayland protocols #2331 -- view by ibus maintainer https://github.com/ibus/ibus/issues/2331 * New ideas using Wayland Input Methods -- view by QT people? August 3, 2023 https://blog.davidedmundson.co.uk/blog/new-ideas-using-wayland-input-methods/ Out of all these linked pages, the following table may be useful for resolving this bug (I may be wrong): https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/39#implementation-matrix Regards, Osamu On Fri, 2023-09-15 at 23:47 +0200, Gunnar Hjalmarsson wrote: > Package: im-config > Version: 0.57-2 > Severity: important > > If you use IBus in a Plasma (Wayland) session, the intention seems to be > that you apply an "IBus Wayland" virtual keyboard and let Wayland handle > everything internally. Otherwise the suggestion window does not show up, > for instance. OTOH, with the virtual keyboard enabled im-config should > better be disabled. > > In a Plasma (X11) session im-config keeps dealing with IBus as intended. > > Probably we should change im-config so it doesn't do anything in case of > a Plasma (Wayland) session. However, during my tests things get > extremely slow with that "IBus Wayland" virtual keyboard enabled, which > may be a bug or a "user error" from my side. > > In any case it's highly desirable that any changes are made in > consultation with somebody who actually uses IBus together with Plasma. >
