You are not logged in.

Pages: 1

#1 2023-11-07 19:09:20

qsqcqs
Member
Registered: 2023-11-07
Posts: 18

GTK_IM_MODULE and others not set to fcitx despite ~/.xprofile [SOLVED]

fcitx5-diagnose returns that (below) despite the contents of my xprofile being 

export XIM_PROGRAM=fcitx
export XIM=fcitx
export GTK_IM_MODULE=fcitx
export QT_IM_MODULE=fcitx
export XMODIFIERS="@im=fcitx"
# System Info:
1.  `uname -a`:

        Linux archlinux 6.5.9-arch2-1 #1 SMP PREEMPT_DYNAMIC Thu, 26 Oct 2023 00:52:20 +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://bugs.archlinux.org/"
        PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
        LOGO=archlinux-logo

6.  Desktop Environment:

    Desktop environment is `kde`.

7.  XDG SESSION TYPE:

        XDG_SESSION_TYPE='wayland'

8.  Bash Version:

        BASH_VERSION='5.2.15(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+cn+inet(evdev)+terminate(ctrl_alt_bksp)"    };
                xkb_geometry  { include "pc(pc105)"     };
            };

    2.  `xprop`:

            _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "cn", "", "terminate:ctrl_alt_bksp"

3.  Locale:

    1.  All locales:

            C
            C.utf8
            en_US.utf8
            POSIX

    2.  Current locale:

            LANG=en_US.UTF-8
            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_IE.UTF-8
            LC_IDENTIFICATION="en_US.UTF-8"
            LC_ALL=

        **Error occurs when running `locale`. Please check your locale settings.**

            locale: Cannot set LC_ALL to default locale: No such file or directory

4.  Directories:

    1.  Home:

            /home/qsqcqs

    2.  `${XDG_CONFIG_HOME}`:

        Environment variable `XDG_CONFIG_HOME` is not set.

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

    3.  Fcitx5 Settings Directory:

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

5.  Current user:

    The script is run as qsqcqs (1000).

# Fcitx State:
1.  executable:

    Found fcitx5 at `/usr/bin/fcitx5`.

2.  version:

    Fcitx version: `5.1.4`

3.  process:

    Found 1 fcitx5 process:

            786 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.17`.

    PID of DBus name `org.fcitx.Fcitx5` owner is `786`.

    Debug information from dbus:

           Group [x11::1] has 0 InputContext(s)
        Group [wayland:] has 11 InputContext(s)
          IC [748021d3ebd44ee6bd32630163dd3906] program:org.kde.konsole frontend:wayland cap:52 focus:1
          IC [cc204001fa8c404fa97791231725c0cd] program:firefox frontend:wayland cap:80052 focus:0
          IC [9b321a80a8924108bc5bb437e15fa52b] program: frontend:ibus cap:12 focus:0
          IC [fd07ad1684474a06a958f658f9fdb913] program:firefox frontend:wayland cap:80052 focus:0
          IC [00ac3be8dc2444838bd4d1ab8fab2b8c] program: frontend:ibus cap:12 focus:0
          IC [fc6ce44aa9034a69a13d0e7cdd3a6ddd] program: frontend:ibus cap:12 focus:0
          IC [176eabf10799420798cbcc2c95b2bf8c] program: frontend:ibus cap:12 focus:0
          IC [56d0ae4554d748ef917d09ae45927d4c] program: frontend:ibus cap:12 focus:0
          IC [bf54c819dd8e4764bcc535be17d860ff] program: frontend:ibus cap:12 focus:0
          IC [722daf9fa0d74fd48451a98008b8e8d1] program:org.kde.plasmashell frontend:wayland cap:52 focus:0
          IC [b2d018f0f2fe4062ab299636eb74245e] program: frontend:wayland cap:52 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:

    Found fcitx5 kcm module.

        kcm_fcitx5                     - Configure Input Method

# 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}`:

    **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]([url]http://fcitx-im.org/wiki/Input_method_related_environment_variables#XMODIFIERS[/url]).**
    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}`:

    **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]([url]http://fcitx-im.org/wiki/Input_method_related_environment_variables#QT_IM_MODULE[/url]).**

    **`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]([url]http://fcitx-im.org/wiki/Input_method_related_environment_variables#QT_IM_MODULE[/url]).**

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

        QT_QPA_PLATFORM=wayland
        QT_IM_MODULE=
        IM_MODULE_CLASSNAME=QtWaylandClient::QWaylandInputContext

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]([url]http://fcitx-im.org/wiki/Input_method_related_environment_variables#QT_IM_MODULE[/url]).**

    **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_QPA_PLATFORM=xcb
        QT_IM_MODULE=
        IM_MODULE_CLASSNAME=QComposeInputContext

4.  Qt IM module files:

    Found fcitx5 im module for qt6: `/usr/lib/qt6/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so`.
    Found fcitx5 qt5 module: `/usr/lib/fcitx5/qt5/libfcitx-quickphrase-editor5.so`.
    Found fcitx5 im module for qt: `/usr/lib/qt/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so`.
    Found unknown fcitx qt module: `/usr/lib/qt/plugins/kcms/kcm_fcitx5.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]([url]http://fcitx-im.org/wiki/Input_method_related_environment_variables#GTK_IM_MODULE[/url]).**

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

        GTK_IM_MODULE=ibus

    Using fcitx5-gtk3-immodule-probing to check the actual im module to be used under current environment:

        GTK_IM_MODULE=wayland

    Using fcitx5-gtk4-immodule-probing to check the actual im module to be used under current environment:

        GTK_IM_MODULE=wayland

2.  `gtk-query-immodules`:

    1.  gtk 2:

        Found `gtk-query-immodules` for gtk `2.24.33` at `/usr/bin/gtk-query-immodules-2.0`.
        Version Line:

            # Created by /usr/bin/gtk-query-immodules-2.0 from gtk+-2.24.33

        Found fcitx5 im modules for gtk `2.24.33`.

            "/usr/lib/gtk-2.0/2.10.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:*" 

    2.  gtk 3:

        Found `gtk-query-immodules` for gtk `3.24.38` at `/usr/bin/gtk-query-immodules-3.0`.
        Version Line:

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

        Found fcitx5 im modules for gtk `3.24.38`.

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

        Found immodules cache for gtk `2.24.33` at `/usr/lib/gtk-2.0/2.10.0/immodules.cache`.
        Version Line:

            # Created by /usr/bin/gtk-query-immodules-2.0 from gtk+-2.24.33

        Found fcitx5 im modules for gtk `2.24.33`.

            "/usr/lib/gtk-2.0/2.10.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:*" 

    2.  gtk 3:

        Found immodules cache for gtk `3.24.38` 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.38

        Found fcitx5 im modules for gtk `3.24.38`.

            "/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 23 enabled addons:

            Classic User Interface 5.1.4
            Clipboard 5.1.4
            DBus 5.1.4
            DBus Frontend 5.1.4
            Emoji 5.1.4
            Fcitx4 Frontend 5.1.4
            IBus Frontend 5.1.4
            Lua IME API 5.0.11
            Input method selector 5.1.4
            Keyboard 5.1.4
            KDE Input Method Panel 5.1.4
            Lua Addon Loader 5.0.11
            Status Notifier 5.1.4
            Notification 5.1.4
            Quick Phrase 5.1.4
            Rime 5.1.3
            Spell 5.1.4
            Unicode 5.1.4
            DBus Virtual Keyboard 5.1.4
            Wayland 5.1.4
            Wayland Input method frontend 5.1.4
            XCB 5.1.4
            X Input Method Frontend 5.1.4

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

        [Groups/0]
        # Group Name
        Name="Group 1"
        # Layout
        Default Layout=cn
        # Default Input Method
        DefaultIM=keyboard-cn-altgr-pinyin

        [Groups/0/Items/0]
        # Name
        Name=keyboard-cn
        # Layout
        Layout=

        [Groups/0/Items/1]
        # Name
        Name=keyboard-gb
        # Layout
        Layout=

        [Groups/0/Items/2]
        # Name
        Name=keyboard-cn-altgr-pinyin
        # Layout
        Layout=

        [GroupOrder]
        0="Group 1"

# Log:
1.  `date`:

        Tue Nov  7 10:56:46 PST 2023

2.  `/home/qsqcqs/.config/fcitx5/crash.log`:

    `/home/qsqcqs/.config/fcitx5/crash.log` not found.

Last edited by qsqcqs (2023-11-12 07:53:39)

Offline

#2 2023-11-07 19:44:00

qsqcqs
Member
Registered: 2023-11-07
Posts: 18

Re: GTK_IM_MODULE and others not set to fcitx despite ~/.xprofile [SOLVED]

I forgot to mention this above but I am running KDE plasma using wayland

Offline

#3 2023-11-07 20:42:51

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,070

Re: GTK_IM_MODULE and others not set to fcitx despite ~/.xprofile [SOLVED]

Please use [code][/code] tags. Edit your post in this regard.

Does fcitx5 work with plasma on X11?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#4 2023-11-07 20:46:01

qsqcqs
Member
Registered: 2023-11-07
Posts: 18

Re: GTK_IM_MODULE and others not set to fcitx despite ~/.xprofile [SOLVED]

no, virtual keyboard doesn't show up when using it for some reason

Offline

#5 2023-11-07 21:49:14

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,070

Re: GTK_IM_MODULE and others not set to fcitx despite ~/.xprofile [SOLVED]

Please fix your post with code tags, I'll not ask again.

Your xprofile is most likely not source, what's normal depending on how you login.

loginctl session-status

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#6 2023-11-08 00:33:42

qsqcqs
Member
Registered: 2023-11-07
Posts: 18

Re: GTK_IM_MODULE and others not set to fcitx despite ~/.xprofile [SOLVED]

mb, where would source be for sddm?

Offline

#7 2023-11-08 03:44:46

qsqcqs
Member
Registered: 2023-11-07
Posts: 18

Re: GTK_IM_MODULE and others not set to fcitx despite ~/.xprofile [SOLVED]

loginctl system-status

returns 

2 - qsqcqs (1000)
           Since: Tue 2023-11-07 19:19:57 PST; 23min ago
          Leader: 610 (sddm-helper)
            Seat: seat0; vc1
             TTY: tty1
         Service: sddm; type wayland; class user
         Desktop: KDE
           State: active
            Idle: no
            Unit: session-2.scope
                  ├─610 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-auth-feaa6d78-e197-4abe-9f76-188c0275
c515 --id 1 --start "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" --user qsqcqs
                  ├─645 /usr/bin/kwalletd5 --pam-login 12 14
                  └─646 /usr/bin/startplasma-wayland

Nov 07 19:19:57 archlinux systemd[1]: Started Session 2 of User qsqcqs.
Nov 07 19:19:57 archlinux sddm-helper[644]: pam_kwallet5: final socket path: /run/us
er/1000/kwallet5.socket
Nov 07 19:19:57 archlinux sddm-helper[646]: Jumping to VT 1
Nov 07 19:19:57 archlinux sddm-helper[646]: VT mode didn't need to be fixed

Offline

#8 2023-11-08 07:34:57

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,070

Re: GTK_IM_MODULE and others not set to fcitx despite ~/.xprofile [SOLVED]

That's (still) a  wayland session (again) and .xprofile is certainly not going to be sourced for that.
You can set the environment for the greeter: https://wiki.archlinux.org/title/SDDM#Enable_HiDPI
For your plasma session specifically: https://wiki.archlinux.org/title/KDE#Autostart
Generally https://wiki.archlinux.org/title/Environment_variables - I'd try ~/.profile

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

Pages: 1

Board footer

Powered by FluxBB