fcitx5-remote (core dumped)

[zostj]

fcitx5 is an input method framework for foreign languages (Chinese, Japanese, Korean).
fcitx5-remote which is located in /usr/local/bin/fcitx5-remote is part of the package and a tool for controlling the fcitx state (switching between the foreign language input of your choice and english)

Now, fcitx5 works, but I noticed that when I explicitly try to run fcitx5-remote in the terminal or via VIM, it says:

Abort trap (core dumped)

and leaves a 11 MB file of the name: fcitx5-remote.core in the directory path where you executed the command.

For people that use fcitx5 input method in conjunction with Vim/Neovim, people often manually configure vim/neovim or use a fcitx plugin to automatically switch the state of fcitx via explicitly calling fcitx5-remote.

On linux, there's no issues but for some reason on FreeBSD, explicitly calling fcitx5-remote seems to create a core dump instead for some reason.

Anyone have any idea what might be causing this problem?

 

[yuripv79]

Just tried running it (though I have absolutely no idea how it should be called so I just did fcitx5-remote):

(gdb) bt
#0  thr_kill () at thr_kill.S:4
#1  0x00000008260813a4 in __raise (s=s@entry=6) at /usr/src/lib/libc/gen/raise.c:52
#2  0x0000000826132279 in abort () at /usr/src/lib/libc/stdlib/abort.c:67
#3  0x0000000823bd8d49 in report_failure (err=<optimized out>, thrown_exception=0x82b9c1000)
    at /usr/src/contrib/libcxxrt/exception.cc:714
#4  0x000000082412c56f in fcitx::dbus::Bus::Bus(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) () from /usr/local/lib/libFcitx5Utils.so.2
#5  0x000000082412c415 in fcitx::dbus::Bus::Bus(fcitx::dbus::BusType) () from /usr/local/lib/libFcitx5Utils.so.2
#6  0x0000000000203756 in ?? ()
#7  0x0000000826055d1b in __libc_start1 (argc=1, argv=0x8211842e8, env=0x8211842f8, cleanup=<optimized out>,
    mainX=0x203720) at /usr/src/lib/libc/csu/libc_start1.c:155
#8  0x0000000000203692 in ?? ()
#9  0x0000000000000000 in ?? ()

Now it really looks like a bad way to signal user that something is missing; it wants something about dbus, and I didn't have it running. So what I tried next is running per-user dbus daemon, e.g. dbus-launch --exit-with-session xterm, and running fcitx5-remote from that terminal seems to succeed (it printed 0). I am not sure how *you* should invoke the dbus daemon, but hopefully this helps.

EDIT: I don't think this should be in offtopic section, there is nothing offtopic about it.