Bug#965264: fcitx: cannot switch to Chinese pinyin input by
pressing Ctrl+space
Message-Id: <20200730205622.24694f6abc16618144a76dec@126.com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,Aron :
I got the same problem after upgrated to the latest debian testing yesterday . I can't switch to Pinyin via Ctrl+Space . but I found it works well in WPS .
here is the msg via command `fcitx`:
$ (ERROR-7443 ime.c:432) fcitx-keyboard-in-tel-kagapa already exists
(ERROR-7443 ime.c:432) fcitx-keyboard-cm-mmuock already exists
here is the msg via command `fcitx-diagnose` :
# System Info:
1. `uname -a`:
Linux ZHZSX230 5.7.0-1-amd64 #1 SMP Debian 5.7.6-1 (2020-06-24) x86_64 GNU/Linux
2. `lsb_release -a`:
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux bullseye/sid
Release: testing
Codename: bullseye
3. `lsb_release -d`:
Description: Debian GNU/Linux bullseye/sid
4. `/etc/lsb-release`:
`/etc/lsb-release` not found.
5. `/etc/os-release`:
PRETTY_NAME="Debian GNU/Linux bullseye/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/";
SUPPORT_URL="https://www.debian.org/support";
BUG_REPORT_URL="https://bugs.debian.org/";
6. Desktop Environment:
Desktop environment is `xfce`.
7. Bash Version:
BASH_VERSION='5.0.16(1)-release'
# Environment:
1. DISPLAY:
DISPLAY=':0.0'
2. Keyboard Layout:
1. `setxkbmap`:
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+inet(evdev)" };
xkb_geometry { include "pc(pc105)" };
};
2. `xprop`:
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", ""
3. Locale:
1. All locale:
C
C.UTF-8
en_US.utf8
POSIX
zh_CN
zh_CN.gb18030
zh_CN.gb2312
zh_CN.gbk
zh_CN.utf8
2. Current locale:
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE=zh_CN.UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
4. Directories:
1. Home:
/home/zhz
2. `${XDG_CONFIG_HOME}`:
Environment variable `XDG_CONFIG_HOME` is not set.
Current value of `XDG_CONFIG_HOME` is `~/.config` (`/home/zhz/.config`).
3. Fcitx Settings Directory:
Current fcitx settings directory is `~/.config/fcitx` (`/home/zhz/.config/fcitx`).
5. Current user:
The script is run as zhz (1000).
# Fcitx State:
1. executable:
Found fcitx at `/usr/bin/fcitx`.
2. version:
Fcitx version: `4.2.9.7`
3. process:
Found 2 fcitx processes:
2023 fcitx
2040 fcitx-dbus-watc
4. `fcitx-remote`:
`fcitx-remote` works properly.
5. DBus interface:
Using `dbus-send` to check dbus.
Owner of DBus name `org.fcitx.Fcitx` is `:1.6`.
PID of DBus name `org.fcitx.Fcitx` owner is `2023`.
# Fcitx Configure UI:
1. Config Tool Wrapper:
Found fcitx-configtool at `/usr/bin/fcitx-configtool`.
2. Config GUI for gtk2:
Found `fcitx-config-gtk` at `/usr/bin/fcitx-config-gtk`.
3. Config GUI for gtk3:
**Config GUI for gtk3 not found.**
4. Config GUI for kde:
**`kcmshell4` not found.**
# Frontends setup:
## Xim:
1. `${XMODIFIERS}`:
Environment variable XMODIFIERS is set to "@im=fcitx" correctly.
Xim Server Name from Environment variable is fcitx.
2. XIM_SERVERS on root window:
Xim server name is the same with that set in the environment variable.
## Qt:
1. qt4 - `${QT4_IM_MODULE}`:
Environment variable QT4_IM_MODULE is set to "fcitx" correctly.
2. qt5 - `${QT_IM_MODULE}`:
Environment variable QT_IM_MODULE is set to "fcitx" correctly.
3. Qt IM module files:
Found fcitx im module for Qt5: `/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so`.
**Cannot find fcitx input method module for Qt4.**
## Gtk:
1. gtk - `${GTK_IM_MODULE}`:
Environment variable GTK_IM_MODULE is set to "fcitx" correctly.
2. `gtk-query-immodules`:
1. gtk 2:
**Cannot find `gtk-query-immodules` for gtk 2**
**Cannot find fcitx im module for gtk 2.**
2. gtk 3:
**Cannot find `gtk-query-immodules` for gtk 3**
**Cannot find fcitx im module for gtk 3.**
3. Gtk IM module cache:
1. gtk 2:
Found immodules cache for gtk `2.24.32` at `/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules.cache`.
Version Line:
# Created by /usr/lib/x86_64-linux-gnu/libgtk2.0-0/gtk-query-immodules-2.0 from gtk+-2.24.32
Found fcitx im modules for gtk `2.24.32`.
"/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-fcitx.so"
"fcitx" "Fcitx (Flexible Input Method Framework)" "fcitx" "/usr/share/locale" "ja:ko:zh:*"
2. gtk 3:
**Cannot find immodules cache for gtk 3**
**Cannot find fcitx im module for gtk 3 in cache.**
4. Gtk IM module files:
1. gtk 2:
All found Gtk 2 immodule files exist.
2. gtk 3:
All found Gtk 3 immodule files exist.
# Configuration:
## Fcitx Addons:
1. Addon Config Dir:
Found fcitx addon config directory: `/usr/share/fcitx/addon`.
2. Addon List:
1. Found 27 enabled addons:
fcitx-autoeng
fcitx-classic-ui
fcitx-clipboard
fcitx-dbus
fcitx-freedesktop-notify
fcitx-fullwidth-char
fcitx-googlepinyin
fcitx-imselector
fcitx-ipc
fcitx-keyboard
fcitx-kimpanel-ui
fcitx-lua
fcitx-notificationitem
fcitx-pinyin
fcitx-pinyin-enhance
fcitx-punc
fcitx-quickphrase
fcitx-remote
fcitx-spell
fcitx-sunpinyin
fcitx-table
fcitx-unicode
fcitx-vk
fcitx-x11
fcitx-xim
fcitx-xkb
fcitx-xkbdbus
2. Found 1 disabled addons:
fcitx-chttrans
3. Addon Libraries:
All libraries for all addons are found.
4. User Interface:
Found 2 enabled user interface addons:
fcitx-classic-ui
fcitx-kimpanel-ui
## Input Methods:
1. Found 8 enabled input methods:
fcitx-keyboard-us
sunpinyin
pinyin
shuangpin
fcitx-keyboard-cn-altgr-pinyin
googlepinyin
sogoupinyin
sogouwubi
2. Default input methods:
You have a keyboard input method "fcitx-keyboard-us" correctly added as your default input method.
# Log:
1. `date`:
Thu 30 Jul 2020 08:43:39 PM CST
2. `~/.config/fcitx/log/`:
total 4
-rw-r--r-- 1 zhz zhz 44 Mar 30 09:40 crash.log
3. `~/.config/fcitx/log/crash.log`:
fcitx: BadWindow (invalid Window parameter)
hope it helps to fix the problem.
Best ,
ZHZ
On Sun, 19 Jul 2020 14:23:12 +0800 Aron Xu <aron@debian.org> wrote:
> Hi,
>
> Would you mind to attach the output of `fcitx-diagnose` command?
>
> Best,
> Aron
>
>
--
zhz <zhuhuaizhong@126.com>
Reply to: