You are not logged in.
- Topics: Active | Unanswered
#1 2025-02-09 21:51:45
- LightBlueCube
- Member
- Registered: 2025-02-09
- Posts: 9
fcitx5 not work in CS2 [KDE, Wayland, steam]
first at all, my english isnt very well and im sorry abou this, and i have a poor skills
if u have any question or need more infomation, please let me know
im using KDE Wayland and installed fcitx5
its working normally everywhere execpt on CS2
when i foucs on CS2, fcitx5 no action for any hotkeys or button
i found those similar infos, that may cloud give some help
[Not work for me] https://github.com/ValveSoftware/steam- … 2565050431
[Not work for me] https://wiki.archlinux.org/title/Fcitx5 … and_Dota_2
i have setup the fcitx on KDE virtual keyboard
also i know the debian distro with KDE5 can use fcitx5 normally on CS2, no ide how they did that
here is my /etc/environment
[lightbluecube@Archlinux ~]$ cat /etc/environment
#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
#QT_IM_MODULE=fcitx
#GTK_IM_MODULE=fcitx
XMODIFIERS=@im=fcitx
SDL_IM_MODULE=fcitx
GLFW_IM_MODULE=fcitx the infomation about fcitx5-diagnose
also my LANG is zh_CN.UTF-8, but i need print those log with english, so i switched to en_GB.UTF-8 temporary
# System Info:
1. `uname -a`:
Linux Archlinux 6.13.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 08 Feb 2025 18:54:55 +0000 x86_64 GNU/Linux
2. `lsb_release -a`:
LSB Version: n/a
Distributor ID: Arch
Description: Arch Linux
Release: rolling
Codename: n/a
3. `lsb_release -d`:
Description: Arch Linux
4. `/etc/lsb-release`:
DISTRIB_ID="Arch"
DISTRIB_RELEASE="rolling"
DISTRIB_DESCRIPTION="Arch Linux"
5. `/etc/os-release`:
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo
6. Desktop Environment:
Cannot determine desktop environment.
7. XDG SESSION TYPE:
XDG_SESSION_TYPE='tty'
8. Bash Version:
BASH_VERSION='5.2.37(1)-release'
# Environment:
1. DISPLAY:
DISPLAY=''
WAYLAND_DISPLAY=''
2. Keyboard Layout:
1. `setxkbmap`:
Cannot open display "default display"
2. `xprop`:
xprop: unable to open display ''
3. Locale:
1. All locales:
C
C.utf8
POSIX
en_US.utf8
zh_CN.utf8
2. Current locale:
LANG=en_GB.UTF-8
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=
**Error occurs when running `locale`. Please check your locale settings.**
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
4. Directories:
1. Home:
/root
2. `${XDG_CONFIG_HOME}`:
Environment variable `XDG_CONFIG_HOME` is not set.
Current value of `XDG_CONFIG_HOME` is `~/.config` (`/root/.config`).
3. Fcitx5 Settings Directory:
Current fcitx5 settings directory is `~/.config/fcitx5` (`/root/.config/fcitx5`).
5. Current user:
The script is run as root (0).
1. `sudo` Environment Variables:
SUDO_COMMAND is not set.
SUDO_USER is not set.
SUDO_UID is not set.
SUDO_GID is not set.
2. Running as root:
**You are probably logging in as `root` or using `sudo` to run this script. This either means you have security problems or the result of this script may not be accurate. See [Why is it bad to run as root](https://www.google.com/search?q=Why+is+it+bad+to+run+as+root) or [sudo environment variables](https://www.google.com/search?q=sudo+environment+variables) for more information.**
# Fcitx State:
1. executable:
Found fcitx5 at `/usr/bin/fcitx5`.
2. version:
Fcitx version: `5.1.12`
3. process:
Found 3 fcitx5 processes:
1128 fcitx5
1222 fcitx5-plasma-t
6587 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.4`.
PID of DBus name `org.fcitx.Fcitx5` owner is `6587`.
Debug information from dbus:
Input Context without group
# 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 "@im=fcitx" correctly.
Xim Server Name from Environment variable is fcitx.
2. XIM_SERVERS on root window:
**Cannot find xim_server on root window.**
## Qt:
1. 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](http://fcitx-im.org/wiki/Input_method_related_environment_variables#QT_IM_MODULE).**
**`fcitx5-qt4-immodule-probing` not found.**
2. 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](http://fcitx-im.org/wiki/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:
3. 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](http://fcitx-im.org/wiki/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:
4. Qt IM module files:
Found fcitx5 im module for qt6: `/usr/lib/qt6/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so`.
Found unknown fcitx qt module: `/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_fcitx5.so`.
Found fcitx5 im module for qt: `/usr/lib/qt/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so`.
Found fcitx5 qt6 module: `/usr/lib/fcitx5/qt6/libfcitx-quickphrase-editor5.so`.
Found fcitx5 qt5 module: `/usr/lib/fcitx5/qt5/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.**
## Gtk:
1. 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](http://fcitx-im.org/wiki/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:
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:
Found `gtk-query-immodules` for gtk `3.24.48` at `/usr/bin/gtk-query-immodules-3.0`.
Version Line:
# Created by /usr/bin/gtk-query-immodules-3.0 from gtk+-3.24.48
Found fcitx5 im modules for gtk `3.24.48`.
"/usr/lib/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:*"
3. Gtk IM module cache:
1. gtk 2:
**Cannot find immodules cache for gtk 2**
**Cannot find fcitx5 im module for gtk 2 in cache.**
2. gtk 3:
Found immodules cache for gtk `3.24.48` at `/usr/lib/gtk-3.0/3.0.0/immodules.cache`.
Version Line:
# Created by /usr/bin/gtk-query-immodules-3.0 from gtk+-3.24.48
Found fcitx5 im modules for gtk `3.24.48`.
"/usr/lib/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 28 enabled addons:
Simplified and Traditional Chinese Translation 5.1.7
Classic User Interface 5.1.12
Clipboard 5.1.12
Cloud Pinyin 5.1.7
DBus 5.1.12
DBus Frontend 5.1.12
Emoji 5.1.12
Fcitx4 Frontend 5.1.12
Full width character 5.1.7
IBus Frontend 5.1.12
Input method selector 5.1.12
Keyboard 5.1.12
KDE Input Method Panel 5.1.12
Status Notifier 5.1.12
Notification 5.1.12
Pinyin 5.1.7
Extra Pinyin functionality 5.1.7
Punctuation 5.1.7
Quick Phrase 5.1.12
Rime 5.1.10
Spell 5.1.12
Table 5.1.7
Unicode 5.1.12
DBus Virtual Keyboard 5.1.12
Wayland 5.1.12
Wayland Input method frontend 5.1.12
XCB 5.1.12
X Input Method Frontend 5.1.12
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. `/root/.config/fcitx5/profile`:
`/root/.config/fcitx5/profile` not found.
# Log:
1. `date`:
Mon Feb 10 13:48:11 CST 2025
2. `/root/.config/fcitx5/crash.log`:
`/root/.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.**Last edited by LightBlueCube (2025-02-09 22:13:54)
Offline