What steps will reproduce the problem?
1. startup computer
2. open any programm
3. trigger fcitx chinese input with ctrl-space
Since I updated to Kubuntu 13.10 (quite a time ago) fcitx doesn't work after
starting my computer. It runs and the symbol is available in system tray, as
well the menus can be opened und the pinyin input choosen, but there is no
input window starting. Fcitx first needs to get killed and started again. After
this it works just fine. This I have to do every time, after starting the
computer. It might have to do with dBus, but I am not shure.
What is the expected output? What do you see instead?
The trigger keys should start chinese input. Alternative: Choosing the input
method should start chinese input
What version of the product are you using? On what operating system?
4.2.8.1-3 Kubuntu 13.10 with Saucy backports and fcitx Saucy repository
Please provide any additional information below.
fcitx-diagnose shows (nothing about dbus):
$ LANG="zh_CN" fcitx-diagnose
# System Info:
1. `uname -a`:
Linux xxx 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
2. `lsb_release -a`:
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu 13.10
Release: 13.10
Codename: saucy
3. `lsb_release -d`:
Description: Ubuntu 13.10
4. `/etc/lsb-release`:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.10
DISTRIB_CODENAME=saucy
DISTRIB_DESCRIPTION="Ubuntu 13.10"
5. `/etc/os-release`:
NAME="Ubuntu"
VERSION="13.10, Saucy Salamander"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 13.10"
VERSION_ID="13.10"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
6. Desktop Environment:
Desktop environment is `kde`.
# Environment:
1. DISPLAY:
DISPLAY=':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(xxx)+inet(evdev)+level3(ralt_switch)" };
xkb_geometry { include "thinkpad(60)" };
};
2. `xprop`:
_XKB_RULES_NAMES(STRING) = "evdev", "thinkpadz60", "us", "xxx", "lv3:ralt_switch"
3. Locale:
1. All locale:
C
C.UTF-8
POSIX
de_AT.utf8
de_BE.utf8
de_CH.utf8
de_DE
de_DE.iso88591
de_DE.iso885915
de_DE.utf8
de_LI.utf8
de_LU.utf8
en_AG
en_AG.utf8
en_AU.utf8
en_BW.utf8
en_CA.utf8
en_DK.utf8
en_GB.utf8
en_HK.utf8
en_IE.utf8
en_IN
en_IN.utf8
en_NG
en_NG.utf8
en_NZ.utf8
en_PH.utf8
en_SG.utf8
en_US
en_US.iso88591
en_US.utf8
en_ZA.utf8
en_ZM
en_ZM.utf8
en_ZW.utf8
es_ES.iso885915
eu_ES.iso885915
eu_FR.iso885915
fr_FR.iso885915
it_IT.iso885915
pt_BR.iso885915
ru_RU.koi8r
sl_SI.iso885915
zh_CN.utf8
zh_SG.utf8
2. Current locale:
LANG=zh_CN
LANGUAGE=de:en_US:zh_CN:en
LC_CTYPE="zh_CN"
LC_NUMERIC="zh_CN"
LC_TIME="zh_CN"
LC_COLLATE="zh_CN"
LC_MONETARY="zh_CN"
LC_MESSAGES="zh_CN"
LC_PAPER="zh_CN"
LC_NAME="zh_CN"
LC_ADDRESS="zh_CN"
LC_TELEPHONE="zh_CN"
LC_MEASUREMENT="zh_CN"
LC_IDENTIFICATION="zh_CN"
LC_ALL=
**Error occurs when running `locale`. Please check your locale settings.**
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
# Fcitx State:
1. executable:
Found fcitx at `/usr/bin/fcitx`.
2. version:
Fcitx version: `4.2.8.1`
3. process:
Found 2 fcitx processes:
3062 fcitx
3077 fcitx-dbus-watc
4. `fcitx-remote`:
**Cannot connect to fcitx correctly.**
# 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:
Found `fcitx-config-gtk3` at `/usr/bin/fcitx-config-gtk3`.
4. Config GUI for kde:
Found fcitx kcm module.
kcm_fcitx - FCITX konfigurieren
# 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.
3. XIM encoding:
**Your LC_CTYPE is set to zh_CN whose encoding is not UTF-8. You may have trouble committing strings using XIM.**
## Qt:
1. `${QT_IM_MODULE}`:
Environment variable QT_IM_MODULE is set to "fcitx" correctly.
2. Qt IM module files:
Found fcitx im module for Qt4: `/usr/lib/x86_64-linux-gnu/qt4/plugins/inputmethods/qtim-fcitx.so`.
Found fcitx im module for Qt5: `/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so`.
## Gtk:
1. `${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.20` 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.20
Found fcitx im modules for gtk `2.24.20`.
"/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:*"
Found immodules cache for gtk `2.24.20` at `/usr/lib/i386-linux-gnu/gtk-2.0/2.10.0/immodules.cache`.
Version Line:
# Created by /usr/lib/i386-linux-gnu/libgtk2.0-0/gtk-query-immodules-2.0 from gtk+-2.24.20
**Failed to find fcitx in immodule cache at `/usr/lib/i386-linux-gnu/gtk-2.0/2.10.0/immodules.cache`**
2. gtk 3:
Found immodules cache for gtk `3.8.6` at `/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules.cache`.
Version Line:
# Created by /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 from gtk+-3.8.6
Found fcitx im modules for gtk `3.8.6`.
"/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-fcitx.so"
"fcitx" "Fcitx (Flexible Input Method Framework)" "fcitx" "/usr/share/locale" "ja:ko:zh:*"
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 19 enabled addons:
fcitx-autoeng
fcitx-chttrans
fcitx-classic-ui
fcitx-clipboard
fcitx-dbus
fcitx-freedesktop-notify
fcitx-fullwidth-char
fcitx-ipc
fcitx-keyboard
fcitx-notificationitem
fcitx-punc
fcitx-quickphrase
fcitx-spell
fcitx-sunpinyin
fcitx-unicode
fcitx-x11
fcitx-xim
fcitx-xkb
fcitx-xkbdbus
2. Found 8 disabled addons:
fcitx-anthy
fcitx-googlepinyin
fcitx-imselector
fcitx-light-ui
fcitx-pinyin-enhance
fcitx-pinyin
fcitx-remote
fcitx-vk
3. User Interface:
Found 1 enabled user interface addons:
fcitx-classic-ui
## Input Methods:
1. Found 2 enabled input methods:
fcitx-keyboard-us
sunpinyin
2. Default input methods:
You have a keyboard input method "fcitx-keyboard-us" correctly added as your default input method.
# Log:
1. `date`:
Fri Dec 6 12:16:38 CST 2013
2. `~/.config/fcitx/log/`:
total 4
-rw-rw-rw- 1 xxx xxx 44 Dec 6 11:20 crash.log
3. `~/.config/fcitx/log/crash.log`:
fcitx: BadWindow (invalid Window parameter)
Original issue reported on code.google.com by marwell....@googlemail.com on 6 Dec 2013 at 4:40
Original issue reported on code.google.com by
marwell....@googlemail.com
on 6 Dec 2013 at 4:40