Bug 222418 - chinese/fcitx tray menu no longer works
Summary: chinese/fcitx tray menu no longer works
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: Walter Schwarzenfeld
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-18 02:18 UTC by Ian Trudel
Modified: 2019-08-14 10:51 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (lichray)


Attachments
fcitx diagnose output (11.62 KB, text/plain)
2017-09-18 02:18 UTC, Ian Trudel
no flags Details
ps -ax (4.99 KB, text/plain)
2017-09-18 10:00 UTC, Ian Trudel
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Trudel 2017-09-18 02:18:09 UTC
Created attachment 186497 [details]
fcitx diagnose output

A couple of months ago I had installed FreeBSD, all packages were binary packages installed via pkg and fcitx was working just fine.

Now I have two machines and everything is compiled through ports. Fcitx works on both machine as far as input (Dvorak, Chinese, Korean and Russian) goes but it will freeze if I right click on the tray icon. The menu is not displayed. There might be something interfering.

Also, please be noted that installing zh-fcitx binary package will require to deinstall Krita. Uh? This is not making any sense.

You shall find fcitx-diagnose output for your convenience.

Any idea?
Comment 1 lichray 2017-09-18 05:41:29 UTC
(In reply to Ian Trudel from comment #0)
Does this happens to all/some combinations of enabled input methods or having a curtain input method enabled?  Can you try to kick all input methods out of configuration and then add them back?

Because Krita uses qt5 while fcitx4 uses Qt4, maybe?
Comment 2 Ian Trudel 2017-09-18 08:49:51 UTC
(In reply to lichray from comment #1)
I removed all input as you suggested, even removed ~/.config/fcitx to see if that would help, but neither make any difference.

The tray tooltip actually display the current input method. Left clicking does change the input method. The right click on fcitx tray icon will freeze the whole system for some 20-30 seconds. It means I cannot switch windows, click anywhere, type anything but the mouse pointer is still moving and there are still screen updates.

Is there any log to look at or some way to gdb the thing?

RE: Krita
Krita is installed on one machine but not the other.


pkg info | grep fcitx
fcitx-qt5-1.1.0_2              Fcitx support for Qt5
ko-fcitx-hangul-0.3.0          Hangul support for Fcitx
zh-fcitx-4.2.9.1_4             Flexible Input Method Framework
zh-fcitx-configtool-0.4.8      Fcitx IM framework configuration tool
zh-fcitx-sunpinyin-0.4.1       SunPinyin support for Fcitx

(The second machine does not have fcitx-qt5)
Comment 3 lichray 2017-09-18 09:39:40 UTC
(In reply to Ian Trudel from comment #2)

I need more information (before handling it to upstream).  Which desktop you are using?  Which tray application you are running?  Did you activated any fcitx UI plugin (classic or kimpanel)?

Hmm, pkg doesn't say that zh-fcitx and kirita conflicts here.  Did you build one of their dependencies through ports?  Maybe there are some library version conflicts.
Comment 4 Ian Trudel 2017-09-18 10:00:02 UTC
Created attachment 186506 [details]
ps -ax
Comment 5 Ian Trudel 2017-09-18 10:01:00 UTC
(In reply to lichray from comment #3)

MATE Desktop. Using default config in fcitx + four keyboard layouts (dvorak intl+dead keys, sunpinyin, hangul, Russian).

Attached the output of ps -ax to help you know what's going on.

RE: krita
It's possible that some dependencies are crossing over. Not sure how to find out besides looking at every dependency one by one.
Comment 6 Ian Trudel 2017-09-18 12:14:18 UTC
A small update:

I installed a virtual machine with the official FreeBSD vm image then installed binary packages for xorg, mate, fcitx and krita. It works just fine.

Now the problem is that I've got two different machines with the same problem. The machines have some similarities, some differences. You may however be right that there is a dependency down the line that interferes with fcitx.

By the way, fcitx configuration has a tabbed UI on both machines but is visually different (panes instead of tabs) from binary package on the VM. 

I will attempt to find out how to reliably reproduce the problem so that you can also test. Meanwhile, if you have further questions or things for me to try on, let me know. Perhaps you will find something on your side anyway.
Comment 7 Ian Trudel 2017-09-19 10:47:01 UTC
Recompiling fcitx and all its dependencies on the VM did not trigger the issue. I had used portmaster -f chinese/fcitx and individual ports configuration similar to what I am using on both machines. Still haven't found the source of interference.
Comment 8 Ian Trudel 2017-09-22 05:45:40 UTC
Hi Zhihao,

I'm getting closer and determined that something in my make.conf is causing the issue. Rebuilt the whole thing (xorg, mate, fcitx, etc) with a make.conf similar to the two other machines. Not quite sure which one is the culprit though. I suspect building static or no profile might cause some troubles. Any thoughts?

cat /etc/make.conf
DEFAULT_VERSIONS+= linux=c7 python=2.7 python2=2.7 #python3=2.7
#RANDOMIZE_MASTER_SITES=YES
MAKE_JOBS_NUMBER?=6
MAKEOPTS=-j5
BATCH=YES            # for testing purpose

COPTFLAGS= -O3 -pipe -funroll-loops
CFLAGS+= -O3 -pipe # -fno-strict-aliasing
CXXFLAGS+= -O3 -pipe

BUILD_OPTIMIZED=YES
BUILD_STATIC=YES

WITHOUT_DEBUG=YES
MK_PROFILE=no

QT_SELECT=qt5

# IT170914: living dangerously
DISABLE_VULNERABILITIES=yes
NO_INET6=YES
Comment 9 Ian Trudel 2017-09-26 21:45:29 UTC
Recompiled one machine without COPTFLAGS, CFLAGS, CXXFLAGS. Right clicking on the icon in the tray bar, the menu now shows up most of the time but not always. It is also particularly slow to show up (up to a minute).
Comment 10 lichray 2017-09-28 17:58:26 UTC
Upstream fix in progress: https://github.com/mate-desktop/mate-panel/issues/662
Comment 11 Ian Trudel 2017-09-28 18:02:31 UTC
(In reply to lichray from comment #10)

Thanks for the update.
Comment 12 Walter Schwarzenfeld freebsd_triage 2018-11-16 05:22:33 UTC
We have version 1.2.3,1. Is this still relevant?