-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
在marktext中打字时,能输入,但是不显示候选框 #1209
Comments
别的程序什么情况,能正常显示吗? |
我刚试了下,typora也是一样的情况,能打字但不显示输入框,然后google浏览器也这样。是不是我哪里没设置好,导致对chrome内核的软件支持有问题? |
一般这个情况是fcitx界面没有加载正确,经常有 fcitx5-modules-x11 没有安装的人有这种情况,但目前我看不出来你少了什么包,不太确定发生了什么 你能不能在终端执行一下 fcitx5 --verbose=classicui=5 -rd (它会重新启动一个 fcitx)看看有什么输出 |
librer@Yilong15Pro-Series-GM5HG0A-6eda5651: |
没发现什么明显的问题,这样启动的fcitx你再去 marktext 里面打字的话会显示什么新的日志? |
Environment:
Fcitx State:
Fcitx Configure UI:
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 Xim:
Qt:
Gtk:
Configuration:Fcitx Addons:
Input Methods:
Log:
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. 好像跟之前的没什么不一样 |
不是这个意思,我的意思是,用上面那条命令启动fcitx,然后在marktext里面打字,会发生什么
zero-hugo ***@***.***> 于 2024年12月16日周一 04:04写道:
… 没发现什么明显的问题,这样启动的fcitx你再去 marktext 里面打字的话会显示什么新的日志?
1.
uname -a:
Linux Yilong15Pro-Series-GM5HG0A-6eda5651 6.8.0-49-generic #49-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 4 02:06:24 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
2.
lsb_release -a:
Distributor ID: Elementary
Description: elementary OS 8
Release: 8
Codename: circe
3.
lsb_release -d:
Description: elementary OS 8
4.
/etc/lsb-release:
DISTRIB_ID=elementary
DISTRIB_RELEASE=8
DISTRIB_CODENAME=circe
DISTRIB_DESCRIPTION="elementary OS 8"
5.
/etc/os-release:
PRETTY_NAME="elementary OS 8"
NAME="elementary OS"
CPE_NAME="cpe:/o:elementary:elementary_os:8"
VERSION_ID="8"
VERSION="8"
VERSION_CODENAME=circe
ID=elementary
ID_LIKE="ubuntu debian"
HOME_URL="https://elementary.io/"
DOCUMENTATION_URL="https://elementary.io/docs/learning-the-basics"
SUPPORT_URL="https://elementary.io/support"
BUG_REPORT_URL="https://docs.elementary.io/contributor-guide/feedback/reporting-issues"
PRIVACY_POLICY_URL="https://elementary.io/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=distributor-logo
UBUNTU_CODENAME=noble
UBUNTU_PRETTY_NAME="Ubuntu 24.04.1 LTS"
UBUNTU_NAME="Ubuntu"
UBUNTU_VERSION_ID="24.04"
UBUNTU_VERSION="24.04.1 LTS (Noble Numbat)"
UBUNTU_VERSION_CODENAME=noble
6.
Desktop Environment:
Desktop environment is gnome3.
7.
XDG SESSION TYPE:
XDG_SESSION_TYPE='wayland'
8.
Bash Version:
BASH_VERSION='5.2.21(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" };
xkb_symbols { include "pc+us+inet(evdev)" };
xkb_geometry { include "pc(pc105)" };
};
2.
xprop:
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", ""
3.
Locale:
1.
All locales:
C
C.utf8
POSIX
bg_BG.utf8
ca_AD.utf8
ca_ES.utf8
***@***.***
ca_FR.utf8
ca_IT.utf8
cs_CZ.utf8
da_DK.utf8
de_AT.utf8
de_BE.utf8
de_CH.utf8
de_DE.utf8
de_IT.utf8
de_LI.utf8
de_LU.utf8
en_AG
en_AG.utf8
en_AU.utf8
en_BW.utf8
en_CA.utf8
en_DK.utf8
en_GB.utf8
en_HK.utf8
en_IE.utf8
en_IL
en_IL.utf8
en_IN
en_IN.utf8
en_NG
en_NG.utf8
en_NZ.utf8
en_PH.utf8
en_SG.utf8
en_US.utf8
en_ZA.utf8
en_ZM
en_ZM.utf8
en_ZW.utf8
es_AR.utf8
es_BO.utf8
es_CL.utf8
es_CO.utf8
es_CR.utf8
es_CU
es_CU.utf8
es_DO.utf8
es_EC.utf8
es_ES.utf8
es_GT.utf8
es_HN.utf8
es_MX.utf8
es_NI.utf8
es_PA.utf8
es_PE.utf8
es_PR.utf8
es_PY.utf8
es_SV.utf8
es_US.utf8
es_UY.utf8
es_VE.utf8
fr_BE.utf8
fr_CA.utf8
fr_CH.utf8
fr_FR.utf8
fr_LU.utf8
hu_HU.utf8
id_ID.utf8
it_CH.utf8
it_IT.utf8
ja_JP.utf8
ko_KR.utf8
nb_NO.utf8
nl_AW
nl_AW.utf8
nl_BE.utf8
nl_NL.utf8
pl_PL.utf8
pt_BR.utf8
pt_PT.utf8
ru_RU.utf8
ru_UA.utf8
sv_FI.utf8
sv_SE.utf8
th_TH.utf8
tr_CY.utf8
tr_TR.utf8
uk_UA.utf8
vi_VN
vi_VN.utf8
zh_CN.utf8
zh_HK.utf8
zh_SG.utf8
zh_TW.utf8
2.
Current locale:
LANG=zh_CN.UTF-8
LANGUAGE=zh_CN
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/librer
2.
${XDG_CONFIG_HOME}:
Environment variable XDG_CONFIG_HOME is not set.
Current value of XDG_CONFIG_HOME is ~/.config (/home/librer/.config
).
3.
Fcitx5 Settings Directory:
Current fcitx5 settings directory is ~/.config/fcitx5 (
/home/librer/.config/fcitx5).
5.
Current user:
The script is run as librer (1000).
Fcitx State:
1.
executable:
Found fcitx5 at /usr/bin/fcitx5.
2.
version:
Fcitx version: 5.1.7
3.
process:
Found 1 fcitx5 process:
358789 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.7714.
PID of DBus name org.fcitx.Fcitx5 owner is 358789.
Debug information from dbus:
Group [x11::0] has 4 InputContext(s)
IC [c88af5425d1a4cd4b5b0eb67090efddb] program:marktext frontend:dbus cap:6000000032 focus:0
IC [29e44abcc00f417c8dad628ec1adf612] program:Nutstore frontend:dbus cap:6000000032 focus:0
IC [cf62cb9c3e3d4527a0a92f1c07c2af97] program:Nutstore frontend:dbus cap:6000000032 focus:0
IC [02374a830bcf457299428e2654aee86f] program:Typora frontend:dbus cap:6000000032 focus:0
Group [wayland:] has 17 InputContext(s)
IC [cf7765c6667f404dbcc0e03c9eefbada] program:clash-verge frontend:dbus cap:6001000032 focus:0
IC [effe5d5286704b239396cc6859a023b4] program:io.elementary.settings frontend:dbus cap:c001000032 focus:0
IC [389d93436ff343428e9542a370a4371f] program:clash-verge frontend:dbus cap:6001000032 focus:0
IC [cabf73223d934268bafb461aec1ee99c] program:io.elementary.settings frontend:dbus cap:c001000032 focus:0
IC [6ecea2d70b324631880709fa49ce3ad2] program:missioncenter frontend:dbus cap:4001000032 focus:0
IC [676f975ef4bb408c873895b347f3a73a] program:clash-verge frontend:dbus cap:e001000060 focus:0
IC [6f6eb1bf500948ff81f4f72f45e8737f] program:missioncenter frontend:dbus cap:4001000032 focus:0
IC [f2a3c1ca6f584ea28ce0e2f42c6b3891] program:clash-verge frontend:dbus cap:6001000032 focus:0
IC [edcb3edbc0164568a350c114c1c5f337] program:io.elementary.terminal frontend:dbus cap:e001000032 focus:1
IC [bf856c72433c4bf5889e5753b3e465da] program:AppFlowy frontend:dbus cap:e001000072 focus:0
IC [1944870e0400423a921ebcdc236ee9a1] program:firefox frontend:dbus cap:e001000072 focus:0
IC [2ef5e9ed5ca746e3a62a6ea2b0e80b4f] program:io.elementary.wingpanel frontend:dbus cap:e001000072 focus:0
IC [c9164d0058f04151bd988ef367af699e] program:firefox frontend:dbus cap:e001000032 focus:0
IC [0d9d6af3f57440d1a9942e8fae8ccd32] program:io.elementary.files.xdg-desktop-portal frontend:dbus cap:6001000032 focus:0
IC [c58a5a870e1b40eb82b99ba5cde33340] program:clash-verge frontend:dbus cap:6001000032 focus:0
IC [8e2a7921cbd44ef18a47b2ad72f6f3ad] program:io.elementary.terminal frontend:dbus cap:6001000032 focus:0
IC [ea90ed7752344670a613477f8e8da681] program:io.elementary.files.xdg-desktop-portal frontend:dbus cap:6001000032 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 ***@***.*** <https://github.com/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 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 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=wayland
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=wayland
QT_IM_MODULE=fcitx
IM_MODULE_CLASSNAME=fcitx::QFcitxPlatformInputContext
4.
Qt IM module files:
Found fcitx5 qt6 module:
/lib/x86_64-linux-gnu/fcitx5/qt6/libfcitx-quickphrase-editor5.so.
Found unknown fcitx qt module:
/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fcitx5.so
.
Found fcitx5 im module for qt5:
/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so
.
Found fcitx5 im module for qt6:
/lib/x86_64-linux-gnu/qt6/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.*
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:
*Cannot find gtk-query-immodules for gtk 2*
*Cannot find fcitx5 im module for gtk 2.*
2.
gtk 3:
*Cannot find gtk-query-immodules for gtk 3*
*Cannot find fcitx5 im module for gtk 3.*
3.
Gtk IM module cache:
1.
gtk 2:
Found immodules cache for gtk 2.24.33 at
/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-0t64/gtk-query-immodules-2.0 from gtk+-2.24.33
Found fcitx5 im modules for gtk 2.24.33.
"/usr/lib/x86_64-linux-gnu/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:*"
2.
gtk 3:
Found immodules cache for gtk 3.24.41 at
/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-0t64/gtk-query-immodules-3.0 from gtk+-3.24.41
Found fcitx5 im modules for gtk 3.24.41.
"/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.
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 31 enabled addons:
Simplified and Traditional Chinese Translation 5.1.3
Classic User Interface 5.1.7
Clipboard 5.1.7
Cloud Pinyin 5.1.3
DBus 5.1.7
DBus Frontend 5.1.7
Emoji 5.1.7
Fcitx4 Frontend 5.1.7
Full width character 5.1.3
IBus Frontend 5.1.7
Lua IME API 5.0.12
Input method selector 5.1.7
Keyboard 5.1.7
KDE Input Method Panel 5.1.7
Lua Addon Loader 5.0.12
Mozc
Status Notifier 5.1.7
Notification 5.1.7
Pinyin 5.1.3
Extra Pinyin functionality 5.1.3
Punctuation 5.1.3
Quick Phrase 5.1.7
Rime 5.1.4
Spell 5.1.7
Table 5.1.3
Unicode 5.1.7
DBus Virtual Keyboard 5.1.7
Wayland 5.1.7
Wayland Input method frontend 5.1.7
XCB 5.1.7
X Input Method Frontend 5.1.7
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/librer/.config/fcitx5/profile:
[Groups/0]
# Group Name
Name=默认
# Layout
Default Layout=us
# Default Input Method
DefaultIM=rime
[Groups/0/Items/0]
# Name
Name=keyboard-us
# Layout
Layout=
[Groups/0/Items/1]
# Name
Name=rime
# Layout
Layout=us
[GroupOrder]
0=默认
Log:
1.
date:
Mon Dec 16 20:01:14 CST 2024
2.
/home/librer/.config/fcitx5/crash.log:
/home/librer/.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.*
好像跟之前的没什么不一样
—
Reply to this email directly, view it on GitHub
<#1209 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB7MZARCC3UZRDVEK5ETID2F26WJAVCNFSM6AAAAABTS7NQNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBVGQ2DSMJYGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
另外请问你的 marktext 是怎么安装的,启动的时候是否加了什么参数 |
等一下,我在虚拟机里面重现了你的问题了 但我觉得是 elementary 的 bug |
简单来说,我观察到的现象是,fcitx 的输入框能在第一次使用的时候被显示,然后我能看见 fcitx 正常绘制窗口,但是看不见 测试 elementary 的 X11 会话可以正常显示 fcitx 的窗口 |
好吧,这系统有点让人无语。谢谢!麻烦你了。 |
@zero-hugo 我找到了办法workaround,但是我在master修复的话你要是不打算编译自己也用不上吧 |
重新编译安装fcitx5吗?这……我研究研究怎么弄。你已经在master更新修复代码了吗? |
还并没有,因为那个属性还是有用的 它也是为了解决 fcitx 4 曾经遇到的问题 fcitx/fcitx#191 我在研究怎么写一个 minimal case 给 elementary 汇报 bug |
哦好的,谢谢你啦! |
里面有一个测试程序,你也可以看看是不是和我的视频里面的现象一样 |
Pantheon has a bug that can't not display popup window under Xwayland twice. While the bug is reported, it's not clear when it may be fixed. Also, input method window is indeed more like a combo box and wmspec mentioned that it's also a common override redirect. So try to use that instead. Workaround #1209
Pantheon has a bug that can't not display popup window under Xwayland twice. While the bug is reported, it's not clear when it may be fixed. Also, input method window is indeed more like a combo box and wmspec mentioned that it's also a common override redirect. So try to use that instead. Workaround #1209
anyway I'll close this, since I already did the workaround on fcitx side. If you want to try the patch, please refer to c0e1c7e . |
Summary
在marktext中打字时,能输入文字,但是不显示候选框。marktext是用eletron开发的,我不知道跟这个有没有关系。我该怎么设置让候选框显示出来?
ps:按照下面的信息里显示的缺少组建,我试了一遍,能找到的包我都按上了,下面信息中还报找不到的包我也找不到……
Steps to Reproduce
安装marktext?
Expected Behavior
无法显示输入框?
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/librer/.config
).Fcitx5 Settings Directory:
Current fcitx5 settings directory is
~/.config/fcitx5
(/home/librer/.config/fcitx5
).Current user:
The script is run as librer (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.96
.PID of DBus name
org.fcitx.Fcitx5
owner is36233
.Debug information from dbus:
Fcitx Configure UI:
Config Tool Wrapper:
Found fcitx5-configtool at
/usr/bin/fcitx5-configtool
.Config GUI for qt:
Found
fcitx5-config-qt
at/usr/bin/fcitx5-config-qt
.Config GUI for kde:
Found fcitx5 kcm module.
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 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.
Using fcitx5-qt6-immodule-probing to check the actual im module to be used under current environment:
Qt IM module files:
Found fcitx5 qt6 module:
/lib/x86_64-linux-gnu/fcitx5/qt6/libfcitx-quickphrase-editor5.so
.Found unknown fcitx qt module:
/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fcitx5.so
.Found fcitx5 im module for qt5:
/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so
.Found fcitx5 im module for qt6:
/lib/x86_64-linux-gnu/qt6/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.
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/x86_64-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/x86_64-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 31 enabled addons:
Found 0 disabled addons:
Addon Libraries:
All libraries for all addons are found.
User Interface:
Found 3 enabled user interface addons:
Input Methods:
/home/librer/.config/fcitx5/profile
:Log:
date
:/home/librer/.config/fcitx5/crash.log
:/home/librer/.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.
The text was updated successfully, but these errors were encountered: