Specific App Problem #1272

grahamiam · 2025-02-18T06:22:54Z

Summary

I'm running World of Warcraft using Lutris + Wine.

Inside the game, English works fine. Switching to Chinese works fine. When I type in Chinese, the Pinyin panel appears, but in the wrong spot (in the upper left corner, not by the cursor). After I select characters in Pinyin they are not inputted into the game.

Copying and pasting Chinese characters while English keyboard is selected also works fine.

I suspect this is not fcitx's fault because the Windows key also doesn't work while inside game, but I'm trying to figure out next steps.

The odd thing is, it works fine with the Battle.net launcher, which has the exact same launch options as World of Warcraft. I also have not found another app with the same problem yet, but I don't run that many apps that I type in.

Steps to Reproduce

Try to type in World of Warcraft chat. Pinyin panel appears, select characters, no input to application happens.

Expected Behavior

Normal typing and Pinyin panel placement.

Output of fcitx5-diagnose command

graham@gdesktop:~$ fcitx5-diagnose

System Info:

uname -a:

Linux gdesktop 6.8.0-53-generic #55-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 17 15:37:52 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a:

Distributor ID:	Linuxmint
Description:	Linux Mint 22.1
Release:	22.1
Codename:	xia

lsb_release -d:
```
Description:	Linux Mint 22.1
```

/etc/lsb-release:

DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=22.1
DISTRIB_CODENAME=xia
DISTRIB_DESCRIPTION="Linux Mint 22.1 Xia"

/etc/os-release:

NAME="Linux Mint"
VERSION="22.1 (Xia)"
ID=linuxmint
ID_LIKE="ubuntu debian"
PRETTY_NAME="Linux Mint 22.1"
VERSION_ID="22.1"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=xia
UBUNTU_CODENAME=noble

Desktop Environment:

Desktop environment is cinnamon.
XDG SESSION TYPE:
```
XDG_SESSION_TYPE='x11'
```
Bash Version:
```
BASH_VERSION='5.2.21(1)-release'
```

Environment:

DISPLAY:
```
DISPLAY=':0'


WAYLAND_DISPLAY=''
```

Keyboard Layout:

setxkbmap:

xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+us+inet(evdev)+terminate(ctrl_alt_bksp)+group(win_space_toggle)"	};
	xkb_geometry  { include "pc(pc105)"	};
};

xprop:

_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", "grp:win_space_toggle,terminate:ctrl_alt_bksp"

Locale:

All locales:

C
C.utf8
en_AG
en_AG.utf8
en_AU.utf8
en_BW.utf8
en_CA.utf8
en_DK.utf8
en_GB.utf8
en_HK.utf8
en_IE.utf8
en_IL
en_IL.utf8
en_IN
en_IN.utf8
en_NG
en_NG.utf8
en_NZ.utf8
en_PH.utf8
en_SG.utf8
en_US.utf8
en_ZA.utf8
en_ZM
en_ZM.utf8
en_ZW.utf8
lzh_TW
lzh_TW.utf8
POSIX

Current locale:

LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=lzh_TW
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=lzh_TW
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=lzh_TW
LC_NAME=lzh_TW
LC_ADDRESS=lzh_TW
LC_TELEPHONE=lzh_TW
LC_MEASUREMENT=lzh_TW
LC_IDENTIFICATION=lzh_TW
LC_ALL=

Directories:
1. Home:
```
/home/graham
```
2. ${XDG_CONFIG_HOME}:
  
  Environment variable XDG_CONFIG_HOME is not set.
  
  Current value of XDG_CONFIG_HOME is ~/.config (/home/graham/.config).
3. Fcitx5 Settings Directory:
  
  Current fcitx5 settings directory is ~/.config/fcitx5 (/home/graham/.config/fcitx5).
Current user:

The script is run as graham (1000).

Fcitx State:

executable:

Found fcitx5 at /usr/bin/fcitx5.
version:

Fcitx version: 5.1.7
process:

Found 1 fcitx5 process:
```
   2874 fcitx5
```
fcitx5-remote:

fcitx5-remote works properly.

DBus interface:

Using dbus-send to check dbus.

Owner of DBus name org.fcitx.Fcitx5 is :1.86.

PID of DBus name org.fcitx.Fcitx5 owner is 2874.

Debug information from dbus:

   Group [x11::0] has 31 InputContext(s)
  IC [32d0ea2eee7d478caf0f66a2350ce2e9] program:signal-desktop frontend:fcitx4 cap:12 focus:0
  IC [9277c4cde8884863b1378d3561cdde2e] program: frontend:xim cap:4000000000 focus:0
  IC [6bb88b37e7884e598a99e59449003837] program:net.lutris.Lutris frontend:dbus cap:6000000032 focus:0
  IC [09904dc7b5b0424a952d7454c207cf4c] program:firefox-bin frontend:fcitx4 cap:0 focus:0
  IC [8271d47a761049a88fae42ef559a0207] program: frontend:dbus cap:12 focus:0
  IC [5b80e2f99d934bbbb42ada2dba9f13c4] program: frontend:dbus cap:12 focus:0
  IC [6995c293ad344481b8903b3261d165ef] program:nemo-desktop frontend:fcitx4 cap:12 focus:0
  IC [4d75c5a3df53457c8cabf9fbd3251663] program: frontend:dbus cap:12 focus:0
  IC [248dd3043c7a402f8e00c37f8b2733ed] program:nemo-desktop frontend:fcitx4 cap:12 focus:0
  IC [f0b7a92c3057479694d4bdbc6665d2b4] program:firefox-bin frontend:fcitx4 cap:0 focus:0
  IC [af36d59680134346adb88d75b71c224f] program:firefox-bin frontend:fcitx4 cap:0 focus:0
  IC [e937409bcaff456ab38b08c91b222d33] program:nemo-desktop frontend:fcitx4 cap:12 focus:0
  IC [8a33fd37d1384a6299e23bcb2fd7c743] program:firefox-bin frontend:fcitx4 cap:0 focus:0
  IC [f7d793bf864944b882f720361a17d1f2] program: frontend:dbus cap:12 focus:0
  IC [ef5240073fdc4ee8aba2b727e6e86c13] program: frontend:dbus cap:12 focus:0
  IC [f5fba56a6eb04977a7297726682f1b0f] program: frontend:dbus cap:12 focus:0
  IC [b2994d2500f94cb6aa63adc36b8b6015] program: frontend:dbus cap:12 focus:0
  IC [3d18d932ded940eea201ed600026cd82] program: frontend:dbus cap:12 focus:0
  IC [fa488f1733374d1b94b3cba0c4148c0a] program: frontend:dbus cap:12 focus:0
  IC [9276afdaa6c543ccb67bb2a53c4fb77a] program:gnome-terminal- frontend:fcitx4 cap:12 focus:1
  IC [cc9b8990f27f4465b054c905ec8d5473] program: frontend:dbus cap:52 focus:0
  IC [00c06aa7c1b84e60b23af93e50870960] program: frontend:dbus cap:12 focus:0
  IC [104b8179f35e44729514769eefbf1689] program:firefox-bin frontend:fcitx4 cap:0 focus:0
  IC [51d820e2a04546598f35dc5808d9189f] program: frontend:dbus cap:12 focus:0
  IC [0b6f71e095564f0795923c6eab1dda18] program: frontend:dbus cap:12 focus:0
  IC [f16db1cb55134f14bca0c5f3fbb932dc] program: frontend:dbus cap:12 focus:0
  IC [bd7368d16e63478dbe46a4634d5badab] program: frontend:dbus cap:12 focus:0
  IC [19cbde8722eb4abc8c55eef709ac07b9] program: frontend:dbus cap:12 focus:0
  IC [cc10f7612dbb4530921168e0268db918] program: frontend:dbus cap:12 focus:0
  IC [d959c13938cb49988ffad3be991eee9f] program:firefox-bin frontend:fcitx4 cap:0 focus:0
  IC [a1549f2dd26d4cdab499481458e71626] program: frontend:dbus cap:12 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 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.

fcitx5-qt4-immodule-probing not found.
qt5 - ${QT_IM_MODULE}:

Environment variable QT_IM_MODULE is set to "fcitx" correctly.

Using fcitx5-qt5-immodule-probing to check the actual im module to be used under current environment:
```
QT_QPA_PLATFORM=xcb
QT_IM_MODULE=fcitx
IM_MODULE_CLASSNAME=fcitx::QFcitxPlatformInputContext
```
qt6 - ${QT_IM_MODULE}:

Environment variable QT_IM_MODULE is set to "fcitx" correctly.

Using fcitx5-qt6-immodule-probing to check the actual im module to be used under current environment:
```
QT_QPA_PLATFORM=xcb
QT_IM_MODULE=fcitx
IM_MODULE_CLASSNAME=QFcitxPlatformInputContext
```
Qt IM module files:

Found fcitx5 im module for qt5: /lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so.
Found unknown fcitx qt module: /lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so.
Found unknown fcitx qt module: /lib/x86_64-linux-gnu/qt6/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin-qt6.so.
Found fcitx5 im module for qt6: /lib/x86_64-linux-gnu/qt6/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so.
Found unknown fcitx qt module: /lib/x86_64-linux-gnu/fcitx/qt/libfcitx-quickphrase-editor5.so.
Found fcitx5 qt6 module: /lib/x86_64-linux-gnu/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.

Gtk:

gtk - ${GTK_IM_MODULE}:

Environment variable GTK_IM_MODULE is set to "fcitx" correctly.

fcitx5-gtk2-immodule-probing not found.

Using fcitx5-gtk3-immodule-probing to check the actual im module to be used under current environment:
```
GTK_IM_MODULE=fcitx
```
Using fcitx5-gtk4-immodule-probing to check the actual im module to be used under current environment:
```
GTK_IM_MODULE=fcitx
```
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:
  
  Cannot find gtk-query-immodules for gtk 3
  
  Cannot 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:
```
# Created by /usr/lib/x86_64-linux-gnu/libgtk2.0-0t64/gtk-query-immodules-2.0 from gtk+-2.24.33
```
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.41 at /lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules.cache.
Version Line:

# Created by /usr/lib/x86_64-linux-gnu/libgtk-3-0t64/gtk-query-immodules-3.0 from gtk+-3.24.41

Found fcitx5 im modules for gtk 3.24.41.

"/usr/lib/x86_64-linux-gnu/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:*"

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:

Addon Config Dir:

Found fcitx5 addon config directory: /usr/share/fcitx5/addon.

Addon List:

Found 29 enabled addons:

Simplified and Traditional Chinese Translation 5.1.3
Classic User Interface 5.1.7
Clipboard 5.1.7
Cloud Pinyin 5.1.3
DBus 5.1.7
DBus Frontend 5.1.7
Emoji 5.1.7
Fcitx4 Frontend 5.1.7
Full width character 5.1.3
IBus Frontend 5.1.7
Lua IME API 5.0.12
Input method selector 5.1.7
Keyboard 5.1.7
KDE Input Method Panel 5.1.7
Lua Addon Loader 5.0.12
Status Notifier 5.1.7
Notification 5.1.7
Pinyin 5.1.3
Extra Pinyin functionality 5.1.3
Punctuation 5.1.3
Quick Phrase 5.1.7
Spell 5.1.7
Table 5.1.3
Unicode 5.1.7
DBus Virtual Keyboard 5.1.7
Wayland 5.1.7
Wayland Input method frontend 5.1.7
XCB 5.1.7
X Input Method Frontend 5.1.7

Found 0 disabled addons:

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/graham/.config/fcitx5/profile:

[Groups/0]
# Group Name
Name=Default
# 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=Default

Log:

date:
```
Tue Feb 18 02:20:59 PM CST 2025
```
/home/graham/.config/fcitx5/crash.log:

/home/graham/.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:

wengxt · 2025-02-20T01:05:29Z

can you try run in some other non en_US locale?

e.g. zh_CN.UTF-8 or zh_TW.UTF-8 (make sure your locale -a has them before you try , you may need to install some package since you're on debian-like system).

This locale thing can affect input method on xim and wine.

grahamiam · 2025-02-20T03:07:46Z

Thanks for the suggestion. I tried switching over the individual program to lzh_TW.utf8 and it broke the Pinyin entirely - would no longer switch. I also tried switching over the whole system instead and same thing. Then I installed zh_TW (not sure difference) and did the same two steps - this time there was no change from the original problem.

wengxt · 2025-02-23T20:56:04Z

Not having a good answer to it, but can you test if wine's built-in notepad works?

grahamiam · 2025-02-24T05:37:57Z

Notepad.exe works. I also tried Epic Games Store and Battle.net, both using the exact same Wine config, and they all worked. It's just this one application.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Specific App Problem #1272

Specific App Problem #1272

grahamiam commented Feb 18, 2025

wengxt commented Feb 20, 2025

grahamiam commented Feb 20, 2025

wengxt commented Feb 23, 2025

grahamiam commented Feb 24, 2025

Specific App Problem #1272

Specific App Problem #1272

Comments

grahamiam commented Feb 18, 2025

Summary

Steps to Reproduce

Expected Behavior

Output of fcitx5-diagnose command

System Info:

Environment:

Fcitx State:

Fcitx Configure UI:

Frontends setup:

Xim:

Qt:

Gtk:

Configuration:

Fcitx Addons:

Input Methods:

Log:

wengxt commented Feb 20, 2025

grahamiam commented Feb 20, 2025

wengxt commented Feb 23, 2025

grahamiam commented Feb 24, 2025