fcitx input method does not work on Xubuntu 16.04 - Ask Ubuntu
i'm using xubuntu 16.04. although active fcitx input method (unikey , hangul), not works application.
here fcitx-diagnose
# system info: 1. `uname -a`: linux 4.4.0-45-generic #66-ubuntu smp wed oct 19 14:12:37 utc 2016 x86_64 x86_64 x86_64 gnu/linux 2. `lsb_release -a`: no lsb modules available. distributor id: ubuntu description: ubuntu 16.04 lts release: 16.04 codename: xenial 3. `lsb_release -d`: description: ubuntu 16.04 lts 4. `/etc/lsb-release`: distrib_id=ubuntu distrib_release=16.04 distrib_codename=xenial distrib_description="ubuntu 16.04 lts" 5. `/etc/os-release`: name="ubuntu" version="16.04 lts (xenial xerus)" id=ubuntu id_like=debian pretty_name="ubuntu 16.04 lts" version_id="16.04" home_url="http://www.ubuntu.com/" support_url="http://help.ubuntu.com/" bug_report_url="http://bugs.launchpad.net/ubuntu/" ubuntu_codename=xenial 6. desktop environment: desktop environment `xfce`. 7. bash version: bash_version='4.3.42(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. locale: c c.utf-8 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.utf8 en_za.utf8 en_zm en_zm.utf8 en_zw.utf8 ko_kr.utf8 posix 2. current locale: lang=en_us.utf-8 language=en_us lc_ctype="en_us.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/trongkha 2. `${xdg_config_home}`: environment variable `xdg_config_home` not set. current value of `xdg_config_home` `~/.config` (`/home/trongkha/.config`). 3. fcitx settings directory: current fcitx settings directory `~/.config/fcitx` (`/home/trongkha/.config/fcitx`). 5. current user: script run trongkha (1000). # fcitx state: 1. executable: found fcitx @ `/usr/bin/fcitx`. 2. version: fcitx version: `4.2.9.1` 3. process: found 3 fcitx processes: 19239 fcitx 24544 fcitx 25691 fcitx-dbus-watc 4. `fcitx-remote`: `fcitx-remote` works properly. # fcitx configure ui: 1. config tool wrapper: found fcitx-configtool @ `/usr/bin/fcitx-configtool`. 2. config gui gtk2: **config gui gtk2 not found.** 3. config gui gtk3: found `fcitx-config-gtk3` @ `/usr/bin/fcitx-config-gtk3`. 4. config gui kde: **`kcmshell4` not found.** # frontends setup: ## xim: 1. `${xmodifiers}`: **xmodifiers not set** **please set environment variable xmodifiers "@im=fcitx" using tool distribution provides or add `export xmodifiers=@im=fcitx` `~/.xprofile`. see [input method related environment variables: xmodifiers](http://fcitx-im.org/wiki/input_method_related_environment_variables#xmodifiers).** xim server name environment variable fcitx. 2. xim_servers on root window: xim server name same set in environment variable. ## qt: 1. qt4 - `${qt4_im_module}`: **please set environment variable qt_im_module "fcitx" using tool distribution provides or add `export qt_im_module=fcitx` `~/.xprofile`. see [input method related environment variables: qt_im_module](http://fcitx-im.org/wiki/input_method_related_environment_variables#qt_im_module).** 2. qt5 - `${qt_im_module}`: **please set environment variable qt_im_module "fcitx" using tool distribution provides or add `export qt_im_module=fcitx` `~/.xprofile`. see [input method related environment variables: qt_im_module](http://fcitx-im.org/wiki/input_method_related_environment_variables#qt_im_module).** 3. qt im module files: found fcitx im module qt4: `/usr/lib/x86_64-linux-gnu/qt4/plugins/inputmethods/qtim-fcitx.so`. found fcitx im module qt5: `/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libfcitxplatforminputcontextplugin.so`. ## gtk: 1. gtk - `${gtk_im_module}`: **environment variable gtk_im_module "xim" instead of "fcitx". please check if have exported incorrectly in of init files.** **you using xim in gtk programs.** **to see application specific problems may have when using xim, check [hall of shame linux ime support](http://fcitx-im.org/wiki/hall_of_shame_for_linux_ime_support). other more general problems of using xim including application freezing, see [here](http://fcitx-im.org/wiki/xim).** **please set environment variable gtk_im_module "fcitx" using tool distribution provides or add `export gtk_im_module=fcitx` `~/.xprofile`. see [input method related environment variables: gtk_im_module](http://fcitx-im.org/wiki/input_method_related_environment_variables#gtk_im_module).** 2. `gtk-query-immodules`: 1. gtk 2: **cannot find `gtk-query-immodules` gtk 2** **cannot find fcitx im module gtk 2.** 2. gtk 3: **cannot find `gtk-query-immodules` gtk 3** **cannot find fcitx im module gtk 3.** 3. gtk im module cache: 1. gtk 2: found immodules cache gtk `2.24.30` @ `/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules.cache`. version line: # created /usr/lib/x86_64-linux-gnu/libgtk2.0-0/gtk-query-immodules-2.0 gtk+-2.24.30 found fcitx im modules gtk `2.24.30`. "/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: found immodules cache gtk `3.18.9` @ `/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules.cache`. version line: # created /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 gtk+-3.18.9 found fcitx im modules gtk `3.18.9`. "/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: found gtk 2 immodule files exist. 2. gtk 3: 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 25 enabled addons: fcitx-autoeng fcitx-chttrans fcitx-classic-ui fcitx-clipboard fcitx-dbus fcitx-freedesktop-notify fcitx-fullwidth-char fcitx-hangul fcitx-imselector fcitx-ipc fcitx-keyboard fcitx-kimpanel-ui fcitx-lua fcitx-notificationitem fcitx-punc fcitx-quickphrase fcitx-remote fcitx-spell fcitx-unicode fcitx-unikey fcitx-vk fcitx-x11 fcitx-xim fcitx-xkb fcitx-xkbdbus 2. found 0 disabled addons: 3. addon libraries: libraries addons found. 4. user interface: found 2 enabled user interface addons: fcitx-classic-ui fcitx-kimpanel-ui ## input methods: 1. found 2 enabled input methods: fcitx-keyboard-us unikey 2. default input methods: have keyboard input method "fcitx-keyboard-us" correctly added default input method. # log: 1. `date`: sat oct 29 19:09:27 kst 2016 2. `~/.config/fcitx/log/`: total 0 -rw-rw-r-- 1 trongkha trongkha 0 oct 29 19:00 crash.log 3. `~/.config/fcitx/log/crash.log`:
on machine fcitx got autostarted im-config under (x)ubuntu 16.04 see /usr/share/im-config/ when deinstalled fcitx packages, im-config still invoke fcitx. therefore recommend check if have im-config installed , how configured. (in case im-config autostarted fcitx process eat memory , made machine unusable).
why relevant?
my guess im-config improperly launches (or improperly configured launch) its own fcitx binary may interfere actual packaged fcitx tool set. means while suspect running fcitx 1 came package manager in reality another, potentially older version of fcitx gets run , gets in trouble system. consequence recommendations above reinstall fcitx not change/improve anything.
what im-config set found in /usr/share/im-config/
i had behaviour on machine , either packaging bug or legacy configuration bug or upgrade bug (i had ubuntu kylin installed , dist-upgraded multiple times). recommend backup im-config configuration files in /usr/share/im-config/, , purge im-config, delete files in /usr/share/im-config/ if , reinstall clean, fresh installation of im-config.
Comments
Post a Comment