Open amazingfate opened 2 months ago
Does your system start up takes too long?
If you run fcitx5 -r
from terminal after you logged in, does it show the message again?
fcitx5 -r
It will not show the message after running fcitx5 -r
.
From systemctl --user status
I can see fcitx5 is started by gnome-session-manager@gnome.service. This service starts 4 seconds after kernel boots.
7月 07 08:56:25 xiaomi-elish kernel: Booting Linux on physical CPU 0x0000000000 [0x51df805e]
7月 07 08:56:25 xiaomi-elish kernel: Linux version 6.9.7-current-sm8250 (armbian@next) (aarch64-linux-gnu-gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #16 SMP Thu Jun 27 19:52:32 CST 2024
7月 07 08:56:25 xiaomi-elish kernel: KASLR enabled
7月 07 08:56:25 xiaomi-elish kernel: random: crng init done
7月 07 08:56:25 xiaomi-elish kernel: Machine model: Xiaomi Mi Pad 5 Pro (BOE)
7月 07 08:56:25 xiaomi-elish kernel: efi: UEFI not found.
7月 07 08:56:25 xiaomi-elish kernel: [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader!
7月 07 08:56:25 xiaomi-elish kernel: OF: reserved mem: 0x0000000080000000..0x00000000805fffff (6144 KiB) nomap non-reusable memory@80000000
7月 07 08:56:25 xiaomi-elish kernel: OF: reserved mem: 0x0000000080600000..0x000000008085ffff (2432 KiB) nomap non-reusable xbl-aop@80600000
7月 07 08:56:25 xiaomi-elish kernel: OF: reserved mem: 0x0000000080860000..0x000000008087ffff (128 KiB) nomap non-reusable memory@80860000
......
7月 07 08:56:29 xiaomi-elish systemd[1820]: Created slice app-gnome\x2dsession\x2dmanager.slice - Slice /app/gnome-session-manager.
7月 07 08:56:29 xiaomi-elish systemd[1820]: Starting gnome-session-monitor.service - Monitor Session leader for GNOME Session...
7月 07 08:56:29 xiaomi-elish systemd[1820]: Started gnome-session-monitor.service - Monitor Session leader for GNOME Session.
7月 07 08:56:29 xiaomi-elish systemd[1820]: Starting gnome-session-manager@gnome.service - GNOME Session Manager (session: gnome)...
7月 07 08:56:29 xiaomi-elish systemd[1820]: Started gnome-session-manager@gnome.service - GNOME Session Manager (session: gnome).
7月 07 08:56:29 xiaomi-elish systemd[1820]: Reached target gnome-session-manager.target - GNOME Session Manager is ready.
That doesn't mean anything.
Actually, the current timeout is 7s after fcitx is started. Since you're running an arm device, I would guess your system might not finish this within 7s, it can be either due to cpu, or disk.
If you don't want to see that message, just click "don't show" on the message.
I'll try to adjust the time limit in code to see if it helps.
I'm running an am device but this is now a lowend one. It is xiaomi pad5 pro with snapdragon 870 soc and ufs storage, which should be powerful enough as intel n5105. Maybe there are some qcom specific userspace services making the system start slow.
I am experiencing the same issue on Manjaro GNOME (Wayland) (x8664). It seems that instance->currentUI() is a string of 0 characters.
@phoepsilonix fcitx5-diagnose please.
Is there an order in which to load Mozule (Ui, Wayand etc)?
# System Info:
1. `uname -a`:
Linux phoepsilonix-hp 6.10.5-4-MANJARO #1 SMP PREEMPT_DYNAMIC Sun Aug 18 01:01:34 JST 2024 x86_64 GNU/Linux
2. `lsb_release -a`:
LSB Version: n/a
Distributor ID: ManjaroLinux
Description: Manjaro Linux
Release: 24.0.6
Codename: Wynsdey
3. `lsb_release -d`:
Description: Manjaro Linux
4. `/etc/lsb-release`:
DISTRIB_ID="ManjaroLinux"
DISTRIB_RELEASE="24.0.6"
DISTRIB_CODENAME="Wynsdey"
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 `gnome3`.
7. XDG SESSION TYPE:
XDG_SESSION_TYPE='wayland'
8. Bash Version:
BASH_VERSION='5.2.26(1)-release'
# Environment:
1. DISPLAY:
DISPLAY=':0'
WAYLAND_DISPLAY='wayland-0'
2. Keyboard Layout:
1. `setxkbmap`:
WARNING: Running setxkbmap against an Xwayland server
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete+japan" };
xkb_symbols { include "pc+jp(kana86)+inet(evdev)" };
xkb_geometry { include "pc(pc105)" };
};
2. `xprop`:
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "jp", "kana86", ""
3. Locale:
1. All locales:
C
C.utf8
POSIX
aa_DJ
aa_DJ.utf8
aa_ER
aa_ET
af_ZA
af_ZA.utf8
agr_PE
ak_GH
am_ET
an_ES
an_ES.utf8
anp_IN
ar_AE
ar_AE.utf8
ar_BH
ar_BH.utf8
ar_DZ
ar_DZ.utf8
ar_EG
ar_EG.utf8
ar_IN
ar_IQ
ar_IQ.utf8
ar_JO
ar_JO.utf8
ar_KW
ar_KW.utf8
ar_LB
ar_LB.utf8
ar_LY
ar_LY.utf8
ar_MA
ar_MA.utf8
ar_OM
ar_OM.utf8
ar_QA
ar_QA.utf8
ar_SA
ar_SA.utf8
ar_SD
ar_SD.utf8
ar_SS
ar_SY
ar_SY.utf8
ar_TN
ar_TN.utf8
ar_YE
ar_YE.utf8
as_IN
ast_ES
ast_ES.utf8
ayc_PE
az_AZ
az_IR
be_BY
be_BY.utf8
be_BY@latin
bem_ZM
ber_DZ
ber_MA
bg_BG
bg_BG.utf8
bhb_IN.utf8
bho_IN
bho_NP
bi_VU
bn_BD
bn_IN
bo_CN
bo_IN
br_FR
br_FR.utf8
br_FR@euro
brx_IN
bs_BA
bs_BA.utf8
byn_ER
ca_AD
ca_AD.utf8
ca_ES
ca_ES.utf8
ca_ES@euro
ca_ES@valencia
ca_FR
ca_FR.utf8
ca_IT
ca_IT.utf8
ce_RU
chr_US
ckb_IQ
cmn_TW
crh_RU
crh_UA
cs_CZ
cs_CZ.utf8
csb_PL
cv_RU
cy_GB
cy_GB.utf8
da_DK
da_DK.utf8
de_AT
de_AT.utf8
de_AT@euro
de_BE
de_BE.utf8
de_BE@euro
de_CH
de_CH.utf8
de_DE
de_DE.utf8
de_DE@euro
de_IT
de_IT.utf8
de_LI.utf8
de_LU
de_LU.utf8
de_LU@euro
doi_IN
dsb_DE
dv_MV
dz_BT
el_CY
el_CY.utf8
el_GR
el_GR.utf8
el_GR@euro
en_AG
en_AU
en_AU.utf8
en_BW
en_BW.utf8
en_CA
en_CA.utf8
en_DK
en_DK.utf8
en_GB
en_GB.utf8
en_HK
en_HK.utf8
en_IE
en_IE.utf8
en_IE@euro
en_IL
en_IN
en_NG
en_NZ
en_NZ.utf8
en_PH
en_PH.utf8
en_SC.utf8
en_SG
en_SG.utf8
en_US
en_US.utf8
en_ZA
en_ZA.utf8
en_ZM
en_ZW
en_ZW.utf8
eo
es_AR
es_AR.utf8
es_BO
es_BO.utf8
es_CL
es_CL.utf8
es_CO
es_CO.utf8
es_CR
es_CR.utf8
es_CU
es_DO
es_DO.utf8
es_EC
es_EC.utf8
es_ES
es_ES.utf8
es_ES@euro
es_GT
es_GT.utf8
es_HN
es_HN.utf8
es_MX
es_MX.utf8
es_NI
es_NI.utf8
es_PA
es_PA.utf8
es_PE
es_PE.utf8
es_PR
es_PR.utf8
es_PY
es_PY.utf8
es_SV
es_SV.utf8
es_US
es_US.utf8
es_UY
es_UY.utf8
es_VE
es_VE.utf8
et_EE
et_EE.iso885915
et_EE.utf8
eu_ES
eu_ES.utf8
eu_ES@euro
fa_IR
ff_SN
fi_FI
fi_FI.utf8
fi_FI@euro
fil_PH
fo_FO
fo_FO.utf8
fr_BE
fr_BE.utf8
fr_BE@euro
fr_CA
fr_CA.utf8
fr_CH
fr_CH.utf8
fr_FR
fr_FR.utf8
fr_FR@euro
fr_LU
fr_LU.utf8
fr_LU@euro
fur_IT
fy_DE
fy_NL
ga_IE
ga_IE.utf8
ga_IE@euro
gbm_IN
gd_GB
gd_GB.utf8
gez_ER
gez_ER@abegede
gez_ET
gez_ET@abegede
gl_ES
gl_ES.utf8
gl_ES@euro
gu_IN
gv_GB
gv_GB.utf8
ha_NG
hak_TW
he_IL
he_IL.utf8
hi_IN
hif_FJ
hne_IN
hr_HR
hr_HR.utf8
hsb_DE
hsb_DE.utf8
ht_HT
hu_HU
hu_HU.utf8
hy_AM
hy_AM.armscii8
ia_FR
id_ID
id_ID.utf8
ig_NG
ik_CA
is_IS
is_IS.utf8
it_CH
it_CH.utf8
it_IT
it_IT.utf8
it_IT@euro
iu_CA
ja_JP.eucjp
ja_JP.utf8
ka_GE
ka_GE.utf8
kab_DZ
kk_KZ
kk_KZ.utf8
kl_GL
kl_GL.utf8
km_KH
kn_IN
ko_KR.euckr
ko_KR.utf8
kok_IN
ks_IN
ks_IN@devanagari
ku_TR
ku_TR.utf8
kv_RU
kw_GB
kw_GB.utf8
ky_KG
lb_LU
lg_UG
lg_UG.utf8
li_BE
li_NL
lij_IT
ln_CD
lo_LA
lt_LT
lt_LT.utf8
ltg_LV.utf8
lv_LV
lv_LV.utf8
lzh_TW
mag_IN
mai_IN
mai_NP
mdf_RU
mfe_MU
mg_MG
mg_MG.utf8
mhr_RU
mi_NZ
mi_NZ.utf8
miq_NI
mjw_IN
mk_MK
mk_MK.utf8
ml_IN
mn_MN
mni_IN
mnw_MM
mr_IN
ms_MY
ms_MY.utf8
mt_MT
mt_MT.utf8
my_MM
nan_TW
nan_TW@latin
nb_NO
nb_NO.utf8
nds_DE
nds_NL
ne_NP
nhn_MX
niu_NU
niu_NZ
nl_AW
nl_BE
nl_BE.utf8
nl_BE@euro
nl_NL
nl_NL.utf8
nl_NL@euro
nn_NO
nn_NO.utf8
nr_ZA
nso_ZA
oc_FR
oc_FR.utf8
om_ET
om_KE
om_KE.utf8
or_IN
os_RU
pa_IN
pa_PK
pap_AW
pap_CW
pl_PL
pl_PL.utf8
ps_AF
pt_BR
pt_BR.utf8
pt_PT
pt_PT.utf8
pt_PT@euro
quz_PE
raj_IN
rif_MA
ro_RO
ro_RO.utf8
ru_RU
ru_RU.koi8r
ru_RU.utf8
ru_UA
ru_UA.utf8
rw_RW
sa_IN
sah_RU
sat_IN
sc_IT
scn_IT
sd_IN
sd_IN@devanagari
se_NO
sgs_LT
shn_MM
shs_CA
si_LK
sid_ET
sk_SK
sk_SK.utf8
sl_SI
sl_SI.utf8
sm_WS
so_DJ
so_DJ.utf8
so_ET
so_KE
so_KE.utf8
so_SO
so_SO.utf8
sq_AL
sq_AL.utf8
sq_MK
sr_ME
sr_RS
sr_RS@latin
ss_ZA
ssy_ER
st_ZA
st_ZA.utf8
su_ID
sv_FI
sv_FI.utf8
sv_FI@euro
sv_SE
sv_SE.utf8
sw_KE
sw_TZ
syr
szl_PL
ta_IN
ta_LK
tcy_IN.utf8
te_IN
tg_TJ
tg_TJ.utf8
th_TH
th_TH.utf8
the_NP
ti_ER
ti_ET
tig_ER
tk_TM
tl_PH
tl_PH.utf8
tn_ZA
to_TO
tok
tpi_PG
tr_CY
tr_CY.utf8
tr_TR
tr_TR.utf8
ts_ZA
tt_RU
tt_RU@iqtelif
ug_CN
uk_UA
uk_UA.utf8
unm_US
ur_IN
ur_PK
uz_UZ
uz_UZ.utf8
uz_UZ@cyrillic
ve_ZA
vi_VN
wa_BE
wa_BE.utf8
wa_BE@euro
wae_CH
wal_ET
wo_SN
xh_ZA
xh_ZA.utf8
yi_US
yi_US.utf8
yo_NG
yue_HK
yuw_PG
zgh_MA
zh_CN
zh_CN.gb18030
zh_CN.gbk
zh_CN.utf8
zh_HK
zh_HK.utf8
zh_SG
zh_SG.gbk
zh_SG.utf8
zh_TW
zh_TW.euctw
zh_TW.utf8
zu_ZA
zu_ZA.utf8
2. Current locale:
LANG=ja_JP.UTF-8
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=C
4. Directories:
1. Home:
/home/phoepsilonix
2. `${XDG_CONFIG_HOME}`:
Environment variable `XDG_CONFIG_HOME` is not set.
Current value of `XDG_CONFIG_HOME` is `~/.config` (`/home/phoepsilonix/.config`).
3. Fcitx5 Settings Directory:
Current fcitx5 settings directory is `~/.config/fcitx5` (`/home/phoepsilonix/.config/fcitx5`).
5. Current user:
The script is run as phoepsilonix (1000).
# Fcitx State:
1. executable:
Found fcitx5 at `/usr/bin/fcitx5`.
2. version:
Fcitx version: `5.1.10`
3. process:
Found 1 fcitx5 process:
8807 fcitx5
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.124`.
PID of DBus name `org.fcitx.Fcitx5` owner is `8807`.
Debug information from dbus:
Group [wayland:] has 1 InputContext(s)
IC [bb03f0df482849f3b47253aecc951cd8] program: frontend:ibus cap:52 focus:1
Group [x11::0] has 0 InputContext(s)
Input Context without group
# Fcitx Configure UI:
1. Config Tool Wrapper:
Found fcitx5-configtool at `/usr/bin/fcitx5-configtool`.
2. Config GUI for qt:
**Config GUI for qt not found.**
3. Config GUI for kde:
**`kcmshell5` not found.**
**Cannot find a GUI config tool, please install one of `kcm-fcitx5`, or `fcitx5-config-qt`.**
# 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 "@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).**
**If you are using `gnome>=3.6`, you may want to uninstall `ibus` or remove `ibus-daemon` in order to use any input method other than `ibus`. See [Note for GNOME Later than 3.6](http://fcitx-im.org/wiki/Note_for_GNOME_Later_than_3.6) for more detail as well as alternative solutions.**
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.
3. XIM encoding:
**Your LC_CTYPE is set to C whose encoding is not UTF-8. You may have trouble committing strings using XIM.**
## 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).**
**`fcitx5-qt4-immodule-probing` not found.**
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).**
**`fcitx5-qt5-immodule-probing` not found.**
3. qt6 - `${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 qt6 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).**
**`fcitx5-qt6-immodule-probing` not found.**
4. Qt IM module files:
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.**
**Cannot find fcitx5 input method module for Qt5.**
**Cannot find fcitx5 input method module for Qt6.**
## Gtk:
1. gtk - `${GTK_IM_MODULE}`:
**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).**
**It is OK to use gtk built-in Wayland im module if your compositor fully supports text-input protocol used by gtk.**
Using fcitx5-gtk2-immodule-probing to check the actual im module to be used under current environment:
GTK_IM_MODULE=fcitx5
Using fcitx5-gtk3-immodule-probing to check the actual im module to be used under current environment:
GTK_IM_MODULE=wayland
Using fcitx5-gtk4-immodule-probing to check the actual im module to be used under current environment:
GTK_IM_MODULE=wayland
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.43` at `/usr/bin/gtk-query-immodules-3.0`.
Version Line:
# Created by /usr/bin/gtk-query-immodules-3.0 from gtk+-3.24.43
Found fcitx5 im modules for gtk `3.24.43`.
"/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:*"
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.43` 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.43
Found fcitx5 im modules for gtk `3.24.43`.
"/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:*"
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 18 enabled addons:
Clipboard 5.1.10
DBus 5.1.10
DBus Frontend 5.1.10
Emoji 5.1.10
Fcitx4 Frontend 5.1.10
IBus Frontend 5.1.10
Input method selector 5.1.10
Keyboard 5.1.10
KDE Input Method Panel 5.1.10
Status Notifier 5.1.10
Notification 5.1.10
Quick Phrase 5.1.10
Spell 5.1.10
Unicode 5.1.10
Wayland 5.1.10
Wayland Input method frontend 5.1.10
XCB 5.1.10
X Input Method Frontend 5.1.10
2. Found 2 disabled addons:
Classic User Interface 5.1.10
DBus Virtual Keyboard 5.1.10
3. Addon Libraries:
All libraries for all addons are found.
4. User Interface:
Found 1 enabled user interface addons:
KDE Input Method Panel
Kimpanel process:
7597 /usr/bin/gnome-shell
## Input Methods:
1. `/home/phoepsilonix/.config/fcitx5/profile`:
[Groups/0]
# Group Name
Name=デフォルト
# Layout
Default Layout=jp-kana86
# Default Input Method
DefaultIM=keyboard-jp-kana86
[Groups/0/Items/0]
# Name
Name=keyboard-jp-kana86
# Layout
Layout=
[GroupOrder]
0=デフォルト
# Log:
1. `date`:
Sun Aug 18 12:04:36 JST 2024
2. `/home/phoepsilonix/.config/fcitx5/crash.log`:
`/home/phoepsilonix/.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.**
When I re-enabled the virtual keyboard and classic ui add-ons, currentUI seemed to be set to classicui.
Summary
I have installed kimpanel from https://extensions.gnome.org/extension/261/kimpanel/ and I can input Chinese in gnome's overview search. Which component is doing the extension check and how I can debug it?
Steps to Reproduce
Login gnome wayland session in ubuntu 24.04
Expected Behavior
There should be no notification complaining that kimpanel is not installed
Output of fcitx5-diagnose command
System Info:
uname -a
:lsb_release -a
:lsb_release -d
:/etc/lsb-release
:/etc/os-release
:Desktop Environment:
Desktop environment is
gnome3
.XDG SESSION TYPE:
Bash Version:
Environment:
DISPLAY:
Keyboard Layout:
setxkbmap
:xprop
:Locale:
All locales:
Current locale:
Directories:
Home:
${XDG_CONFIG_HOME}
:Environment variable
XDG_CONFIG_HOME
is not set.Current value of
XDG_CONFIG_HOME
is~/.config
(/home/jfliu/.config
).Fcitx5 Settings Directory:
Current fcitx5 settings directory is
~/.config/fcitx5
(/home/jfliu/.config/fcitx5
).Current user:
The script is run as jfliu (1000).
Fcitx State:
executable:
Found fcitx5 at
/usr/bin/fcitx5
.version:
Fcitx version:
5.1.7
process:
Found 1 fcitx5 process:
fcitx5-remote
:fcitx5-remote
works properly.DBus interface:
Using
dbus-send
to check dbus.Owner of DBus name
org.fcitx.Fcitx5
is:1.79
.PID of DBus name
org.fcitx.Fcitx5
owner is3290
.Debug information from dbus:
Fcitx Configure UI:
Config Tool Wrapper:
Found fcitx5-configtool at
/usr/bin/fcitx5-configtool
.Config GUI for qt:
Config GUI for qt not found.
Config GUI for kde:
kcmshell5
not found.Cannot find a GUI config tool, please install one of
kcm-fcitx5
, orfcitx5-config-qt
.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:
${XMODIFIERS}
:Environment variable XMODIFIERS is set to "@im=fcitx" correctly. Xim Server Name from Environment variable is fcitx.
XIM_SERVERS on root window:
Xim server name is the same with that set in the environment variable.
XIM for Emacs:
Your LC_CTYPE is set to C 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.
XIM encoding:
Your LC_CTYPE is set to C whose encoding is not UTF-8. You may have trouble committing strings using XIM.
Qt:
qt4 -
${QT4_IM_MODULE}
:Environment variable QT_IM_MODULE is set to "fcitx" correctly.
fcitx5-qt4-immodule-probing
not found.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:
qt6 -
${QT_IM_MODULE}
:Environment variable QT_IM_MODULE is set to "fcitx" correctly.
fcitx5-qt6-immodule-probing
not found.Qt IM module files:
Found fcitx5 im module for qt5:
/lib/aarch64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.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. Cannot find fcitx5 input method module for Qt6.
Gtk:
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:
Using fcitx5-gtk3-immodule-probing to check the actual im module to be used under current environment:
Using fcitx5-gtk4-immodule-probing to check the actual im module to be used under current environment:
gtk-query-immodules
:gtk 2:
Cannot find
gtk-query-immodules
for gtk 2Cannot find fcitx5 im module for gtk 2.
gtk 3:
Cannot find
gtk-query-immodules
for gtk 3Cannot find fcitx5 im module for gtk 3.
Gtk IM module cache:
gtk 2:
Found immodules cache for gtk
2.24.33
at/lib/aarch64-linux-gnu/gtk-2.0/2.10.0/immodules.cache
. Version Line:Found fcitx5 im modules for gtk
2.24.33
.gtk 3:
Found immodules cache for gtk
3.24.41
at/lib/aarch64-linux-gnu/gtk-3.0/3.0.0/immodules.cache
. Version Line:Found fcitx5 im modules for gtk
3.24.41
.Gtk IM module files:
gtk 2:
All found Gtk 2 immodule files exist.
gtk 3:
All found Gtk 3 immodule files exist.
gtk 4:
All found Gtk 4 immodule files exist.
Configuration:
Fcitx Addons:
Addon Config Dir:
Found fcitx5 addon config directory:
/usr/share/fcitx5/addon
.Addon List:
Found 22 enabled addons:
Found 0 disabled addons:
Addon Libraries:
All libraries for all addons are found.
User Interface:
Found 3 enabled user interface addons:
Kimpanel process:
Input Methods:
/home/jfliu/.config/fcitx5/profile
:Log:
date
:/home/jfliu/.config/fcitx5/crash.log
:/home/jfliu/.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.