https://bugzilla.redhat.com/show_bug.cgi?id=1473715
--- Comment #25 from agents(a)meddatainc.com ---
This was not an upgrade but an installation on a new computer, hence I did not
access epel-release. This is what rpm -qa reports:
rpm -qa | grep fcitx
fcitx-pinyin-4.2.9.6-1.el7.x86_64
fcitx-data-4.2.9.6-1.el7.noarch
fcitx-table-4.2.9.6-1.el7.x86_64
fcitx-configtool-0.4.10-1.el7.x86_64
fcitx-4.2.9.6-1.el7.x86_64
fcitx-qt5-1.2.3-10.el7.x86_64
fcitx-gtk3-4.2.9.6-1.el7.x86_64
fcitx-qt4-4.2.9.6-1.el7.x86_64
fcitx-libs-4.2.9.6-1.el7.x86_64
fcitx-table-chinese-4.2.9.6-1.el7.noarch
fcitx-gtk2-4.2.9.6-1.el7.x86_64
Yet when I run fcitx-diagnose it reports fcitx 4.2.9.5? Unless I have made any
errors installing, I still have the same issue I reported earlier, ie choosing
another keyboard using the MATE keyboard switcher does not stick even in one
single application such as firefox, chromium. Hitting TAB in Firefox entry
fields switches me back to the default keyboard (I use RIGHT-CTRL+RIGHT-SHIFT
to switch among keyboards (two western ones and a Chinese keyboard layout),
CTRL-SPACE to switch between Pinyin and non-Pinyin. The Pinyin/non-Pinyin seems
to stick though between apps whereas switching the keyboard layout using the
RIGHT-CTRL+RIGHT-SHIFT switches back to the default keyboard when hitting ENTER
in chromium but remains when hitting ENTER in Firefox. Switching between
different entry fields in either switches me back to the default keyboard in
both apps.
So, to make a long story short, there might be two issues:
- fcitx-diagnose seems to reports fcitx 4.2.9.5 even though 4.2.9.6 is
installed. Can you confirm this?
- using the keyboard layout switcher in MATE does not seem to work as expected
in chromium and firefox (only apps I tried now) whereas it does seem to work
when switching between MATE terminals. Just tried firefox as well and Pinyin
switching seems OK here as well whereas keyboard layout switching using the
other keyboard combo gets lost when switching between different entry fields
etc.
--
You are receiving this mail because:
You are on the CC list for the bug.