Bug 263696 - chinese/fcitx: Stop working with devel/dbus 1.14.0
Summary: chinese/fcitx: Stop working with devel/dbus 1.14.0
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks: dbus-1.14
  Show dependency tree / graph
 
Reported: 2022-05-01 00:31 UTC by Tomoaki AOKI
Modified: 2022-05-03 07:31 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomoaki AOKI 2022-05-01 00:31:04 UTC 
chinese/fcitx (at least in conjunction with japanese/fcitx-mozc) stops working with devel/dbus 1.14.0, updated by ports git: 692fe38479eb [1].

 *IME icon on Mate top panel doesn't appear at all.

 *IME panel doesn't show up on pressing Kanji key, thus cannot input
  Japanese text.

 *fcitx process is running according to `ps auxww | fgrep fitx`, but
  corresponding dbus-related processes (/usr/local/bin/fcitx-dbus-watcher
  and /usr/local/bin/dbus-daemon with --config-file /usr/local/share/fcitx
  /dbus/daemon.conf option) don't show up.

 *mozc_server processes are running as usual.

 *textproc/fcitx5 is not at all tested, as required (for me) fcitx5-mozc
  is not yet ported.


The above-mentioned commit is already reverted with ports git: f5a0f6f2041d, as xfce4 was reported to crash with it.

Now fcitx is working OK with dbus reverted, but would be broken again once xfce4 is fixed and devel/dbus is updated.

Please see also discussion on freebsd-ports ML starting at [3].

Note that at least x11/mate desktop is working fine (except IME) even if dbus is at 1.14.0. www/firefox, mail/sylpheed, editors/leafpad are also OK except IME.


[1] https://lists.freebsd.org/archives/dev-commits-ports-main/2022-April/022131.html

[2] https://lists.freebsd.org/archives/dev-commits-ports-main/2022-April/022309.html

[3] https://lists.freebsd.org/archives/freebsd-ports/2022-April/001809.html
Comment 1 Guido Falsi freebsd_committer freebsd_triage 2022-05-01 12:50:45 UTC 
I think I found the cause of the issues and filed a new update patch on bug 263014, could you test it and report back there?

Thanks!
Comment 2 Guido Falsi freebsd_committer freebsd_triage 2022-05-03 07:31:39 UTC 
Closing this as fixed with the commit of the corrected dbus 1.14 update as per
 bug #263014, comment #8