hanja key does not work properly on veracrypt

[234135396879774804062264191513872605089]

Summary

All other program works well. Only veracrypt password input scene has problem.

Can confirm that 1~5/Up/Down key works. But only all thing that related to mouse does not work on veracrypt password input scene

Steps to Reproduce

1. Open veracrypt
2. try to mount encrypt disk
3. enable "Display password"
4. type any letter that can be used for pressing hanja key, then press hanja key
5. now you can confirm that all mouse related things does not work for hanja selection popup

Expected Behavior

mouse click should work for hanja selection popup on veracrypt like other case could.

Output of fcitx5-diagnose command

System Info:

1. uname -a:

   Linux debian 6.12.74+deb13+1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.74-2 (2026-03-08) x86_64 GNU/Linux
   

2. lsb_release -a:

   Distributor ID: Debian
   Description:    Debian GNU/Linux 13 (trixie)
   Release:        13
   Codename:       trixie
   

3. lsb_release -d:

   Description:    Debian GNU/Linux 13 (trixie)
   

4. /etc/lsb-release:

   /etc/lsb-release not found.

5. /etc/os-release:

   PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
   NAME="Debian GNU/Linux"
   VERSION_ID="13"
   VERSION="13 (trixie)"
   VERSION_CODENAME=trixie
   DEBIAN_VERSION_FULL=13.4
   ID=debian
   HOME_URL="https://www.debian.org/"
   SUPPORT_URL="https://www.debian.org/support"
   BUG_REPORT_URL="https://bugs.debian.org/"
   

6. Desktop Environment:

   Desktop environment is kde.

7. XDG SESSION TYPE:

   XDG_SESSION_TYPE='wayland'
   

8. Bash Version:

   BASH_VERSION='5.2.37(1)-release'
   

Environment:

1. DISPLAY:

   DISPLAY=':1'
   
   
   WAYLAND_DISPLAY='wayland-0'
   

2. Keyboard Layout:

   1. setxkbmap:

      WARNING: Running setxkbmap against an Xwayland server
      xkb_keymap {
          xkb_keycodes  { include "evdev+aliases(qwerty)" };
          xkb_types     { include "complete"      };
          xkb_compat    { include "complete"      };
          xkb_symbols   { include "pc+us+inet(evdev)"     };
          xkb_geometry  { include "pc(pc105)"     };
      };
      

   2. xprop:

      _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", ""
      

3. Locale:

   1. All locales:

      C
      C.utf8
      en_US.utf8
      POSIX
      

   2. Current locale:

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

4. Directories:

   1. Home:

      /home/user
      

   2. ${XDG_CONFIG_HOME}:

      Environment variable XDG_CONFIG_HOME is not set.

      Current value of XDG_CONFIG_HOME is ~/.config (/home/user/.config).

   3. Fcitx5 Settings Directory:

      Current fcitx5 settings directory is ~/.config/fcitx5 (/home/user/.config/fcitx5).

5. Current user:

   The script is run as user (1000).

Fcitx State:

1. executable:

   Found fcitx5 at /usr/bin/fcitx5.

2. version:

   Fcitx version: 5.1.12

3. process:

   Found 1 fcitx5 process:

      1895 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.74.

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

   Debug information from dbus:

      Group [wayland:] has 35 InputContext(s)
     IC [34d3479e7a7d46ada9ae7af6e4b012a2] program:konsole frontend:dbus cap:e001820872 focus:1
     IC [c0126684c94348ccb0af5b87fc83a6fb] program:veracrypt frontend:dbus cap:6001000032 focus:0
     IC [5c7eb57b14ef4df7a73842bd2540c0e1] program:veracrypt frontend:dbus cap:6001000032 focus:0
     IC [691e794265b44d70a0964fb7053a3279] program:veracrypt frontend:dbus cap:6001000032 focus:0
     IC [bd2fca286f954c3b8039936b155ba82d] program:veracrypt frontend:dbus cap:6001000032 focus:0
     IC [7f5102dad91e48b89b49967a06a6fb5e] program:veracrypt frontend:dbus cap:e00100007a focus:0
     IC [67024a559e4141c4904246907f014045] program:veracrypt frontend:dbus cap:6001000032 focus:0
     IC [819c61fb83844065a0e2b46f73337446] program:plasmashell frontend:dbus cap:1e001800072 focus:0
     IC [adcbaf9fec0d4ac4b2a2b66e71acc73a] program:plasmashell frontend:dbus cap:1e001800072 focus:0
     IC [af4a7a3badcd4080a5d1850e8d165c5e] program:veracrypt frontend:dbus cap:6001000020 focus:0
     IC [05a9a7a5293a4c8eb07c90d0a643c34b] program:veracrypt frontend:dbus cap:e001000072 focus:0
     IC [49a6334603784bb3a8fade3851edf98c] program:plasmashell frontend:dbus cap:1e001800072 focus:0
     IC [d903284b316f488eb25bac40d5edce4e] program:veracrypt frontend:dbus cap:e001000020 focus:0
     IC [66f1569cf9ee4abdbdcc65e1d71470f7] program:veracrypt frontend:dbus cap:6001000020 focus:0
     IC [c27263b929f34d5e8f9565a0b2b38f09] program:plasmashell frontend:dbus cap:1e001800072 focus:0
     IC [54376d30a0954607b3b22f129fcb1b11] program:veracrypt frontend:dbus cap:e001000020 focus:0
     IC [67983b1a44744820b65ad9de74981603] program:veracrypt frontend:dbus cap:6001000020 focus:0
     IC [62bd2accf0ad45d4a0d54123f068241c] program:veracrypt frontend:dbus cap:e001000020 focus:0
     IC [36c9e9f5237046f6a375c3237b8b0cca] program:veracrypt frontend:dbus cap:6001000032 focus:0
     IC [c954a60d9c12486cad15153005abf7bf] program:veracrypt frontend:dbus cap:6001000020 focus:0
     IC [2ba929e37f934178952ad0592292be6e] program:veracrypt frontend:dbus cap:6001000032 focus:0
     IC [b9ea2aba72bd4ffda298adb2e63e4582] program:veracrypt frontend:dbus cap:6001000032 focus:0
     IC [e4533d5aa1d54fa3ad8b005a12660b12] program:veracrypt frontend:dbus cap:6001000020 focus:0
     IC [f297af3b3c4c49da9adc6ff182a835fa] program:veracrypt frontend:dbus cap:6001000020 focus:0
     IC [68137c1eef0148b0989f52e1eeb04332] program:veracrypt frontend:dbus cap:6001000020 focus:0
     IC [f39f088f3583448fbf5e3620f261ffca] program:plasmashell frontend:dbus cap:1e001800072 focus:0
     IC [769201dabe6a41d5b5eb36ac1548eea1] program:veracrypt frontend:dbus cap:e001000020 focus:0
     IC [0fdd1546bc7a49cb9baa5d99bfe2b1da] program:plasmashell frontend:dbus cap:1e001800072 focus:0
     IC [71731b41c5a74fc28338fbe3202d70f0] program:plasmashell frontend:dbus cap:1e001800072 focus:0
     IC [649af788b40c435c8fb48bc900a8a38b] program:protonvpn-app frontend:dbus cap:c001000072 focus:0
     IC [5c570678ed3746709a4825e5461db37a] program:plasmashell frontend:dbus cap:1e001800072 focus:0
     IC [30e6c431d90c49c5bf09e48f7aa6cff6] program:veracrypt frontend:dbus cap:e001000020 focus:0
     IC [d913ed0470bd4ea486ab0d924e1e5889] program:veracrypt frontend:dbus cap:e001000020 focus:0
     IC [48bd7639900647aba095e26a47385a61] program:veracrypt frontend:dbus cap:e001000020 focus:0
     IC [0a1b8c6ec6fa4fd580675a10eba5ab86] program:plasmashell frontend:dbus cap:1e001800072 focus:0
   Group [x11::1] has 0 InputContext(s)
   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:

   Xim server name is the same with that set in the environment variable.

Qt:

1. qt4 - ${QT4_IM_MODULE}:

   Environment variable QT_IM_MODULE is set to "fcitx" correctly.

   fcitx5-qt4-immodule-probing not found.

2. 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=wayland
   QT_IM_MODULE=fcitx
   IM_MODULE_CLASSNAME=fcitx::QFcitxPlatformInputContext
   

3. 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=wayland
   QT_IM_MODULE=fcitx
   IM_MODULE_CLASSNAME=fcitx::QFcitxPlatformInputContext
   

4. Qt IM module files:

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

1. 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
   

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:

      Cannot find gtk-query-immodules for gtk 3

      Cannot find fcitx5 im module for gtk 3.

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.49 at /usr/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.49
      

      Found fcitx5 im modules for gtk 3.24.49.

      "/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:*" 
      

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 21 enabled addons:

      Classic User Interface 5.1.12
      Clipboard 5.1.12
      DBus 5.1.12
      DBus Frontend 5.1.12
      Emoji 5.1.12
      Fcitx4 Frontend 5.1.12
      Hangul 5.1.6
      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
      Quick Phrase 5.1.12
      Spell 5.1.12
      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. /home/user/.config/fcitx5/profile:

   [Groups/0]
   # Group Name
   Name=Default
   # Layout
   Default Layout=us
   # Default Input Method
   DefaultIM=hangul
   
   [Groups/0/Items/0]
   # Name
   Name=keyboard-us
   # Layout
   Layout=
   
   [Groups/0/Items/1]
   # Name
   Name=hangul
   # Layout
   Layout=
   
   [GroupOrder]
   0=Default
   

Log:

1. date:

   Tue Apr 28 05:25:52 PM JST 2026
   

2. /home/user/.config/fcitx5/crash.log:

   /home/user/.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.

[wengxt]

Are you saying you want to use input method within a password field?

There's an option to allow use regular input method feature in password field in global options.

[295924543907319018832217504886746765061]

Override Xkb Option, Allow input method in the password field, Show preedit text when typing password

all of three does not work

and as I said, I am talking about mouse does not working. All thing related with Keyboard works fine. I don't think this is related with input method