Skip to content
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

Cannot switch to fcitx and input in vlc #1117

Open
blackteahamburger opened this issue Aug 10, 2024 · 1 comment
Open

Cannot switch to fcitx and input in vlc #1117

blackteahamburger opened this issue Aug 10, 2024 · 1 comment

Comments

@blackteahamburger
Copy link

Summary

Cannot switch to fcitx and input in vlc

Steps to Reproduce

  1. Open vlc(3.0.21)
  2. Select an input box

Expected Behavior

Able to switch to fcitx and input in vlc.

Output of fcitx5-diagnose command

System Info:

  1. uname -a:

    Linux blacktea 6.10.3-tkg-bore #1 SMP PREEMPT TKG Tue Aug  6 13:37:34 CST 2024 x86_64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz GenuineIntel GNU/Linux
    
  2. lsb_release -a:

    LSB Version:    n/a
    Distributor ID: Gentoo
    Description:    Gentoo Linux
    Release:        2.15
    Codename:       n/a
    
  3. lsb_release -d:

    Description:    Gentoo Linux
    
  4. /etc/lsb-release:

    DISTRIB_ID="Gentoo"
    
  5. /etc/os-release:

    NAME=Gentoo
    ID=gentoo
    PRETTY_NAME="Gentoo Linux"
    ANSI_COLOR="1;32"
    HOME_URL="https://www.gentoo.org/"
    SUPPORT_URL="https://www.gentoo.org/support/"
    BUG_REPORT_URL="https://bugs.gentoo.org/"
    VERSION_ID="2.15"
    
  6. Desktop Environment:

    Desktop environment is kde.

  7. XDG SESSION TYPE:

    XDG_SESSION_TYPE='tty'
    
  8. Bash Version:

    BASH_VERSION='5.2.32(1)-release'
    

Environment:

  1. DISPLAY:

    DISPLAY=':0'
    
    
    WAYLAND_DISPLAY=''
    
  2. Keyboard Layout:

    1. setxkbmap:

      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
      POSIX
      zh_CN.utf8
      
    2. Current locale:

      LANG=zh_CN.utf8
      LC_CTYPE="C"
      LC_NUMERIC="C"
      LC_TIME="C"
      LC_COLLATE="C"
      LC_MONETARY="C"
      LC_MESSAGES="C"
      LC_PAPER="C"
      LC_NAME="C"
      LC_ADDRESS="C"
      LC_TELEPHONE="C"
      LC_MEASUREMENT="C"
      LC_IDENTIFICATION="C"
      LC_ALL=C
      
  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 or sudo environment variables for more information.

Fcitx State:

  1. executable:

    Found fcitx5 at /usr/bin/fcitx5.

  2. version:

    Fcitx version: 5.1.10

  3. process:

    Found 1 fcitx5 process:

        633 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.44.

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

    Debug information from dbus:

       Group [x11::0] has 10 InputContext(s)
      IC [45d09bd3a2504fb3a056c580228ac89a] program:qv2ray frontend:dbus cap:16000800072 focus:0
      IC [1f9d20e80c0a486a87a8f5788aa0a7df] program:qv2ray frontend:dbus cap:16000800072 focus:0
      IC [4978935f7a054b65bd7434fdac8094bf] program:qv2ray frontend:dbus cap:6000800072 focus:0
      IC [96dcd0b77c9c4d48bca60b7aa95a62e5] program:telegram-desktop frontend:dbus cap:6800800072 focus:0
      IC [09b3c61d22a341a584ad459d647f252c] program:thorium frontend:xim cap:4000000000 focus:0
      IC [d61905c2c827450bb5090a1e2d85c2df] program:yakuake frontend:dbus cap:6000820872 focus:1
      IC [5b5c8beec22841cc9fa73684b2430d46] program:plasmashell frontend:dbus cap:16000800072 focus:0
      IC [ba90a61ff9bd4201a2d61cdf7de40fd5] program:plasmashell frontend:dbus cap:16000800072 focus:0
      IC [2ebfef03a79245c0a0352de5bb51f2c5] program:yakuake frontend:dbus cap:16000800072 focus:0
      IC [4e8a8eef0e4c4a7db9087b8b61cab20a] program:plasmashell frontend:dbus cap:16000800072 focus:0
    Input Context without group
    

Fcitx Configure UI:

  1. Config Tool Wrapper:

    Found fcitx5-configtool at /usr/bin/fcitx5-configtool.

  2. Config GUI for qt:

    Found fcitx5-config-qt at /usr/bin/fcitx5-config-qt.

  3. 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:

  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.

  3. XIM encoding:

    Your LC_CTYPE is set to C whose encoding is not UTF-8. You may have trouble committing strings using XIM.

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.

    fcitx5-qt5-immodule-probing not found.

  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=xcb
    QT_IM_MODULE=fcitx
    IM_MODULE_CLASSNAME=fcitx::QFcitxPlatformInputContext
    
  4. Qt IM module files:

    Found fcitx5 im module for qt6: /usr/lib64/qt6/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so.
    Found unknown fcitx qt module: /usr/lib64/qt6/plugins/plasma/kcms/systemsettings/kcm_fcitx5.so.
    Found fcitx5 qt6 module: /usr/lib64/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.
    Cannot find fcitx5 input method module for Qt5.

Gtk:

  1. gtk - ${GTK_IM_MODULE}:

    Environment variable GTK_IM_MODULE is set to "fcitx" correctly.

    fcitx5-gtk2-immodule-probing not found.

    fcitx5-gtk3-immodule-probing not found.

    fcitx5-gtk4-immodule-probing not found.

  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.42 at /usr/bin/gtk-query-immodules-3.0.
      Version Line:

      # Created by /usr/bin/gtk-query-immodules-3.0 from gtk+-3.24.42
      

      Failed to find fcitx5 in the output of /usr/bin/gtk-query-immodules-3.0

      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.42 at /usr/lib64/gtk-3.0/3.0.0/immodules.cache.
      Version Line:

      # Created by /usr/bin/x86_64-pc-linux-gnu-gtk-query-immodules-3.0 from gtk+-3.24.42
      

      Failed to find fcitx5 in immodule cache at /usr/lib64/gtk-3.0/3.0.0/immodules.cache

      Cannot find fcitx5 im module for gtk 3 in cache.

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

      Classic User Interface 5.1.10
      Cloud Pinyin 5.1.6
      DBus 5.1.10
      DBus Frontend 5.1.10
      Emoji 5.1.10
      Input method selector 5.1.10
      Keyboard 5.1.10
      KDE Input Method Panel 5.1.10
      Status Notifier 5.1.10
      Notification 5.1.10
      Pinyin 5.1.6
      Extra Pinyin functionality 5.1.6
      Punctuation 5.1.6
      Unicode 5.1.10
      DBus Virtual Keyboard 5.1.10
      XCB 5.1.10
      X Input Method Frontend 5.1.10
      
    2. Found 8 disabled addons:

      Simplified and Traditional Chinese Translation 5.1.6
      Clipboard 5.1.10
      Fcitx4 Frontend 5.1.10
      Full width character 5.1.6
      IBus Frontend 5.1.10
      Quick Phrase 5.1.10
      Spell 5.1.10
      Table 5.1.6
      
  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:

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

Log:

  1. date:

    Sat Aug 10 20:27:43 CST 2024
    
  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.

@chikobara
Copy link

same issue here with fcitx5-qt4-immodule-probing not found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants