Typing issue: Maximum conversion candidate results limit of 100 seems to hide conversion of given name 凱 (かい) (kai) when typed with only lower case letters.

[AlexFolland]

Category of the typing issue

1. Out-of-vocabulary (e.g. "凱" is not in the candidate list at all when typed with only lower-case letters).

Issues

Write issues to the following table. (It's in the markdown format)

input [e.g.ゆうひ]	expected [e.g. 夕日]	actual [e.g. ユウヒ]
kai -> かい	凱	limit of 100 results not including 凱

Version or commit-id

2.26.4632.102.g4d2e3bd-2

You can get the version string by converting "Version" or "ばーじょん".

Aside: This did not seem to be true, by the way. I tried converting "Version" and it just gave me "Version" as the only conversion candidate. ばーじょん also did not show the version number among its conversion candidates, even when typing "ba-jyonn" which was able to produce ばーじょん in hiragana before conversion. I got the version number instead from querying my system package manager with pacman -Qi fcitx5-mozc.

Additional context

I am running Manjaro with the unstable branch and my system is up to date.

I looked through all 100 of the conversion results kanji that was displayed when typing "kai" which converted to "かい", and did not find 凱, which is the name of a family member. I noticed there is a limit of 100 conversion candidates, so I have a feeling that the conversion candidate exists, but would only be visible if the limit of 100 conversion results was raised or removed entirely. I did extensive research to try to find where to configure the limit of 100 conversion candidates and could not find anywhere that it could be configured. If 凱 does exist as a conversion candidate for かい when typed using lower-case romaji, then this issue report is focused primarily on raising or disabling the limit of 100 conversion candidates.

[mikunimaru]

Is it really Mozc? I think it's likely that Mozc is just installed, but another engine is enabled.

[AlexFolland]

I don't have any other Japanese engines installed. Here's a screenshot of my Fcitx 5 menu showing only Mozc as an enabled engine. I'm curious what makes you suspect it's a different engine. Is some behavior I've described different from what you expected? If so, what behavior is that?

[mikunimaru]

It usually looks like this.

Also, the version of Mozc in the official Manjaro (Arch Linux) package is very old. Get the latest packages from AUR etc.

For Arch Linux, you need to edit the environment variables and change the DE settings so that fcitx5 starts automatically at login.
I think it's probably the same with Manjaro.

[AlexFolland]

I guess the package I am using must be out of date and has some old limit of 100 conversion candidates. It is indeed mozc, but maybe just an old version before this issue was resolved and before the version querying system was implemented.

I see the upstream copy of this particular package was flagged out of date months ago here: https://archlinux.org/packages/extra/x86_64/fcitx5-mozc/

To work around the outdated package, I tried to install the fcitx5-mozc-git package from the AUR, but I was unable to install it. Part of the installation is trying to download a file named jigyosyo-202011.zip from https://osdn.net/projects/ponsfoot-aur/storage/mozc/jigyosyo-202011.zip, and that download fails with a certificate expiry error, which causes the installation to fail.

I will await a proper package update in the Arch Linux extra repository (which will be subsequently updated in the Manjaro stable extra repository) and/or a fix of the AUR package and test this again when either package has been able to be updated on my system.

[hiroyuki-komatsu]

Hi AlexFolland,

We have the entry of "かい → 凱".
https://github.com/google/mozc/blob/master/src/data/single_kanji/single_kanji.tsv#L627

So the latest version should be able to type 凱 from かい as mikunimaru mentioned.

I close this issue. Please feel free to reopen or update it, if you keep having a trouble with the latest version.

Thanks,

[AlexFolland]

I was able to update to the latest version of mozc from the AUR with the fcitx5-mozc-git by modifying the PKGBUILD file before installing the package and removing the "s" from the "https" sources for the 2 zip files from the OSDN server, working around their expired SSL certificate and allowing curl to download the files.

After the update and a reboot, this issue still manifests. There is still a limit of 100 candidates, and 凱 was still not in that limited list of candidates. I noticed I could work around the issue by typing "Kai" with an upper-case "K", but that was not explained anywhere and not expected. I thought upper and lower case were not relevant to the sounds that are produced.

However, that does not solve the issue of the limit of 100 candidates, which I still don't see an issue ticket for anywhere. How do I remove the limit of 100 candidates? Nothing explains this limit anywhere on the internet, even after hours of researching. Can any developer point me in the right direction toward removing that limit? I am extremely confused as to why my copy of mozc has a limit of 100 candidates and the one in the screenshots shown by @mikunimaru does not. Is this limit only applied on Linux and not on Windows or macOS, or something like that? If so, how can I fix mozc or fcitx to not have that limit?

I'm also confused about why typing ba-jonn does not show the version in my copy. Something's not right, and there's no clear documentation on this anywhere that I can find.

[yukawa]

Is this limit only applied on Linux and not on Windows or macOS, or something like that? If so, how can I fix mozc or fcitx to not have that limit?

Mozc itself doesn't have such a limitation on Windows and macOS. Most likely the limitation is coming from fcitx, which is maintained in a different repository by different developers.

I'm also confused about why typing ba-jonn does not show the version in my copy. Something's not right, and there's no clear documentation on this anywhere that I can find.

Try exactly the following steps.

1. Hit b key
2. Hit a key
3. Hit - key
4. Hit j key
5. Hit o key
6. Hit n key
7. Hit n key
8. Hit Space key
9. Hit Space key

Note that hitting Tab key doesn't trigger this.

[AlexFolland]

Yes, this works with space, but not the down arrow key or tab! I'm so confused by this. I had no idea there was a way to get a different list of candidates that's better. Thanks for this info, even though I only saw this comment 3 days later.

[AlexFolland]

I wish to reopen this ticket since I was told to "please feel free to reopen or update it, if you keep having trouble with the latest version", and I still have trouble with the latest version, as described in my previous comment, but I don't see a way to reopen it. Can someone please reopen it?

[mikunimaru]

It is very likely that an IME engine other than mozc is enabled. It is possible that another IME engine, perhaps installed as a dependency of other Japanese-related software, is already enabled. For example, even if you uninstall Mozc, will Japanese input still be possible? In that case, it is confirmed that a Japanese input engine other than Mozc is enabled.
What DE are you using? The settings that can be advised vary depending on the type of DE.

[AlexFolland]

No, Japanese input is not possible if I uninstall Mozc. It is the only Japanese IME engine that is installed. I do not have any other Japanese-related software installed.

When I switch input with the fcitx5 context menu, I am clicking specifically on a context menu list entry named "Mozc". This causes text that says "あ (Hiragana)" to appear in a tooltip at the typing cursor location in the focused text box.

Additionally, I have had no ability to enter Japanese text before I installed Mozc with my package manager.

I am using XFCE as my desktop environment, and I can change input sources with fcitx5 through its tray icon with either a left click on the icon or right-click on it and clicking "Mozc" in the list. I can also press Alt+Space on my keyboard to switch to Japanese input, but to confirm that I am using only Mozc for these tests, I have made sure I am clicking the "Mozc" entry in the fcitx5 tray icon context menu.

[mikunimaru]

I will install Manjaro in a virtual environment tomorrow and check it.
Can you install fcitx5-configtool and confirm that Mozc is included in the items?

[AlexFolland]

I will install Manjaro in a virtual environment tomorrow and check it.

Thank you. I expect this may help.

Can you install fcitx5-configtool and confirm that Mozc is included in the items?

Is that expected to show a different menu from the menu shown in the screenshot in my previous comment? I ran fcitx5-configtool and I see the same configuration menu that's pictured in my screenshot, with the same list as in my screenshot.

[mikunimaru]

There seems to be no problem with fcitx5 settings. My current guess is that ibus or fcitx (not fcitx5) is being prioritized and working as the Japanese IME. This is probably a bug that only occurs with the combination of Manjaro and xfce.

[AlexFolland]

OK, I've checked both of those possibilities. Ibus has no engines installed or set, and fcitx (not fcitx5) is not installed. Here is terminal output which may serve to prove that.

[alex@alex-pc ~]$ ibus list-engine

(ibus list-engine:1290786): IBUS-WARNING **: 00:55:57.320: ibus_bus_call_sync: org.freedesktop.DBus.Properties.Get: GDBus.Error:org.freedesktop.DBus.Error.UnknownProperty: Unknown interface org.freedesktop.IBus or property Engines.
[alex@alex-pc ~]$ ibus engine

(process:1290811): IBUS-WARNING **: 00:56:03.427: ibus_bus_call_sync: org.freedesktop.DBus.Properties.Get: GDBus.Error:org.freedesktop.DBus.Error.UnknownProperty: Unknown interface org.freedesktop.IBus or property GlobalEngine.
No engine is set.
[ble: exit 1]
[alex@alex-pc ~]$ pacman -Q fcitx
error: package 'fcitx' was not found
[ble: exit 1]
[alex@alex-pc ~]$ pacman -Q fcitx5
fcitx5-git 5.1.5.r48.g322eed31-1
[alex@alex-pc ~]$

If you have more suggestions for ways to test hypotheses, I am willing to run them and show the output.

[mikunimaru]

What are the environment variables for Japanese input? I also suspect that Manjaro may have automatically generated the wrong environment variables.
https://fcitx-im.org/wiki/Setup_Fcitx_5#Environment_variables

[AlexFolland]

Here is the output of env, which lists all environment variables and their values.

[alex@alex-pc ~]$ env
SHELL=/bin/bash
SESSION_MANAGER=local/alex-pc:@/tmp/.ICE-unix/2692,unix/alex-pc:/tmp/.ICE-unix/2692
WINDOWID=41418755
COLORTERM=truecolor
XDG_CONFIG_DIRS=/etc/xdg:/usr/share/manjaro-kde-settings/xdg:/etc/xdg
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
XDG_MENU_PREFIX=xfce-
GNOME_KEYRING_CONTROL=/run/user/1000/keyring
LC_ADDRESS=en_CA.UTF-8
VDPAU_DRIVER=nvidia
LC_NAME=en_CA.UTF-8
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
GRADLE_HOME=/usr/share/java/gradle
LIBVA_DRIVER_NAME=nvidia
DESKTOP_SESSION=xfce
LC_MONETARY=en_CA.UTF-8
FLUTTER_HOME=/opt/flutter
GTK_MODULES=canberra-gtk-module:canberra-gtk-module
XDG_SEAT=seat0
PWD=/home/alex
LOGNAME=alex
XDG_SESSION_DESKTOP=XFCE
QT_QPA_PLATFORMTHEME=qt5gtk2
XDG_SESSION_TYPE=x11
PANEL_GDK_CORE_DEVICE_EVENTS=0
XAUTHORITY=/tmp/xauth_EYyFsq
ftp_proxy=
MOTD_SHOWN=pam
HOME=/home/alex
MANGOHUD=1
LC_PAPER=en_CA.UTF-8
LANG=en_US.UTF-8
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.pdf=00;32:*.ps=00;32:*.txt=00;32:*.patch=00;32:*.diff=00;32:*.log=00;32:*.tex=00;32:*.doc=00;32:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:
XDG_CURRENT_DESKTOP=XFCE
VTE_VERSION=7402
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
https_proxy=
_ble_util_fd_zero=34
YAOURT_COLORS=nb=1:pkg=1:ver=1;32:lver=1;45:installed=1;42:grp=1;34:od=1;41;5:votes=1;44:dsc=0:other=1;35
socks_proxy=
MOZ_DISABLE_RDD_SANDBOX=1
_ble_util_fd_stdin=30
XDG_SESSION_CLASS=user
TERM=xterm-256color
LC_IDENTIFICATION=en_CA.UTF-8
USER=alex
PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket
DISPLAY=:0.0
SHLVL=1
_ble_util_fd_stderr=32
LC_TELEPHONE=en_CA.UTF-8
LC_MEASUREMENT=en_CA.UTF-8
XDG_VTNR=2
XDG_SESSION_ID=2
QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
http_proxy=
EMSDK_NODE=/usr/lib/emsdk/node/15.14.0_64bit/bin/node
_ble_util_fd_null=33
MOZ_PLUGIN_PATH=/usr/lib/mozilla/plugins
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
LC_TIME=en_GB.UTF-8
GTK3_MODULES=xapp-gtk3-module:xapp-gtk3-module
XDG_DATA_DIRS=/home/alex/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
PATH=/usr/lib/emsdk:/usr/lib/emsdk/upstream/emscripten:/home/alex/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/emscripten:/var/lib/flatpak/exports/bin:/opt/flutter/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl://home/alex/work/ecg/android-studio/bin
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
HG=/usr/bin/hg
MAIL=/var/spool/mail/alex
EMSDK=/usr/lib/emsdk
LC_NUMERIC=en_CA.UTF-8
_ble_util_fd_stdout=31
_=/usr/bin/env
[alex@alex-pc ~]$

[mikunimaru]

In order for fcitx5 to work, the following values ​​are required for the environment variables. XMODIFIERS=@im=fcitx GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitx
There is a possibility that something other than fcitx5 is running with the current environment variables.

[hiroyuki-komatsu]

It's possibly a limitation of Fcitx.

Would you confirm whether the same issue happens with Ibus?

[yukawa]

Let's also convert this to a discussion as this looks more like a Q&A topic on how to dig into a mysterious behavior.

[mikunimaru]

There is no problem with Mozc's behavior. This is not a bug in Mozc, but an issue on your Manjaro side running an engine other than Mozc.
Since the problem did not occur with a clean install of Manjaro, some setting on your part is the cause. If possible, please check if you get the same behavior even if you clean install Manjaro in a virtual environment.

[AlexFolland]

I didn't install extra/manjaro-asian-input-support-fcitx and that was never part of the discussion before. That's not even for fcitx5. Is that what you are running?

[hiroyuki-komatsu]

10 Enter "kai" in the text box, then press the down arrow key 3 times.

You might want to use space instead of down arrow key.

[AlexFolland]

You might want to use space instead of down arrow key.

Oh, what is this mode?! When I typed "kai" and pressed space, then down arrow key, it gave me 164 candidates instead of 100, and that list included 凱! This changes everything. That explains the difference @mikunimaru has been showing me. Thank you for pointing this out!

That being said, why is there a mode with a more limited list of candidates? Is that determined by Mozc or Fcitx5? I can't find the configuration that explains what the difference is between just pressing the down arrow key to get a list of candidates and first pressing space then the down arrow key.

[AlexFolland]

I was also able to see the version number when typing ba-jonn and then pressing space twice. Pressing the down arrow key does not show it. Is this a bug? It's extremely unexpected behavior to me, at least as a new user. I don't know why there would be a list of candidates that is different from the "good" list.

[hiroyuki-komatsu]

There are two modes called "conversion" and "prediction".

• "conversion" is a mode to get candidate words by exact match from the typed query (e.g. あ → 亜). space is used for this mode.
• "prediction" is a mode to get candidate words by prefix match from the typed query (e.g. あ → 明日). This is triggered while you are typing until you press space.

down selects the next candidate word in your current mode.
Thanks,

[AlexFolland]

Ohhh, that explains a lot! The one thing that is still confusing is that the prediction list doesn't contain the conversion candidates. I don't see why it wouldn't predict a correct conversion using a conversion candidate if the sounds already match. A unified prediction and conversion list would really simplify this. If everyone's used to separate lists though, then I'll just get used to it. I'm glad this community is here with information like this.

[AlexFolland]

What's the output of fcitx5-diagnose there? Here's my output.

terminal output

[alex@alex-pc ~]$ fcitx5-diagnose
# System Info:
1.  `uname -a`:

        Linux alex-pc 6.6.8-2-MANJARO #1 SMP PREEMPT_DYNAMIC Thu Dec 21 16:21:45 UTC 2023 x86_64 GNU/Linux

2.  `lsb_release -a`:

        LSB Version:	n/a
        Distributor ID:	ManjaroLinux
        Description:	Manjaro Linux
        Release:	23.1.1
        Codename:	Vulcan

3.  `lsb_release -d`:

        Description:	Manjaro Linux

4.  `/etc/lsb-release`:

        DISTRIB_ID="ManjaroLinux"
        DISTRIB_RELEASE="23.1.1"
        DISTRIB_CODENAME="Vulcan"
        DISTRIB_DESCRIPTION="Manjaro Linux"

5.  `/etc/os-release`:

        NAME="Manjaro Linux"
        PRETTY_NAME="Manjaro Linux"
        ID=manjaro
        ID_LIKE=arch
        BUILD_ID=rolling
        ANSI_COLOR="32;1;24;144;200"
        HOME_URL="https://manjaro.org/"
        DOCUMENTATION_URL="https://wiki.manjaro.org/"
        SUPPORT_URL="https://forum.manjaro.org/"
        BUG_REPORT_URL="https://docs.manjaro.org/reporting-bugs/"
        PRIVACY_POLICY_URL="https://manjaro.org/privacy-policy/"
        LOGO=manjarolinux

6.  Desktop Environment:

    Desktop environment is `xfce`.

7.  XDG SESSION TYPE:

        XDG_SESSION_TYPE='x11'

8.  Bash Version:

        BASH_VERSION='5.2.21(1)-release'

# Environment:
1.  DISPLAY:

        DISPLAY=':0.0'


        WAYLAND_DISPLAY=''

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+us(dvorak)+inet(evdev)+terminate(ctrl_alt_bksp)"	};
            	xkb_geometry  { include "pc(pc105)"	};
            };

    2.  `xprop`:

            _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "dvorak", "terminate:ctrl_alt_bksp"

3.  Locale:

    1.  All locales:

            C
            C.utf8
            en_CA.utf8
            en_GB.utf8
            en_US.utf8
            POSIX

    2.  Current locale:

            LANG=en_US.UTF-8
            LC_CTYPE="en_US.UTF-8"
            LC_NUMERIC=en_CA.UTF-8
            LC_TIME=en_GB.UTF-8
            LC_COLLATE="en_US.UTF-8"
            LC_MONETARY=en_CA.UTF-8
            LC_MESSAGES="en_US.UTF-8"
            LC_PAPER=en_CA.UTF-8
            LC_NAME=en_CA.UTF-8
            LC_ADDRESS=en_CA.UTF-8
            LC_TELEPHONE=en_CA.UTF-8
            LC_MEASUREMENT=en_CA.UTF-8
            LC_IDENTIFICATION=en_CA.UTF-8
            LC_ALL=

4.  Directories:

    1.  Home:

            /home/alex

    2.  `${XDG_CONFIG_HOME}`:

        Environment variable `XDG_CONFIG_HOME` is not set.

        Current value of `XDG_CONFIG_HOME` is `~/.config` (`/home/alex/.config`).

    3.  Fcitx5 Settings Directory:

        Current fcitx5 settings directory is `~/.config/fcitx5` (`/home/alex/.config/fcitx5`).

5.  Current user:

    The script is run as alex (1000).

# Fcitx State:
1.  executable:

    Found fcitx5 at `/usr/bin/fcitx5`.

2.  version:

    Fcitx version: `5.1.6`

3.  process:

    Found 2 fcitx5 processes:

           2973 fcitx5
           8464 fcitx5-config-q

4.  `fcitx5-remote`:

    `fcitx5-remote` works properly.

5.  DBus interface:

    Using `dbus-send` to check dbus.

    Owner of DBus name `org.fcitx.Fcitx5` is `:1.64`.

    PID of DBus name `org.fcitx.Fcitx5` owner is `2973`.

    Debug information from dbus:

           Group [x11::0.0] has 40 InputContext(s)
          IC [445d05e8cae8435099ba04ee0cda2d9e] program:xfce4-terminal frontend:dbus cap:6000000032 focus:1
          IC [cf82d194ccbb4d4d8717faf81aceb6ee] program:fcitx5-config-qt frontend:dbus cap:16000800072 focus:0
          IC [fcb1a42198cd43b09793f992591a9605] program:fcitx5-config-qt frontend:dbus cap:6000000032 focus:0
          IC [09d9192864b3489dbb039c32a17dced2] program:fcitx5-config-qt frontend:dbus cap:6000000032 focus:0
          IC [f3f218535eca45d5b60f7446f03782cf] program:firefoxdeveloperedition frontend:dbus cap:6000000032 focus:0
          IC [43c14e9502014ab4a9b361a5b0300629] program:firefoxdeveloperedition frontend:dbus cap:6000000032 focus:0
          IC [bbf984ac02054b478e4530f2ebedc15d] program:firefoxdeveloperedition frontend:dbus cap:6000000032 focus:0
          IC [eb7e4fd002da4830b95cdd3aba9c49f8] program:firefoxdeveloperedition frontend:dbus cap:6000000032 focus:0
          IC [f6109f28762e4dc4a7ddbbc3ea392ceb] program:qbittorrent frontend:dbus cap:6000000032 focus:0
          IC [d93a69b8434f4973ad333aa4d530ee14] program:pasystray frontend:dbus cap:6000000032 focus:0
          IC [9c0b22802d8f4f2ba21902f9d48ec8da] program:wrapper-2.0 frontend:dbus cap:6000000072 focus:0
          IC [a527daf9a0b1419c81920f2a13a76ef6] program:firefoxdeveloperedition frontend:dbus cap:6000000032 focus:0
          IC [14251504490d43a5b97a883778147343] program:firefoxdeveloperedition frontend:dbus cap:6000000032 focus:0
          IC [d74e65eee1ad4d7fa8c2a9901f0c7901] program:qmmp frontend:dbus cap:6000000032 focus:0
          IC [157f4d5d8cbe4f918f3f103df12a8fa1] program:copyq frontend:dbus cap:6000000032 focus:0
          IC [f62d4576f80b4fd18b207cd04856dd83] program:slack frontend:dbus cap:6000000032 focus:0
          IC [8a530a2f44c14df88c12829710463eb8] program:pavucontrol frontend:dbus cap:6000000032 focus:0
          IC [9a54dd88f52c4f1ba3c0fad70f549b71] program:kwalletd5 frontend:dbus cap:6000000032 focus:0
          IC [2c580c52b8f0474284c0549120ac9939] program:Discord frontend:dbus cap:6000000032 focus:0
          IC [58883c2239294ea8ba30c1236cf34431] program:copyq frontend:dbus cap:6000000032 focus:0
          IC [0dc962b6704f453e807dc1267fc5dd62] program:firefoxdeveloperedition frontend:dbus cap:6000000032 focus:0
          IC [33d3e50a85cc4164ae744d5de43d00c8] program:kwalletd5 frontend:dbus cap:6000000032 focus:0
          IC [cefbbf7dbaca47bba0cfa616dfdc5a40] program:flameshot frontend:dbus cap:6000000032 focus:0
          IC [b8732350d56840079ea58d8b8b54927c] program:qbittorrent frontend:dbus cap:6000000032 focus:0
          IC [36e9618de6244a8fb851b01ec835c5eb] program:flameshot frontend:dbus cap:6000000032 focus:0
          IC [a9cfa376d1fc49fbb1635f127c015a14] program:pavucontrol frontend:dbus cap:6000000032 focus:0
          IC [66d63bfaf9384b4085a8340d85589ffa] program:pavucontrol frontend:dbus cap:6000000032 focus:0
          IC [d11d92e730e8401a830d9d8b22a71e09] program:pavucontrol frontend:dbus cap:6000000032 focus:0
          IC [07e062e738bc4b1288f309aaaaeaf92d] program:firefoxdeveloperedition frontend:dbus cap:6000000032 focus:0
          IC [20010406d4764e86b40ddca65a8cc30c] program:pavucontrol frontend:dbus cap:6000000032 focus:0
          IC [68bde4400bb9443e8f21f48668e79962] program:firefoxdeveloperedition frontend:dbus cap:6000000072 focus:0
          IC [f71aebbdfff64880989d0ce831183124] program:pavucontrol frontend:dbus cap:6000000032 focus:0
          IC [426873fa3cc549b2ad21184635182e0c] program:element-desktop-nightly frontend:dbus cap:6000000032 focus:0
          IC [0f685b5119bf4fa4b6bbea81842a6ee0] program:qmmp frontend:dbus cap:6000000032 focus:0
          IC [0488724ed6d440148430e6aa3cd601fb] program:qmmp frontend:dbus cap:16000800072 focus:0
          IC [8e5d628c1ef1498bb941c7a92208544c] program:steamwebhelper frontend:dbus cap:12 focus:0
          IC [ab77ecb2667549df9e8ee457342a7b6b] program:whatsapp-nativefier frontend:dbus cap:6000000032 focus:0
          IC [71ace94d5c0c4ef5ad44a0b6ac98661d] program:firefoxdeveloperedition frontend:dbus cap:6000000032 focus:0
          IC [12316d1616e345e8bc8df027b6b9c0d2] program:qbittorrent frontend:dbus cap:6000800072 focus:0
          IC [5a71e9b03d8d444689d68148ba945ff9] program:steam frontend:dbus cap:12 focus:0
        Input Context without group

# Fcitx Configure UI:
1.  Config Tool Wrapper:

    Found fcitx5-configtool at `/usr/bin/fcitx5-configtool`.

2.  Config GUI for qt:

    Found `fcitx5-config-qt` at `/usr/bin/fcitx5-config-qt`.

3.  Config GUI for kde:

    Found fcitx5 kcm module.

        kcm_fcitx5                     - Configure Input Method

# Frontends setup:
The environment variable checked by this script only shows the environment under current shell. It is still possible that you did not set the environment to the whole graphic desktop session. You may inspect the actual environment variable of a certain process by using `xargs -0 -L1 /proc/$PID/environ` for a certain process that you find not working.

## Xim:
1.  `${XMODIFIERS}`:

    Environment variable XMODIFIERS is set to "@im=fcitx" correctly.
    Xim Server Name from Environment variable is fcitx.

2.  XIM_SERVERS on root window:

    Xim server name is the same with that set in the environment variable.

3.  XIM for Emacs:

    **Your LC_CTYPE is set to en_US.UTF-8 instead of one of zh, ja, ko. You may not be able to use input method in emacs because of an really old emacs bug that upstream refuse to fix for years.**

## Qt:
1.  qt4 - `${QT4_IM_MODULE}`:

    Environment variable QT_IM_MODULE is set to "fcitx" correctly.

    **`fcitx5-qt4-immodule-probing` not found.**

2.  qt5 - `${QT_IM_MODULE}`:

    Environment variable QT_IM_MODULE is set to "fcitx" correctly.

    Using fcitx5-qt5-immodule-probing to check the actual im module to be used under current environment:

        QT_QPA_PLATFORM=xcb
        QT_IM_MODULE=fcitx
        IM_MODULE_CLASSNAME=fcitx::QFcitxPlatformInputContext

3.  qt6 - `${QT_IM_MODULE}`:

    Environment variable QT_IM_MODULE is set to "fcitx" correctly.

    Using fcitx5-qt6-immodule-probing to check the actual im module to be used under current environment:

        QT_QPA_PLATFORM=xcb
        QT_IM_MODULE=fcitx
        IM_MODULE_CLASSNAME=fcitx::QFcitxPlatformInputContext

4.  Qt IM module files:

    Found unknown fcitx qt module: `/usr/lib/qt/plugins/kcms/kcm_fcitx5.so`.
    Found fcitx5 im module for qt: `/usr/lib/qt/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so`.
    Found fcitx5 im module for qt6: `/usr/lib/qt6/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so`.
    Found fcitx5 qt5 module: `/usr/lib/fcitx5/qt5/libfcitx-quickphrase-editor5.so`.

    Following error may not be accurate because guessing Qt version from path depends on how your distribution packages Qt. It is not a critical error if you do not use any Qt application with certain version of Qt or you are using text-input support by Qt under Wayland.
    **Cannot find fcitx5 input method module for Qt4.**

## Gtk:
1.  gtk - `${GTK_IM_MODULE}`:

    Environment variable GTK_IM_MODULE is set to "fcitx" correctly.

    Using fcitx5-gtk2-immodule-probing to check the actual im module to be used under current environment:

        GTK_IM_MODULE=fcitx

    Using fcitx5-gtk3-immodule-probing to check the actual im module to be used under current environment:

        GTK_IM_MODULE=fcitx

    Using fcitx5-gtk4-immodule-probing to check the actual im module to be used under current environment:

        GTK_IM_MODULE=fcitx

2.  `gtk-query-immodules`:

    1.  gtk 2:

        Found `gtk-query-immodules` for gtk `2.24.33` at `/usr/bin/gtk-query-immodules-2.0`.
        Version Line:

            # Created by /usr/bin/gtk-query-immodules-2.0 from gtk+-2.24.33

        Found fcitx5 im modules for gtk `2.24.33`.

            "/usr/lib/gtk-2.0/2.10.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:*" 

        Found `gtk-query-immodules` for gtk `2.24.33` at `/usr/bin/gtk-query-immodules-2.0-32`.
        Version Line:

            # Created by /usr/bin/gtk-query-immodules-2.0-32 from gtk+-2.24.33

        **Failed to find fcitx5 in the output of `/usr/bin/gtk-query-immodules-2.0-32`**

    2.  gtk 3:

        Found `gtk-query-immodules` for gtk `3.24.39` at `/usr/bin/gtk-query-immodules-3.0`.
        Version Line:

            # Created by /usr/bin/gtk-query-immodules-3.0 from gtk+-3.24.39

        Found fcitx5 im modules for gtk `3.24.39`.

            "/usr/lib/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:*" 

        Found `gtk-query-immodules` for gtk `3.24.39` at `/usr/bin/gtk-query-immodules-3.0-32`.
        Version Line:

            # Created by /usr/bin/gtk-query-immodules-3.0-32 from gtk+-3.24.39

        **Failed to find fcitx5 in the output of `/usr/bin/gtk-query-immodules-3.0-32`**

3.  Gtk IM module cache:

    1.  gtk 2:

        Found immodules cache for gtk `2.24.33` at `/usr/lib/gtk-2.0/2.10.0/immodules.cache`.
        Version Line:

            # Created by /usr/bin/gtk-query-immodules-2.0 from gtk+-2.24.33

        Found fcitx5 im modules for gtk `2.24.33`.

            "/usr/lib/gtk-2.0/2.10.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:*" 

        Found immodules cache for gtk `2.24.33` at `/usr/lib32/gtk-2.0/2.10.0/immodules.cache`.
        Version Line:

            # Created by usr/bin/gtk-query-immodules-2.0-32 from gtk+-2.24.33

        **Failed to find fcitx5 in immodule cache at `/usr/lib32/gtk-2.0/2.10.0/immodules.cache`**

    2.  gtk 3:

        Found immodules cache for gtk `3.24.39` at `/usr/lib/gtk-3.0/3.0.0/immodules.cache`.
        Version Line:

            # Created by /usr/bin/gtk-query-immodules-3.0 from gtk+-3.24.39

        Found fcitx5 im modules for gtk `3.24.39`.

            "/usr/lib/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:*" 

        Found immodules cache for gtk `3.24.39` at `/usr/lib32/gtk-3.0/3.0.0/immodules.cache`.
        Version Line:

            # Created by /usr/bin/gtk-query-immodules-3.0-32 from gtk+-3.24.39

        **Failed to find fcitx5 in immodule cache at `/usr/lib32/gtk-3.0/3.0.0/immodules.cache`**

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.

    3.  gtk 4:

        All found Gtk 4 immodule files exist.

# Configuration:
## Fcitx Addons:
1.  Addon Config Dir:

    Found fcitx5 addon config directory: `/usr/share/fcitx5/addon`.

2.  Addon List:

    1.  Found 21 enabled addons:

            Classic User Interface 5.1.6
            Clipboard 5.1.6
            DBus 5.1.6
            DBus Frontend 5.1.6
            Emoji 5.1.6
            Fcitx4 Frontend 5.1.6
            IBus Frontend 5.1.6
            Input method selector 5.1.6
            Keyboard 5.1.6
            KDE Input Method Panel 5.1.6
            Mozc 
            Status Notifier 5.1.6
            Notification 5.1.6
            Quick Phrase 5.1.6
            Spell 5.1.6
            Unicode 5.1.6
            DBus Virtual Keyboard 5.1.6
            Wayland 5.1.6
            Wayland Input method frontend 5.1.6
            XCB 5.1.6
            X Input Method Frontend 5.1.6

    2.  Found 0 disabled addons:

3.  Addon Libraries:

    All libraries for all addons are found.

4.  User Interface:

    Found 3 enabled user interface addons:

        Classic User Interface
        KDE Input Method Panel
        DBus Virtual Keyboard

## Input Methods:
1.  `/home/alex/.config/fcitx5/profile`:

        [Groups/0]
        # Group Name
        Name="Group 1"
        # Layout
        Default Layout=us-dvorak
        # Default Input Method
        DefaultIM=mozc

        [Groups/0/Items/0]
        # Name
        Name=keyboard-us-dvorak
        # Layout
        Layout=

        [Groups/0/Items/1]
        # Name
        Name=mozc
        # Layout
        Layout=us-dvorak

        [Groups/1]
        # Group Name
        Name="Group 2"
        # Layout
        Default Layout=us
        # Default Input Method
        DefaultIM=mozc

        [Groups/1/Items/0]
        # Name
        Name=keyboard-us
        # Layout
        Layout=

        [Groups/1/Items/1]
        # Name
        Name=mozc
        # Layout
        Layout=us

        [GroupOrder]
        0="Group 1"
        1="Group 2"

# Log:
1.  `date`:

        Sat 23 Dec 05:46:08 PST 2023

2.  `/home/alex/.config/fcitx5/crash.log`:

    `/home/alex/.config/fcitx5/crash.log` not found.

**Warning: the output of fcitx5-diagnose contains sensitive information, including the distribution name, kernel version, name of currently running programs, etc.**

**Though such information can be helpful to developers for diagnostic purpose, please double check and remove as necessary before posting it online publicly.**
[alex@alex-pc ~]$

[mikunimaru]

In that step, fcitx5 should not start because the environment variables are not set.
In other words, it seems like a natural result of following steps that don't work.

If Mozc has started, you should be able to check it from the icon etc.

[AlexFolland]

It does start, and I can check it from the icon. "Mozc" is in the tray icon. What step are you talking about, by the way? Which environment variables do you think are not set correctly? I see these lines in the output I included: Environment variable XMODIFIERS is set to "@im=fcitx" correctly., Environment variable QT_IM_MODULE is set to "fcitx" correctly., Environment variable GTK_IM_MODULE is set to "fcitx" correctly..