如何让运行在宿主机 nixos 的 fcitx5 可以被运行在 distrobox podman 管理的 archlinux 容器中的图形软件感知到？ #990

I-Want-ToBelieve · 2024-03-17T11:50:07Z

I-Want-ToBelieve
Mar 17, 2024

How can I get the fcitx5 + rime input method running on the host (nixos) to be used in the GUI software of archlinux running in distrobox podman?

The Host：

Linux nixos 6.8.1 #1-NixOS SMP PREEMPT_DYNAMIC Fri Mar 15 18:19:29 UTC 2024 x86_64 GNU/Linux

❯ fcitx5-diagnose
# System Info:
1.  `uname -a`:

        Linux nixos 6.8.1 #1-NixOS SMP PREEMPT_DYNAMIC Fri Mar 15 18:19:29 UTC 2024 x86_64 GNU/Linux

2.  `lsb_release`:

    `lsb_release` not found.

3.  `/etc/lsb-release`:

        DISTRIB_CODENAME=uakari
        DISTRIB_DESCRIPTION="NixOS 24.05 (Uakari)"
        DISTRIB_ID=nixos
        DISTRIB_RELEASE="24.05"
        LSB_VERSION="24.05 (Uakari)"

4.  `/etc/os-release`:

        ANSI_COLOR="1;34"
        BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
        BUILD_ID="24.05.20240317.ccc0632"
        DOCUMENTATION_URL="https://nixos.org/learn.html"
        HOME_URL="https://nixos.org/"
        ID=nixos
        IMAGE_ID=""
        IMAGE_VERSION=""
        LOGO="nix-snowflake"
        NAME=NixOS
        PRETTY_NAME="NixOS 24.05 (Uakari)"
        SUPPORT_URL="https://nixos.org/community.html"
        VERSION="24.05 (Uakari)"
        VERSION_CODENAME=uakari
        VERSION_ID="24.05"

5.  Desktop Environment:

    Desktop environment is `kde`.

6.  XDG SESSION TYPE:

        XDG_SESSION_TYPE='wayland'

7.  Bash Version:

        BASH_VERSION='5.2.26(1)-release'

# Environment:
1.  DISPLAY:

        DISPLAY=':1'


        WAYLAND_DISPLAY='no'

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)+capslock(swapescape)+terminate(ctrl_alt_bksp)"	};
            	xkb_geometry  { include "pc(pc105)"	};
            };

    2.  `xprop`:

            _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", "terminate:ctrl_alt_bksp,caps:swapescape"

3.  Locale:

    1.  All locales:

            C
            en_US.utf8
            POSIX
            zh_CN.utf8

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

4.  Directories:

    1.  Home:

            /home/i.want.to.believe

    2.  `${XDG_CONFIG_HOME}`:

        Environment variable `XDG_CONFIG_HOME` is set to `/home/i.want.to.believe/.config`.

        Current value of `XDG_CONFIG_HOME` is `~/.config` (`/home/i.want.to.believe/.config`).

    3.  Fcitx5 Settings Directory:

        Current fcitx5 settings directory is `~/.config/fcitx5` (`/home/i.want.to.believe/.config/fcitx5`).

5.  Current user:

    The script is run as i.want.to.believe (1000).

# Fcitx State:
1.  executable:

    Found fcitx5 at `/run/current-system/sw/bin/fcitx5`.

2.  version:

    Fcitx version: `5.1.8`

3.  process:

    Found 2 fcitx5 processes:

          17164 .fcitx5-wrapped
          18790 fcitx5-diagnose

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.186`.

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

    Debug information from dbus:

           Group [wayland:] has 12 InputContext(s)
          IC [2634b8eab97240318c797e3aee57fa40] program:firefox frontend:dbus cap:6001000032 focus:0
          IC [67ab8ecf913a45bbb096e25c4bb33e3d] program:firefox frontend:wayland cap:72 focus:0
          IC [a16d18916f7741018d4fb0d49f221c3d] program:firefox frontend:dbus cap:6001000032 focus:0
          IC [b9e62a3875a24c83a3ec60ddad17bb7d] program:firefox frontend:dbus cap:e001000072 focus:0
          IC [45bec8fa4406455e8aaba12019cc4e2d] program:.plasmashell-wrapped frontend:dbus cap:1e001800072 focus:0
          IC [acab46112615466a95c720aee5e3300c] program:tdrop_terminal frontend:wayland cap:72 focus:0
          IC [4082f4d1b9874bd3a90ec009f178654f] program:.krunner-wrapped frontend:dbus cap:e001820072 focus:0
          IC [5cb1cb3325f04019ae09ea600e1f54a3] program:.plasmashell-wrapped frontend:dbus cap:1e001800072 focus:0
          IC [272d619690d04d099e544f0cad02d642] program:.plasmashell-wrapped frontend:dbus cap:1e001800072 focus:0
          IC [bc9ca45784734837b7f08bea937b9454] program:org.kde.plasmashell frontend:wayland cap:72 focus:0
          IC [7bf4b32414bd4ff6977a9e5f15add751] program:firefox frontend:dbus cap:6001000032 focus:0
          IC [3dcbbf26b3964eb3a9cd3806927bf46d] program: frontend:wayland cap:72 focus:0
        Group [x11::1] has 1 InputContext(s)
          IC [df57e6d82eb347e58c9f2f095d181f3f] program:.copyq-wrapped frontend:dbus cap:6000800072 focus:0
        Input Context without group

# Fcitx Configure UI:
1.  Config Tool Wrapper:

    Found fcitx5-configtool at `/run/current-system/sw/bin/fcitx5-configtool`.

2.  Config GUI for qt:

    Found `fcitx5-config-qt` at `/run/current-system/sw/bin/fcitx5-config-qt`.

3.  Config GUI for kde:

# 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=xcb
        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=xcb
        QT_IM_MODULE=fcitx
        IM_MODULE_CLASSNAME=fcitx::QFcitxPlatformInputContext

4.  Qt IM module files:

    Found unknown fcitx qt module: `./.local/share/containers/storage/overlay/c6456e52eb24fb1fa74f926e5b77f18a275bb339a0869762bf88f83358e512e8/diff/usr/lib/office6/qt/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so`.
    Found unknown fcitx qt module: `./distrobox/archlinux/.cache/paru/clone/wps-office-cn/src/opt/kingsoft/wps-office/office6/qt/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.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.**
    **Cannot find fcitx5 input method module for Qt6.**

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

        **Cannot find immodules cache for gtk 3**

        **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: `/nix/store/xsinp0rmgrbv4zvgr1ysdsyp9q7p630g-fcitx5-5.1.8/share/fcitx5/addon`.

2.  Addon List:

    1.  Found 20 enabled addons:

            Classic User Interface 5.1.8
            Clipboard 5.1.8
            DBus 5.1.8
            DBus Frontend 5.1.8
            Emoji 5.1.8
            Fcitx4 Frontend 5.1.8
            IBus Frontend 5.1.8
            Input method selector 5.1.8
            Keyboard 5.1.8
            KDE Input Method Panel 5.1.8
            Status Notifier 5.1.8
            Notification 5.1.8
            Quick Phrase 5.1.8
            Spell 5.1.8
            Unicode 5.1.8
            DBus Virtual Keyboard 5.1.8
            Wayland 5.1.8
            Wayland Input method frontend 5.1.8
            XCB 5.1.8
            X Input Method Frontend 5.1.8

    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/i.want.to.believe/.config/fcitx5/profile`:

        [Groups/0]
        # Group Name
        Name=Default
        # Layout
        Default Layout=us
        # Default Input Method
        DefaultIM=rime

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

        [Groups/0/Items/1]
        # Name
        Name=rime
        # Layout
        Layout=

        [Groups/0/Items/2]
        # Name
        Name=pinyin
        # Layout
        Layout=

        [GroupOrder]
        0=Default

# Log:
1.  `date`:

        Sun Mar 17 07:49:48 PM CST 2024

2.  `/home/i.want.to.believe/.config/fcitx5/crash.log`:

    `/home/i.want.to.believe/.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.**

Answered by karuboniru

Mar 18, 2024

他们是走的 session dbus 通信的，你把 session bus 挂进去/用xdg-dbus-proxy代理进去就行了

View full answer

I-Want-ToBelieve · 2024-03-18T10:26:17Z

I-Want-ToBelieve
Mar 18, 2024
Author

现在我通过在 archlinux 容器中启动另外一个独立于宿主机的 fcitx5 守护进程来达到在 archlinux 容器中的图形软件中输入中文的目的。
现在的问题是我有两套输入法，nixos 宿主机一套，archlinux 容器中一套。

如果容器中的软件能直接与宿主机的 fcitx5 通信，那就真的太好了！

0 replies

karuboniru · 2024-03-18T12:47:30Z

karuboniru
Mar 18, 2024

他们是走的 session dbus 通信的，你把 session bus 挂进去/用xdg-dbus-proxy代理进去就行了

3 replies

I-Want-ToBelieve Mar 18, 2024
Author

感谢大哥的提示，我做到了！

在 archlinux 容器中：

export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/host/run/user/1000/bus && notify-send "hello host"

I-Want-ToBelieve Mar 18, 2024
Author

感谢您的回答，使我的 CPU 旋转，爱来自德清。

iHad168 Jul 27, 2024

感謝大哥的提示，我做到了！

在 archlinux 容器中：
export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/host/run/user/1000/bus && notify-send "hello host"

Thank you

wengxt · 2024-03-18T19:29:27Z

wengxt
Mar 18, 2024
Maintainer

你可以用 DBus 或者 display server 的协议，但是你需要设置对应的环境变量来指定

具体还得看你运行程序的种类

1 reply

I-Want-ToBelieve Mar 19, 2024
Author

意思是如果是 wayland 的话应该就不用传 DBus 了吧，传 /run/user/1000/wayland-0 进去对吗

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

如何让运行在宿主机 nixos 的 fcitx5 可以被运行在 distrobox podman 管理的 archlinux 容器中的图形软件感知到？ #990

{{title}}

Replies: 3 comments 4 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

如何让运行在宿主机 nixos 的 fcitx5 可以被运行在 distrobox podman 管理的 archlinux 容器中的图形软件感知到？ #990

I-Want-ToBelieve Mar 17, 2024

Replies: 3 comments · 4 replies

I-Want-ToBelieve Mar 18, 2024 Author

karuboniru Mar 18, 2024

I-Want-ToBelieve Mar 18, 2024 Author

I-Want-ToBelieve Mar 18, 2024 Author

iHad168 Jul 27, 2024

wengxt Mar 18, 2024 Maintainer

I-Want-ToBelieve Mar 19, 2024 Author

I-Want-ToBelieve
Mar 17, 2024

Replies: 3 comments 4 replies

I-Want-ToBelieve
Mar 18, 2024
Author

karuboniru
Mar 18, 2024

I-Want-ToBelieve Mar 18, 2024
Author

I-Want-ToBelieve Mar 18, 2024
Author

wengxt
Mar 18, 2024
Maintainer

I-Want-ToBelieve Mar 19, 2024
Author