You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PID of DBus name org.fcitx.Fcitx5 owner is 126190.
Debug information from dbus:
Group [wayland:] has 5 InputContext(s)
IC [c85e1155d39540d3918811b1fafdfe2a] program:org.kde.konsole frontend:wayland cap:72 focus:1
IC [1b1258e91137481686df45591d4e52fa] program:org.kde.dolphin frontend:wayland cap:90072 focus:0
IC [d670867d4f7740acac77eab7ee4ac32a] program:org.mozilla.firefox frontend:wayland cap:72 focus:0
IC [88bed87c119c45bcb3596751061510a1] program:org.kde.dolphin frontend:wayland cap:8000d0072 focus:0
IC [250a6aa69102451f9b13aaef2b152021] program: frontend:wayland cap:72 focus:0
Group [x11::0] has 2 InputContext(s)
IC [8b0551f334724c9092e03e3d13e149cc] program:wechat frontend:fcitx4 cap:800072 focus:0
IC [80755d8687d448cbbc9e2dc9eaf40773] program:wechat frontend:fcitx4 cap:800072 focus:0
Input Context without group
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:
kcmshell5 not found.
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 "@im=ibus" instead of "@im=fcitx". Please check if you have exported it incorrectly in any of your init files.
Found fcitx5 qt5 module: /lib64/fcitx5/qt5/libfcitx-quickphrase-editor5.so.
Found fcitx5 qt6 module: /lib64/fcitx5/qt6/libfcitx-quickphrase-editor5.so.
Found fcitx5 im module for qt5: /lib64/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so.
Found fcitx5 im module for qt6: /lib64/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.
Found fcitx5 addon config directory: /usr/share/fcitx5/addon.
Addon List:
Found 28 enabled addons:
Simplified and Traditional Chinese Translation 5.1.7
Classic User Interface 5.1.11
Cloud Pinyin 5.1.7
DBus 5.1.11
DBus Frontend 5.1.11
Emoji 5.1.11
Fcitx4 Frontend 5.1.11
Full width character 5.1.7
IBus Frontend 5.1.11
Lua IME API 5.0.13
Input method selector 5.1.11
Keyboard 5.1.11
KDE Input Method Panel 5.1.11
Lua Addon Loader 5.0.13
Status Notifier 5.1.11
Notification 5.1.11
Pinyin 5.1.7
Extra Pinyin functionality 5.1.7
Punctuation 5.1.7
Quick Phrase 5.1.11
Spell 5.1.11
Table 5.1.7
Unicode 5.1.11
DBus Virtual Keyboard 5.1.11
Wayland 5.1.11
Wayland Input method frontend 5.1.11
XCB 5.1.11
X Input Method Frontend 5.1.11
Found 1 disabled addons:
Clipboard 5.1.11
Addon Libraries:
All libraries for all addons are found.
User Interface:
Found 3 enabled user interface addons:
Classic User Interface
KDE Input Method Panel
DBus Virtual Keyboard
Input Methods:
/home/cx/.config/fcitx5/profile:
[Groups/0]
# Group Name
Name=默认
# Layout
Default Layout=us
# Default Input Method
DefaultIM=pinyin
[Groups/0/Items/0]
# Name
Name=keyboard-us
# Layout
Layout=
[Groups/0/Items/1]
# Name
Name=pinyin
# Layout
Layout=
[GroupOrder]
0=默认
Log:
date:
Mon Nov 11 00:34:24 CST 2024
/home/cx/.config/fcitx5/crash.log:
/home/cx/.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:
Summary
Steps to Reproduce
输入法的尺寸符合预期,但是文字和背景有明显的清晰度差异。
Expected Behavior
这是在xfce X11环境下使用双倍尺寸svg素材、设置更大的边距得到的截图,可以模拟正确缩放之后的效果。
Output of fcitx5-diagnose command
完整输出 fcitx5-diagnose.txt
System Info:
uname -a
:lsb_release -a
:lsb_release -d
:/etc/lsb-release
:/etc/lsb-release
not found./etc/os-release
:Desktop Environment:
Desktop environment is
kde
.XDG SESSION TYPE:
Bash Version:
Environment:
DISPLAY:
Fcitx State:
executable:
Found fcitx5 at
/usr/bin/fcitx5
.version:
Fcitx version:
5.1.11
process:
Found 2 fcitx5 processes:
fcitx5-remote
:fcitx5-remote
works properly.DBus interface:
Using
dbus-send
to check dbus.Owner of DBus name
org.fcitx.Fcitx5
is:1.34
.PID of DBus name
org.fcitx.Fcitx5
owner is126190
.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:
kcmshell5
not found.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 "@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.Xim Server Name from Environment variable is ibus.
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}
: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.fcitx5-qt4-immodule-probing
not found.qt5 -
${QT_IM_MODULE}
: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.It is OK to use qt5 built-in Wayland im module if your compositor fully supports text-input protocol used by qt5.
Using fcitx5-qt5-immodule-probing to check the actual im module to be used under current environment:
qt6 -
${QT_IM_MODULE}
: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.It is OK to use qt6 built-in Wayland im module if your compositor fully supports text-input protocol used by qt6.
Using fcitx5-qt6-immodule-probing to check the actual im module to be used under current environment:
Qt IM module files:
Found fcitx5 qt5 module:
/lib64/fcitx5/qt5/libfcitx-quickphrase-editor5.so
.Found fcitx5 qt6 module:
/lib64/fcitx5/qt6/libfcitx-quickphrase-editor5.so
.Found fcitx5 im module for qt5:
/lib64/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so
.Found fcitx5 im module for qt6:
/lib64/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}
: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.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:
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:
Found
gtk-query-immodules
for gtk2.24.33
at/usr/bin/gtk-query-immodules-2.0-64
.Version Line:
Found fcitx5 im modules for gtk
2.24.33
.gtk 3:
Found
gtk-query-immodules
for gtk3.24.43
at/usr/bin/gtk-query-immodules-3.0-64
.Version Line:
Found fcitx5 im modules for gtk
3.24.43
.Gtk IM module cache:
gtk 2:
Found immodules cache for gtk
2.24.33
at/lib64/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.43
at/lib64/gtk-3.0/3.0.0/immodules.cache
.Version Line:
Found fcitx5 im modules for gtk
3.24.43
.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 28 enabled addons:
Found 1 disabled addons:
Addon Libraries:
All libraries for all addons are found.
User Interface:
Found 3 enabled user interface addons:
Input Methods:
/home/cx/.config/fcitx5/profile
:Log:
date
:/home/cx/.config/fcitx5/crash.log
:/home/cx/.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: