Bug 263696

Summary:	chinese/fcitx: Stop working with devel/dbus 1.14.0
Product:	Ports & Packages	Reporter:	Tomoaki AOKI <junchoon>
Component:	Individual Port(s)	Assignee:	freebsd-ports-bugs (Nobody) <ports-bugs>
Status:	Closed FIXED
Severity:	Affects Only Me	CC:	desktop, lichray, madpilot
Priority:	---
Version:	Latest
Hardware:	Any
OS:	Any
See Also:	https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263014
Bug Depends on:
Bug Blocks:	263014

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

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

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