wengxt
commented
4 months ago 请汇报 bug 给 falkon，另外 workaround 你可以按 esc 关掉联想再继续输入。
Closed fxzxmic closed 4 months ago
wengxt
commented
4 months ago 请汇报 bug 给 falkon，另外 workaround 你可以按 esc 关掉联想再继续输入。
Summary
在Falkon浏览器的地址栏和搜索栏，只有输入框内无文本时才可以使用输入法，内部有文本的话，输入法会被关键词联想影响而导致无法输入。
Steps to Reproduce
Expected Behavior
在显示关键词联想的情况下依旧可以使用输入法输入。
Output of fcitx5-diagnose command
System Info:
uname -a:**
lsb_release:lsb_releasenot found./etc/lsb-release:/etc/lsb-releasenot found./etc/os-release:Desktop Environment:
Desktop environment is
kde.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_HOMEis not set.Current value of
XDG_CONFIG_HOMEis~/.config(/home/dev/.config).Fcitx5 Settings Directory:
Current fcitx5 settings directory is
~/.config/fcitx5(/home/dev/.config/fcitx5).Current user:
The script is run as dev (1000).
Fcitx State:
executable:
Found fcitx5 at
/usr/bin/fcitx5.version:
Fcitx version:
5.1.9process:
Found 3 fcitx5 processes:
fcitx5-remote:fcitx5-remoteworks properly.DBus interface:
Using
dbus-sendto check dbus.Owner of DBus name
org.fcitx.Fcitx5is:1.15.PID of DBus name
org.fcitx.Fcitx5owner is1015.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:
kcmshell5not 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/environfor 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:
Cannot find xim_server on root window.
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=fcitxto your~/.xprofile. See Input Method Related Environment Variables: QT_IM_MODULE.fcitx5-qt4-immodule-probingnot 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=fcitxto 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.
fcitx5-qt5-immodule-probingnot found.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=fcitxto 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 im module for qt6:
/usr/lib64/qt6/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so. Found unknown fcitx qt module:/usr/lib64/qt6/plugins/plasma/kcms/systemsettings/kcm_fcitx5.so. Found fcitx5 qt6 module:/usr/lib64/fcitx5/qt6/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. Cannot find fcitx5 input method module for Qt5.
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=fcitxto 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.
fcitx5-gtk2-immodule-probingnot found.Using fcitx5-gtk3-immodule-probing to check the actual im module to be used under current environment:
fcitx5-gtk4-immodule-probingnot found.gtk-query-immodules:gtk 2:
Cannot find
gtk-query-immodulesfor gtk 2Cannot find fcitx5 im module for gtk 2.
gtk 3:
Found
gtk-query-immodulesfor gtk3.24.42at/usr/bin/gtk-query-immodules-3.0-64. Version Line:Found fcitx5 im modules for gtk
3.24.42.Gtk IM module cache:
gtk 2:
Cannot find immodules cache for gtk 2
Cannot find fcitx5 im module for gtk 2 in cache.
gtk 3:
Found immodules cache for gtk
3.24.42at/usr/lib64/gtk-3.0/3.0.0/immodules.cache. Version Line:Found fcitx5 im modules for gtk
3.24.42.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 17 enabled addons:
Found 10 disabled addons:
Addon Libraries:
All libraries for all addons are found.
User Interface:
Found 3 enabled user interface addons:
Input Methods:
/home/dev/.config/fcitx5/profile:Log:
date:/home/dev/.config/fcitx5/crash.log:/home/dev/.config/fcitx5/crash.lognot found.