-
Notifications
You must be signed in to change notification settings - Fork 120
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
Desktop environment becomes laggy after fcitx5 running for a long time #824
Comments
Can you check if fcitx is using abnormal amount of memory or CPU when you find it's laggy? Is there any other process using cpu? Also, can you run fcitx5-diagnose when you think it's laggy? |
System Info:
Environment:
Fcitx State:
Fcitx Configure UI:
Frontends setup: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. |
@wengxt here are the contents of
|
You seems to run a lot of applications already on the system. I don't know if that matters. I don't think things like minimize a window could be affected by fcitx at all. Are you using a fcitx theme that has kwin blur feature enabled or sth? |
|
有没有试过重启 kwin |
kwin_x11 --replace |
same issue here, I'd love to test that while my device is getting laggy. |
Desktop operation likes moving or minimizing window becomes laggy.
These disappear after restarting fcitx5.
fcitx5-diagnose
result(after restarting):System Info:
uname -a
:lsb_release -a
:lsb_release -d
:/etc/lsb-release
:/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_HOME
is not set.Current value of
XDG_CONFIG_HOME
is~/.config
(/home/hsz/.config
).Fcitx5 Settings Directory:
Current fcitx5 settings directory is
~/.config/fcitx5
(/home/hsz/.config/fcitx5
).Current user:
The script is run as hsz (1000).
Fcitx State:
executable:
Found fcitx5 at
/usr/bin/fcitx5
.version:
Fcitx version:
5.0.23
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.21721
.PID of DBus name
org.fcitx.Fcitx5
owner is843293
.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:
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.
Qt:
qt4 -
${QT4_IM_MODULE}
:Environment variable QT_IM_MODULE is set to "fcitx" correctly.
qt5 -
${QT_IM_MODULE}
:Environment variable QT_IM_MODULE is set to "fcitx" correctly.
Qt IM module files:
Found fcitx5 im module for qt6:
/usr/lib/qt6/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so
.Found fcitx5 im module for qt:
/usr/lib/qt/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so
.Found unknown fcitx qt module:
/usr/lib/qt/plugins/kcms/kcm_fcitx5.so
.Found fcitx5 qt5 module:
/usr/lib/fcitx5/qt5/libfcitx-quickphrase-editor5.so
.Found unknown fcitx qt module:
/usr/lib/office6/qt/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.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.
gtk-query-immodules
:gtk 2:
Found
gtk-query-immodules
for gtk2.24.33
at/usr/bin/gtk-query-immodules-2.0
.Version Line:
Found fcitx5 im modules for gtk
2.24.33
.gtk 3:
Found
gtk-query-immodules
for gtk3.24.37
at/usr/bin/gtk-query-immodules-3.0
.Version Line:
Found fcitx5 im modules for gtk
3.24.37
.Found
gtk-query-immodules
for gtk3.24.37
at/usr/bin/gtk-query-immodules-3.0-32
.Version Line:
Failed to find fcitx5 in the output of
/usr/bin/gtk-query-immodules-3.0-32
Gtk IM module cache:
gtk 2:
Found immodules cache for gtk
2.24.33
at/usr/lib/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.37
at/usr/lib/gtk-3.0/3.0.0/immodules.cache
.Version Line:
Found fcitx5 im modules for gtk
3.24.37
.Found immodules cache for gtk
3.24.37
at/usr/lib32/gtk-3.0/3.0.0/immodules.cache
.Version Line:
Failed to find fcitx5 in immodule cache at
/usr/lib32/gtk-3.0/3.0.0/immodules.cache
gtk 4:
Cannot find immodules cache for gtk 4
Cannot find fcitx5 im module for gtk 4 in cache.
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 25 enabled addons:
Found 1 disabled addons:
Addon Libraries:
All libraries for all addons are found.
User Interface:
Found 2 enabled user interface addons:
Input Methods:
/home/hsz/.config/fcitx5/profile
:Log:
date
:/home/hsz/.config/fcitx5/crash.log
:/home/hsz/.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: