Closed foriequal0 closed 3 days ago
Hmm. it isn't reproduced anymore... weird.
So, it looks like you're using gnome. So you might be using qt's text-input-v3, which is quite buggy afaik.
Fcitx can't really help here. Telegram may have custom optimization on using wayland or not.
DebugInfo shows you might be using ibus im module now, which might solve your issue. I believe using either ibus or fcitx for QT_IM_MODULE would be ok on gnome for now.
Summary
I'm not sure who's responsible for this bug: Telegram Desktop (Downloaded tar.xz from here https://desktop.telegram.org/), QT, Ubuntu, or fcitx5.
Before Ubuntu 24.10, it did this infrequently. I can reliably reproduce this after I updated to Ubuntu 24.10. Losing focus and getting the focus back to Telegram made fcitx5 stop functioning. Always English is typed although the tray icon shows it is in 'Hangul' mode. (I use
fcitx5-hangul
). I haven't tried other IMs or other QT apps.Steps to Reproduce
Any of these make fcitx5-related functions stop working, not just inputting Korean. Sometimes Hangul key is problematic in Linux, so I changed the 'Trigger Input Method' hotkey to other conventional keys such as
Ctrl+Space
, but it didn't work either. So, I checked other extensions were fine, so I tried to invoke the 'Input method selector' with other shortcuts. It also didn't work.But it works fine when I switch the focus to Telegram using a mouse click. Also, it starts to work again when I alt-tab and make any change in the UI state (e.g. right-clicking an input box to show the context menu, or showing up and closing the user profile info modal)
Also, it is fine under Gnome Xorg. It happens only with Gnome Wayland, Ubuntu Wayland.
Expected Behavior
Be able to type in Korean, and to use fcitx5 shortcuts.
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/foriequal0/.config
).Fcitx5 Settings Directory:
Current fcitx5 settings directory is
~/.config/fcitx5
(/home/foriequal0/.config/fcitx5
).Current user:
The script is run as foriequal0 (1000).
Fcitx State:
executable:
Found fcitx5 at
/usr/bin/fcitx5
.version:
Fcitx version:
5.1.10
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.1121
.PID of DBus name
org.fcitx.Fcitx5
owner is48312
.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}
:XMODIFIERS is not set
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 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}
: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 im module for qt5:
/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so
. Found fcitx5 qt5 module:/lib/x86_64-linux-gnu/fcitx5/qt5/libfcitx-quickphrase-editor5.so
. Found fcitx5 qt6 module:/lib/x86_64-linux-gnu/fcitx5/qt6/libfcitx-quickphrase-editor5.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}
: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.
fcitx5-gtk2-immodule-probing
not found.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:Failed to find fcitx5 in immodule cache at
/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules.cache
Cannot find fcitx5 im module for gtk 2 in cache.
gtk 3:
Found immodules cache for gtk
3.24.43
at/lib/x86_64-linux-gnu/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 21 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/foriequal0/.config/fcitx5/profile
:Log:
date
:/home/foriequal0/.config/fcitx5/crash.log
:/home/foriequal0/.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.