Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Some issues with ibus vs fcitx input methods
-
- Posts: 26
- Joined: 2011-02-14 10:41
- Has thanked: 3 times
Some issues with ibus vs fcitx input methods
Hello Friends,
I have installed Debian Bullseye 11.4 KDE 64 bits version OS on my home desktop last week. As of now, it is working very well. However I am facing a minor issue with keyboard input method. That is I see there are two input methods available on my desktop - IBus and Fcitx.
On fresh boot, I see Ibus icon on the system tray. However if I visit System settings->Regional Settings->Input Method, it either shows an error or shows a button to run Fcitx. Once I click that button , Ibus icon disappears from the tray and Fcitx icon appears. From here I am unable to return to Ibus.
I had installed unofficial version (with nonfree firmware) from debian.org website and these are the default configuration. I use English India and Kannada keyboard frequently. As such I wanted to know what is the correct way of configuring dual keyboard input methods in Debian KDE, I have attached some screenshots I was referring to in above section. Let me know if you need any further details to respond to my query. Thanks in advance,
Regards
Ganesh
I have installed Debian Bullseye 11.4 KDE 64 bits version OS on my home desktop last week. As of now, it is working very well. However I am facing a minor issue with keyboard input method. That is I see there are two input methods available on my desktop - IBus and Fcitx.
On fresh boot, I see Ibus icon on the system tray. However if I visit System settings->Regional Settings->Input Method, it either shows an error or shows a button to run Fcitx. Once I click that button , Ibus icon disappears from the tray and Fcitx icon appears. From here I am unable to return to Ibus.
I had installed unofficial version (with nonfree firmware) from debian.org website and these are the default configuration. I use English India and Kannada keyboard frequently. As such I wanted to know what is the correct way of configuring dual keyboard input methods in Debian KDE, I have attached some screenshots I was referring to in above section. Let me know if you need any further details to respond to my query. Thanks in advance,
Regards
Ganesh
- Attachments
-
- default view.png (154.14 KiB) Viewed 3676 times
-
- fcitx.png (160.61 KiB) Viewed 3676 times
-
- Posts: 18
- Joined: 2022-08-15 23:15
- Has thanked: 2 times
Re: Some issues with ibus vs fcitx input methods
I don't necessarily like to recommend a fresh install however I following my suggestions which I will include later on in my response would help you to help us be better able to assist you then i\I will not shy away from sucha recommendation.
My first recommendation would be to try a differnet desk top environment for example a lighter weight one such as lxqt or xfce might free up some system resources which could well aid us in further diagnosing and fixing your issues. might I also recommend that you provide us with the necessary l related log files.
Thanks,
Chip
My first recommendation would be to try a differnet desk top environment for example a lighter weight one such as lxqt or xfce might free up some system resources which could well aid us in further diagnosing and fixing your issues. might I also recommend that you provide us with the necessary l related log files.
Thanks,
Chip
-
- Posts: 26
- Joined: 2011-02-14 10:41
- Has thanked: 3 times
Re: Some issues with ibus vs fcitx input methods
Hello @flashydolphin8827,flashydolphin8827 wrote: ↑2022-08-16 20:30 I don't necessarily like to recommend a fresh install however I following my suggestions which I will include later on in my response would help you to help us be better able to assist you then i\I will not shy away from sucha recommendation.
My first recommendation would be to try a differnet desk top environment for example a lighter weight one such as lxqt or xfce might free up some system resources which could well aid us in further diagnosing and fixing your issues. might I also recommend that you provide us with the necessary l related log files.
Thanks,
Chip
Thank you for your response. To ensure there was no corruption in the installed media or any software conflicts, I tried booting the system from live Debian image downloaded from https://cdimage.debian.org/cdimage/unof ... onfree.iso. I have copied the iso file on a pen drive and booted the live OS. On fresh boot, I have found the same issue prevalent. I am attaching the screenshots from the live OS session.
So it is confirmed that this issue is present in the installer media itself. I am sure there should be a way to mitigate it. But not sure how. Personally I like KDE plasma desktop environment more than any other, hence not trying to switch out.
Regards
Ganesh
- Attachments
-
- afterclick.png (66.98 KiB) Viewed 3575 times
-
- Error 1.png (92.33 KiB) Viewed 3573 times
-
- Error 2.png (66.89 KiB) Viewed 3573 times
Re: Some issues with ibus vs fcitx input methods
Is kde-config-fcitx installed ?
From a terminal, what is reporting this ?
From a terminal, what is reporting this ?
Code: Select all
/usr/bin/kbd-layout-viewer
-
- Posts: 26
- Joined: 2011-02-14 10:41
- Has thanked: 3 times
Re: Some issues with ibus vs fcitx input methods
Hello @L_V,L_V wrote: ↑2022-08-20 09:48 Is kde-config-fcitx installed ?
From a terminal, what is reporting this ?Code: Select all
/usr/bin/kbd-layout-viewer
Thank for your response. I tried executing the command as guided by you on my existing installation and bootable live OS. Both gave the similar results Screenshot attached. I see there are a few app shortcuts for fcitx. So I assume application package is installed already. Kindly let me know if any further details are needed from my side. Thanks in advance.
Regards
Ganesh
- Attachments
-
- Screenshot_20220821_124455.png (78.92 KiB) Viewed 3544 times
-
- Fcotx shortcuts.png (32.08 KiB) Viewed 3544 times
Re: Some issues with ibus vs fcitx input methods
I cannot help that much because your request is not clear to me.ganeshmallyap wrote: ↑2022-08-11 14:21 hat is I see there are two input methods available on my desktop - IBus and Fcitx.
To clarify, do you need two input methods ?
Why do you need Fcitx ?
Can you remove one you don't need ?
For investigation:
Code: Select all
# apt install fcitx-hangul kde-config-fcitx kde-config-fcitx5 fcitx-bin fcitx5-config-qt fcitx-frontend-qt5
-> any change ?
Can you report this
Code: Select all
ps ax |grep '[f]citx'
Code: Select all
apt list -i *ibus*
Code: Select all
apt list -i *fcitx*
Code: Select all
im-config
Code: Select all
fcitx-diagnose
-
- Posts: 26
- Joined: 2011-02-14 10:41
- Has thanked: 3 times
Re: Some issues with ibus vs fcitx input methods
Hello @L_V.,L_V wrote: ↑2022-08-21 10:12I cannot help that much because your request is not clear to me.ganeshmallyap wrote: ↑2022-08-11 14:21 hat is I see there are two input methods available on my desktop - IBus and Fcitx.
To clarify, do you need two input methods ?
Why do you need Fcitx ?
Can you remove one you don't need ?
For investigation:Close and reopen systemsettingsCode: Select all
# apt install fcitx-hangul kde-config-fcitx kde-config-fcitx5 fcitx-bin fcitx5-config-qt fcitx-frontend-qt5
-> any change ?
Can you report thisCode: Select all
ps ax |grep '[f]citx'
Code: Select all
apt list -i *ibus*
+ see what is said by launching this commandCode: Select all
apt list -i *fcitx*
Code: Select all
im-config
Code: Select all
fcitx-diagnose
Thanks once again for your prompt response. My queries were more to do from choosing what is right for me and why was error coming up on system settings application. I was not sure if ibus and fcitx could be used independently. If I were to chose one among these two, and it will still work without any issues, then I will go with ibus, as I find it more relevant for myself. It would be very helpful if you can kindly let me know what packages do I need to uninstall to remove fcitx. Thanks in advance.
I have pasted outputs of various commands from konsole as indicated in your message.
Code: Select all
ganeshp@anugmp-c2030:~$ sudo apt install fcitx-hangul kde-config-fcitx kde-config-fcitx5 fcitx-bin fcitx5-config-qt fcitx-frontend-qt
[sudo] password for ganeshp:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package fcitx-frontend-qt
ganeshp@anugmp-c2030:~$ sudo apt install fcitx-hangul kde-config-fcitx kde-config-fcitx5 fcitx-bin fcitx5-config-qt
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
fcitx-bin is already the newest version (1:4.2.9.8-3).
fcitx-bin set to manually installed.
kde-config-fcitx is already the newest version (0.5.6-2).
kde-config-fcitx set to manually installed.
fcitx5-config-qt is already the newest version (5.0.3-3).
fcitx5-config-qt set to manually installed.
kde-config-fcitx5 is already the newest version (5.0.3-3).
kde-config-fcitx5 set to manually installed.
The following additional packages will be installed:
libhangul-data libhangul1
The following NEW packages will be installed:
fcitx-hangul libhangul-data libhangul1
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,951 kB of archives.
After this operation, 6,892 kB of additional disk space will be used.
Do you want to continue? [Y/n]
ganeshp@anugmp-c2030:~$ sudo apt install fcitx-hangul kde-config-fcitx kde-config-fcitx5 fcitx-bin fcitx5-config-qt
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
fcitx-bin is already the newest version (1:4.2.9.8-3).
fcitx-bin set to manually installed.
kde-config-fcitx is already the newest version (0.5.6-2).
kde-config-fcitx set to manually installed.
fcitx5-config-qt is already the newest version (5.0.3-3).
fcitx5-config-qt set to manually installed.
kde-config-fcitx5 is already the newest version (5.0.3-3).
kde-config-fcitx5 set to manually installed.
The following additional packages will be installed:
libhangul-data libhangul1
The following NEW packages will be installed:
fcitx-hangul libhangul-data libhangul1
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,951 kB of archives.
After this operation, 6,892 kB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
ganeshp@anugmp-c2030:~$ ps ax |grep '[f]citx'
ganeshp@anugmp-c2030:~$ apt list -i *ibus*
Listing... Done
gir1.2-ibus-1.0/stable,now 1.5.23-2 amd64 [installed,automatic]
ibus-data/stable,now 1.5.23-2 all [installed,automatic]
ibus-gtk3/stable,now 1.5.23-2 amd64 [installed,automatic]
ibus-gtk/stable,now 1.5.23-2 amd64 [installed,automatic]
ibus/stable,now 1.5.23-2 amd64 [installed]
libibus-1.0-5/stable,now 1.5.23-2 amd64 [installed,automatic]
libusb-1.0-0-dev/stable,now 2:1.0.24-3 amd64 [installed,automatic]
libusb-1.0-0/stable,now 2:1.0.24-3 amd64 [installed,automatic]
libusb-1.0-doc/stable,now 2:1.0.24-3 all [installed,automatic]
libusbmuxd6/stable,now 2.0.2-3 amd64 [installed,automatic]
libusbredirparser1/stable,now 0.8.0-1+b1 amd64 [installed,automatic]
python3-ibus-1.0/stable,now 1.5.23-2 all [installed,automatic]
scribus-data/stable,now 1.5.6.1+dfsg-2 all [installed,automatic]
scribus/stable,now 1.5.6.1+dfsg-2 amd64 [installed]
ganeshp@anugmp-c2030:~$ apt list -i *fcitx*
Listing... Done
fcitx-bin/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
fcitx-config-common/stable,now 0.4.10-3 all [installed,automatic]
fcitx-config-gtk/stable,now 0.4.10-3 amd64 [installed,automatic]
fcitx-data/stable,now 1:4.2.9.8-3 all [installed,automatic]
fcitx-frontend-all/stable,now 1:4.2.9.8-3 all [installed,automatic]
fcitx-frontend-gtk2/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
fcitx-frontend-gtk3/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
fcitx-frontend-qt5/stable,now 1.2.5-1+b2 amd64 [installed,automatic]
fcitx-m17n/stable,now 0.2.4-2 amd64 [installed,automatic]
fcitx-module-dbus/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
fcitx-module-kimpanel/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
fcitx-module-lua/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
fcitx-module-x11/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
fcitx-modules/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
fcitx-pinyin/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
fcitx-table-amharic/stable,now 0.2.4-2 all [installed,automatic]
fcitx-table-malayalam-phonetic/stable,now 0.2.4-2 all [installed,automatic]
fcitx-table/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
fcitx-ui-classic/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
fcitx5-chewing/stable,now 5.0.3-1 amd64 [installed,automatic]
fcitx5-chinese-addons-bin/stable,now 5.0.4-1+deb11u1 amd64 [installed,automatic]
fcitx5-chinese-addons-data/stable,now 5.0.4-1+deb11u1 all [installed,automatic]
fcitx5-chinese-addons/stable,now 5.0.4-1+deb11u1 all [installed,automatic]
fcitx5-config-qt/stable,now 5.0.3-3 amd64 [installed,automatic]
fcitx5-data/stable,now 5.0.5-1 all [installed,automatic]
fcitx5-frontend-gtk3/stable,now 5.0.3-1 amd64 [installed,automatic]
fcitx5-frontend-qt5/stable,now 5.0.3-1 amd64 [installed,automatic]
fcitx5-module-chttrans/stable,now 5.0.4-1+deb11u1 amd64 [installed,automatic]
fcitx5-module-cloudpinyin/stable,now 5.0.4-1+deb11u1 amd64 [installed,automatic]
fcitx5-module-emoji/stable,now 5.0.5-1 amd64 [installed,automatic]
fcitx5-module-fullwidth/stable,now 5.0.4-1+deb11u1 amd64 [installed,automatic]
fcitx5-module-pinyinhelper/stable,now 5.0.4-1+deb11u1 amd64 [installed,automatic]
fcitx5-module-punctuation/stable,now 5.0.4-1+deb11u1 amd64 [installed,automatic]
fcitx5-module-quickphrase-editor/stable,now 1.2.5-1+b2 amd64 [installed,automatic]
fcitx5-module-quickphrase/stable,now 5.0.5-1 amd64 [installed,automatic]
fcitx5-module-wayland/stable,now 5.0.5-1 amd64 [installed,automatic]
fcitx5-module-xorg/stable,now 5.0.5-1 amd64 [installed,automatic]
fcitx5-modules/stable,now 5.0.5-1 amd64 [installed,automatic]
fcitx5-pinyin/stable,now 5.0.4-1+deb11u1 amd64 [installed,automatic]
fcitx5-table/stable,now 5.0.4-1+deb11u1 amd64 [installed,automatic]
fcitx5/stable,now 5.0.5-1 amd64 [installed,automatic]
fcitx/stable,now 1:4.2.9.8-3 all [installed,automatic]
kde-config-fcitx5/stable,now 5.0.3-3 amd64 [installed,automatic]
kde-config-fcitx/stable,now 0.5.6-2 amd64 [installed,automatic]
libfcitx-config4/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
libfcitx-core0/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
libfcitx-gclient1/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
libfcitx-qt5-1/stable,now 1.2.5-1+b2 amd64 [installed,automatic]
libfcitx-qt5-data/stable,now 1.2.5-1 all [installed,automatic]
libfcitx-utils0/stable,now 1:4.2.9.8-3 amd64 [installed,automatic]
libfcitx5-qt-data/stable,now 5.0.3-1 all [installed,automatic]
libfcitx5-qt1/stable,now 5.0.3-1 amd64 [installed,automatic]
libfcitx5config6/stable,now 5.0.5-1 amd64 [installed,automatic]
libfcitx5core7/stable,now 5.0.5-1 amd64 [installed,automatic]
libfcitx5gclient1/stable,now 5.0.3-1 amd64 [installed,automatic]
libfcitx5utils2/stable,now 5.0.5-1 amd64 [installed,automatic]
ganeshp@anugmp-c2030:~$ fcitx-diagnose
# System Info:
1. `uname -a`:
Linux anugmp-c2030 5.10.0-17-amd64 #1 SMP Debian 5.10.136-1 (2022-08-13) x86_64 GNU/Linux
2. `lsb_release -a`:
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
3. `lsb_release -d`:
Description: Debian GNU/Linux 11 (bullseye)
4. `/etc/lsb-release`:
`/etc/lsb-release` not found.
5. `/etc/os-release`:
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
6. Desktop Environment:
Desktop environment is `kde`.
7. Bash Version:
BASH_VERSION='5.1.4(1)-release'
# Environment:
1. DISPLAY:
DISPLAY=':0'
2. Keyboard Layout:
1. `setxkbmap`:
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+in(eng)+inet(evdev)" };
xkb_geometry { include "pc(pc105)" };
};
2. `xprop`:
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "in", "eng", ""
3. Locale:
1. All locale:
C
C.UTF-8
en_IN
en_IN.utf8
en_US.utf8
POSIX
2. Current locale:
LANG=en_IN.UTF-8
LANGUAGE=
LC_CTYPE="en_IN.UTF-8"
LC_NUMERIC=en_IN
LC_TIME=en_IN
LC_COLLATE="en_IN.UTF-8"
LC_MONETARY=en_IN
LC_MESSAGES="en_IN.UTF-8"
LC_PAPER=en_IN
LC_NAME=en_IN
LC_ADDRESS=en_IN
LC_TELEPHONE=en_IN
LC_MEASUREMENT=en_IN
LC_IDENTIFICATION=en_IN
LC_ALL=
4. Directories:
1. Home:
/home/ganeshp
2. `${XDG_CONFIG_HOME}`:
Environment variable `XDG_CONFIG_HOME` is not set.
Current value of `XDG_CONFIG_HOME` is `~/.config` (`/home/ganeshp/.config`).
3. Fcitx Settings Directory:
Current fcitx settings directory is `~/.config/fcitx` (`/home/ganeshp/.config/fcitx`).
5. Current user:
The script is run as ganeshp (1000).
# Fcitx State:
1. executable:
Found fcitx at `/usr/bin/fcitx`.
2. version:
Fcitx version: `4.2.9.8`
3. process:
**Fcitx is not running.**
**Please check the Configure link of your distribution in [Beginner's Guide](http://fcitx-im.org/wiki/Beginner%27s_Guide) for how to setup fcitx autostart.**
# Fcitx Configure UI:
1. Config Tool Wrapper:
Found fcitx-configtool at `/usr/bin/fcitx-configtool`.
2. Config GUI for gtk2:
**Config GUI for gtk2 not found.**
3. Config GUI for gtk3:
Found `fcitx-config-gtk3` at `/usr/bin/fcitx-config-gtk3`.
4. Config GUI for kde:
**`kcmshell4` not found.**
# Frontends setup:
## Xim:
1. `${XMODIFIERS}`:
**Environment variable XMODIFIERS is "@im=ibus" instead of "@im=fcitx". Please check if you have exported it incorrectly in any of your init files.**
**Please set environment variable XMODIFIERS to "@im=fcitx" using the tool your distribution provides or add `export XMODIFIERS=@im=fcitx` to your `~/.xprofile`. See [Input Method Related Environment Variables: XMODIFIERS](http://fcitx-im.org/wiki/Input_method_related_environment_variables#XMODIFIERS).**
Xim Server Name from Environment variable is ibus.
2. XIM_SERVERS on root window:
Xim server name is the same with that set in the environment variable.
## Qt:
1. qt4 - `${QT4_IM_MODULE}`:
**Environment variable QT_IM_MODULE is "ibus" instead of "fcitx". Please check if you have exported it incorrectly in any of your init files.**
**You may have trouble using fcitx in qt4 programs.**
**Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add `export QT_IM_MODULE=fcitx` to your `~/.xprofile`. See [Input Method Related Environment Variables: QT_IM_MODULE](http://fcitx-im.org/wiki/Input_method_related_environment_variables#QT_IM_MODULE).**
2. qt5 - `${QT_IM_MODULE}`:
**Environment variable QT_IM_MODULE is "ibus" instead of "fcitx". Please check if you have exported it incorrectly in any of your init files.**
**You may have trouble using fcitx in qt5 programs.**
**Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add `export QT_IM_MODULE=fcitx` to your `~/.xprofile`. See [Input Method Related Environment Variables: QT_IM_MODULE](http://fcitx-im.org/wiki/Input_method_related_environment_variables#QT_IM_MODULE).**
3. Qt IM module files:
Found unknown fcitx qt module: `/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_fcitx.so`.
Found unknown fcitx qt module: `/usr/lib/x86_64-linux-gnu/qt5/plugins/kcms/kcm_fcitx5.so`.
Found unknown fcitx qt module: `/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so`.
Found fcitx im module for Qt5: `/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so`.
Found unknown fcitx qt module: `/usr/lib/x86_64-linux-gnu/fcitx5/qt5/libfcitx-quickphrase-editor5.so`.
Found fcitx qt module: `/usr/lib/x86_64-linux-gnu/fcitx/qt/libfcitx-quickphrase-editor5.so`.
**Cannot find fcitx input method module for Qt4.**
## Gtk:
1. gtk - `${GTK_IM_MODULE}`:
**Environment variable GTK_IM_MODULE is "ibus" instead of "fcitx". Please check if you have exported it incorrectly in any of your init files.**
**You may have trouble using fcitx in gtk programs.**
**Please set environment variable GTK_IM_MODULE to "fcitx" using the tool your distribution provides or add `export GTK_IM_MODULE=fcitx` to your `~/.xprofile`. See [Input Method Related Environment Variables: GTK_IM_MODULE](http://fcitx-im.org/wiki/Input_method_related_environment_variables#GTK_IM_MODULE).**
2. `gtk-query-immodules`:
1. gtk 2:
**Cannot find `gtk-query-immodules` for gtk 2**
**Cannot find fcitx im module for gtk 2.**
2. gtk 3:
**Cannot find `gtk-query-immodules` for gtk 3**
**Cannot find fcitx im module for gtk 3.**
3. Gtk IM module cache:
1. gtk 2:
Found immodules cache for gtk `2.24.33` at `/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules.cache`.
Version Line:
# Created by /usr/lib/x86_64-linux-gnu/libgtk2.0-0/gtk-query-immodules-2.0 from gtk+-2.24.33
Found fcitx im modules for gtk `2.24.33`.
"/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-fcitx.so"
"fcitx" "Fcitx (Flexible Input Method Framework)" "fcitx" "/usr/share/locale" "ja:ko:zh:*"
2. gtk 3:
Found immodules cache for gtk `3.24.24` at `/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules.cache`.
Version Line:
# Created by /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 from gtk+-3.24.24
Found fcitx im modules for gtk `3.24.24`.
"/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx.so"
"fcitx" "Fcitx (Flexible Input Method Framework)" "fcitx" "/usr/share/locale" "ja:ko:zh:*"
"/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx5.so"
"fcitx" "Fcitx5 (Flexible Input Method Framework5)" "fcitx5" "/usr/locale" "ja:ko:zh:*"
"fcitx5" "Fcitx5 (Flexible Input Method Framework5)" "fcitx5" "/usr/locale" "ja:ko:zh:*"
4. Gtk IM module files:
1. gtk 2:
All found Gtk 2 immodule files exist.
2. gtk 3:
All found Gtk 3 immodule files exist.
# Configuration:
## Fcitx Addons:
1. Addon Config Dir:
Found fcitx addon config directory: `/usr/share/fcitx/addon`.
2. Addon List:
1. Found 28 enabled addons:
fcitx-autoeng
fcitx-chttrans
fcitx-classic-ui
fcitx-clipboard
fcitx-dbus
fcitx-freedesktop-notify
fcitx-fullwidth-char
fcitx-imselector
fcitx-ipc
fcitx-ipcportal
fcitx-keyboard
fcitx-kimpanel-ui
fcitx-lua
fcitx-m17n
fcitx-notificationitem
fcitx-pinyin
fcitx-pinyin-enhance
fcitx-punc
fcitx-quickphrase
fcitx-remote
fcitx-spell
fcitx-table
fcitx-unicode
fcitx-vk
fcitx-x11
fcitx-xim
fcitx-xkb
fcitx-xkbdbus
2. Found 0 disabled addons:
3. Addon Libraries:
All libraries for all addons are found.
4. User Interface:
Found 2 enabled user interface addons:
fcitx-classic-ui
fcitx-kimpanel-ui
## Input Methods:
1. Found 1 enabled input methods:
fcitx-keyboard-in-eng
2. Default input methods:
You only have one keyboard input method enabled. You may want to add another input method to input other languages.
# Log:
1. `date`:
Sunday 21 August 2022 10:20:43 PM IST
2. `~/.config/fcitx/log/`:
total 0
3. `~/.config/fcitx/log/crash.log`:
`~/.config/fcitx/log/crash.log` not found.
Ganesh
- Attachments
-
- im-config.png (100.53 KiB) Viewed 3495 times
Re: Some issues with ibus vs fcitx input methods
The problem is that I even don't know why you installed fcitx if you don't need it. First time I see fcitx !ganeshmallyap wrote: ↑2022-08-21 17:09 My queries were more to do from choosing what is right for me ]
I assumed you need something very special, something I am not familiar with.
If finally you think you don't need fcitx , you can uninstall like this:
Code: Select all
apt remove $(dpkg -l |awk '$1$2~/^i.*fcitx/{print $2}')
Re: Some issues with ibus vs fcitx input methods
As one of our SOP, after we installed Debian, one of the first commands we executed was
sudo apt update;; sudo apt purge fcitx* uim*;; sudo apt autoremove;; sudo apt install ibus-libpinyin
Even as late as last year, removing fcitx packages seemed to affect libpinyin, but this problem has been solved.
sudo apt update;; sudo apt purge fcitx* uim*;; sudo apt autoremove;; sudo apt install ibus-libpinyin
Even as late as last year, removing fcitx packages seemed to affect libpinyin, but this problem has been solved.
Last edited by pwzhangzz on 2022-08-21 17:59, edited 1 time in total.
-
- Posts: 26
- Joined: 2011-02-14 10:41
- Has thanked: 3 times
Re: Some issues with ibus vs fcitx input methods
Hello @L_V, @pwzhangzz,
Sincere thanks for your inputs and guidance on the topic. Yes, now I am able to cleanly uninstall fcitx components. Ibus is working fine. I normally need 2 language keyboards - English and Kannada. Both the keyboards are working just fine with ibus.
@L.V, wanted to clarity on one point. I neither installed fcitx nor ibus. Both came preinstalled on freshly installed OS image on my desktop. I had used bootable live iso provided at debian website. Personally I feel it would be better if installer can offer any one of these two input methods to users during install.
Regards
Ganesh
Sincere thanks for your inputs and guidance on the topic. Yes, now I am able to cleanly uninstall fcitx components. Ibus is working fine. I normally need 2 language keyboards - English and Kannada. Both the keyboards are working just fine with ibus.
@L.V, wanted to clarity on one point. I neither installed fcitx nor ibus. Both came preinstalled on freshly installed OS image on my desktop. I had used bootable live iso provided at debian website. Personally I feel it would be better if installer can offer any one of these two input methods to users during install.
Regards
Ganesh
Re: Some issues with ibus vs fcitx input methods
I'm surprised of this. im-config recommends to install only one.ganeshmallyap wrote: ↑2022-08-22 16:26 Both came preinstalled on freshly installed OS image on my desktop
I never install full OS images (too bloated).
ibus is normally the default one when a basic system is installed.
Anyway, it works, and that's the most important !