Replies: 7 comments 5 replies
-
I have tested out the generated fcitx and the the ibus versions of OBK yesterday, KDE on Fedora 39 just won't work with any of them. When I install the fcitx version, rpm-ostree/dnf also needs to download fcitx, so by default Fedora KDE doesn't even ship with fcitx. After installing the fcitx version of OBK, no additional keyboard shows under the Layouts menu, even after I chose fcitx under the Virtual Keyboard menu, unlike in GNOME where OBK will show up as an input method. So I uninstalled the fcitx OBK and installed the standard ibus OBK, set ibus Wayland as the Virtual Keyboard, then went to the Layouts menu, where an OBK layout option still was not present. As a last-ditch effort I used the ibus-setup command in a terminal to access the ibus configuration GUI, where I could add OBK as an additional layout, it then showed up as an additional input method on the input method selector of KDE, but any attempt to switch to it would cause terrible lag and OBK would not work. So far I donot know if this is an issue with KDE or Fedora,or maybe even a bug on OBK, as I did compile the fcitx version from the develop branch, but the ibus OBK rpm for F38 in the Release tab works flawlessly with F39 on GNOME |
Beta Was this translation helpful? Give feedback.
-
version 2.0.0
I installed it via rpm-ostree, rpm-ostree overlays additional packages on top of an OSTree image. Another thing is that in my own personal experience, KDE tends to be extremely buggy and break stuff even between minor updates, so it could be that it is just a transient issue. I will also check under a Debian 12 KDE VM just to be extra sure. |
Beta Was this translation helpful? Give feedback.
-
I installed Fedora 37 inside a VM, then compiled and tested OBK Fcitx inside of it. As you can see, the setup process is not straightforward at all, before installing OBK Fcitx there was only None and Malit virtual keyboards. However, a new Keyboard icon then popped up in the taskbar, I had to use that to get OBK Fcitx working, it was smooth sailing after that. Although my previous test was on Fedora Kinoite 39, knowing how KDE can be, it was probably a regression/bug of some sorts instead of an issue related to OStree, as I have been using OBK ibus on Silverblue 38/39 with zero issues. |
Beta Was this translation helpful? Give feedback.
-
https://github.com/OpenBangla/OpenBangla-Keyboard/wiki/Configure-on-KDE-(Fcitx) I have written a reasonably detailed wiki article on how to configure OBK Fcitx on KDE, hope this will help someone. |
Beta Was this translation helpful? Give feedback.
-
If this gets merged to the master branch then the KDE or any other Qt environment installation methods should ditch IBus in the installation guide/script. As IBus doesnt really play nicely with those desktops...Only working best on GTK based desktops like GNOME or Cinnamon. |
Beta Was this translation helpful? Give feedback.
-
Just as a disclaimer, The issue I have described here: #357 (comment) about Fcitx not showing up under Virtual Keyboards option in KDE Plasma 5.27.9 Wayland is a bug which happens at random. If you install OBK Fcitx and the Fcitx option still doesn't appear under the Virtual Keyboards option, you should uninstall OBK Fcitx, reboot your computer and reinstall OBK Fcitx (preferably also do a reboot after a reinstall). Would also like to confirm that OBK Fcitx works flawlessly under KDE Plasma 6 Beta 1 on Fedora 40 Rawhide with no apparent issues in the 2-3 days I have tested KDE Plasma 6 Beta. |
Beta Was this translation helpful? Give feedback.
-
As make-pkgs has been merged, this article is now redundant, makes sense to close this. |
Beta Was this translation helpful? Give feedback.
-
As OBK still does not have fcitx rpms in release tab, it has prevented users like me who intended on using Fedora Kinoite quite a headache, as the standard "make install" commands will probably not work
However, I have successfully managed to generate rpm packages with fcitx support by using/modifying commands from
#213
https://github.com/OpenBangla/OpenBangla-Keyboard/blob/master/tools/build.sh
This guide is primarily intended to document the process.
You need to use some kind of container like Toolbox/Distrobox with a relatively recent Fedora image.
For toolbox it is :
toolbox create && toolbox enter
You need to install dependencies and update the image by doing the following.
sudo dnf -y update && sudo dnf -y install @buildsys-build rust cargo cmake qt5-qtdeclarative-devel libzstd-devel fcitx5 fcitx5-devel ninja-build curl meson
You need to clone the git repo, switch to develop branch and update repos
cmake -Bbuild -GNinja -DCPACK_GENERATOR=RPM -DCMAKE_INSTALL_PREFIX="/usr" -DENABLE_FCITX=ON && ninja package -C build
the generated rpm will be inside the build folder
Beta Was this translation helpful? Give feedback.
All reactions