Ubuntu安装搜狗输入法无法使用

BugScanner 发布于 2015/12/22 15:28
阅读 10K+
收藏 1

【DevOps必读】产品经理与程序员之间如何破局?>>>

好久没有解决的问题


在Fcitx configuration中一片空白

在Addon中能找到搜狗输入法

在终端运行

fcitx autostart



结果

(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-unicode.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-punc.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-vk.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-autoeng-ng.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-table.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-fullwidth-char.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-quickphrase.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-lua.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-xkbdbus.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-clipboard.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-classic-ui.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-notificationitem.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-autoeng.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-pinyin-enhance.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-sunpinyin.conf
(WARN-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx-config/fcitx-config.c:172) missing value: Name
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-xim.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-punc-ng.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-cloudpinyin.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-xkb.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-pinyin.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-fullwidth-char-enhance.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-chttrans.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-imselector.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-keyboard.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-freedesktop-notify.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-ipc.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-sogoucloudpinyin.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-kimpanel-ui.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-spell.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-dbus.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-remote-module.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-sogoupinyin.conf
(INFO-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:151) Load Addon Config File:fcitx-x11.conf
(WARN-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/addon.c:298) Disable addon fcitx-xkbdbus, dependency fcitx-xkb,fcitx-dbus cannot be satisfied.
(ERROR-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/frontend.c:565) No available frontend
(ERROR-14072 /build/fcitx-cRl76F/fcitx-4.2.9/src/lib/fcitx/instance.c:440) Exiting.

在终端运行

fcitx-diagnose
结果

# System Info:
1.  `uname -a`:

        Linux localhost 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

2.  `lsb_release -a`:

        No LSB modules are available.
        Distributor ID:	Ubuntu
        Description:	Ubuntu 15.10
        Release:	15.10
        Codename:	wily

3.  `lsb_release -d`:

        Description:	Ubuntu 15.10

4.  `/etc/lsb-release`:

        DISTRIB_ID=Ubuntu
        DISTRIB_RELEASE=15.10
        DISTRIB_CODENAME=wily
        DISTRIB_DESCRIPTION="Ubuntu 15.10"

5.  `/etc/os-release`:

        NAME="Ubuntu"
        VERSION="15.10 (Wily Werewolf)"
        ID=ubuntu
        ID_LIKE=debian
        PRETTY_NAME="Ubuntu 15.10"
        VERSION_ID="15.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 `gnome3`.

7.  Bash Version:

        BASH_VERSION='4.3.42(1)-release'

# 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+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_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
            POSIX
            zh_CN.utf8
            zh_SG.utf8

    2.  Current locale:

            LANG=en_GB.UTF-8
            LANGUAGE=en_GB:en
            LC_CTYPE="en_GB.UTF-8"
            LC_NUMERIC=en_GB.UTF-8
            LC_TIME=en_GB.UTF-8
            LC_COLLATE="en_GB.UTF-8"
            LC_MONETARY=en_GB.UTF-8
            LC_MESSAGES="en_GB.UTF-8"
            LC_PAPER=en_GB.UTF-8
            LC_NAME=en_GB.UTF-8
            LC_ADDRESS=en_GB.UTF-8
            LC_TELEPHONE=en_GB.UTF-8
            LC_MEASUREMENT=en_GB.UTF-8
            LC_IDENTIFICATION=en_GB.UTF-8
            LC_ALL=

4.  Directories:

    1.  Home:

            /home/yang

    2.  `${XDG_CONFIG_HOME}`:

        Environment variable `XDG_CONFIG_HOME` is not set.

        Current value of `XDG_CONFIG_HOME` is `~/.config` (`/home/yang/.config`).

    3.  Fcitx Settings Directory:

        Current fcitx settings directory is `~/.config/fcitx` (`/home/yang/.config/fcitx`).

5.  Current user:

    The script is run as yang (1000).

# Fcitx State:
1.  executable:

    Found fcitx at `/usr/bin/fcitx`.

2.  version:

    Fcitx version: `4.2.9`

3.  process:

    **Fcitx is not running.**
    **Please check the Configure link of your distribution in [Beginner's Guide](http://fcitx-im.org/wiki/Beginner%27s_Guide) for how to setup fcitx autostart.**

# 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:

# Frontends setup:
## Xim:
1.  `${XMODIFIERS}`:

    **Environment variable XMODIFIERS is "@im=ibus" instead of "@im=fcitx". Please check if you have exported it incorrectly in any of your init files.**

    **Please set environment variable XMODIFIERS to "@im=fcitx" using the tool your distribution provides or add `export XMODIFIERS=@im=fcitx` to your `~/.xprofile`. See [Input Method Related Environment Variables: XMODIFIERS](http://fcitx-im.org/wiki/Input_method_related_environment_variables#XMODIFIERS).**

    Xim Server Name from Environment variable is ibus.

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 "xim" instead of "fcitx". Please check if you have exported it incorrectly in any of your init files.**
    **You are using xim in qt4 programs.**

    **To see some application specific problems you may have when using xim, check [Hall of Shame for Linux IME Support](http://fcitx-im.org/wiki/Hall_of_Shame_for_Linux_IME_Support). For other more general problems of using XIM including application freezing, see [here](http://fcitx-im.org/wiki/XIM).**

    **Please set environment variable QT4_IM_MODULE to "fcitx" using the tool your distribution provides or add `export QT4_IM_MODULE=fcitx` to your `~/.xprofile`. See [Input Method Related Environment Variables: QT4_IM_MODULE](http://fcitx-im.org/wiki/Input_method_related_environment_variables#QT4_IM_MODULE).**

2.  qt5 - `${QT_IM_MODULE}`:

    **Environment variable QT_IM_MODULE is "ibus" instead of "fcitx". Please check if you have exported it incorrectly in any of your init files.**
    **You may have trouble using fcitx in qt5 programs.**

    **Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add `export QT_IM_MODULE=fcitx` to your `~/.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 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 - `${GTK_IM_MODULE}`:

    **Environment variable GTK_IM_MODULE is "ibus" instead of "fcitx". Please check if you have exported it incorrectly in any of your init files.**
    **You may have trouble using fcitx in gtk programs.**

    **Please set environment variable GTK_IM_MODULE to "fcitx" using the tool your distribution provides or add `export GTK_IM_MODULE=fcitx` to your `~/.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` 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.28` 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.28

        Found fcitx im modules for gtk `2.24.28`.

            "/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 for gtk `3.16.7` 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.16.7

        Found fcitx im modules for gtk `3.16.7`.

            "/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 12 enabled addons:

            fcitx-classic-ui
            fcitx-dbus
            fcitx-fullwidth-char
            fcitx-fullwidth-char-enhance
            fcitx-lua
            fcitx-notificationitem
            fcitx-pinyin-enhance
            fcitx-sogoupinyin
            fcitx-unicode
            fcitx-vk
            fcitx-x11
            fcitx-xkbdbus

    2.  Found 21 disabled addons:

            fcitx-autoeng
            fcitx-autoeng-ng
            fcitx-chttrans
            fcitx-clipboard
            fcitx-cloudpinyin
            fcitx-freedesktop-notify
            fcitx-imselector
            fcitx-ipc
            fcitx-keyboard
            fcitx-kimpanel-ui
            fcitx-pinyin
            fcitx-punc
            fcitx-punc-ng
            fcitx-quickphrase
            fcitx-remote
            fcitx-sogoucloudpinyin
            fcitx-spell
            fcitx-sunpinyin
            fcitx-table
            fcitx-xim
            fcitx-xkb

3.  Addon Libraries:

    All libraries for all addons are found.

4.  User Interface:

    Found 1 enabled user interface addons:

        fcitx-classic-ui

## Input Methods:
1.  Found 1 enabled input methods:

        fcitx-keyboard-cn

2.  Default input methods:

    You only have one keyboard input method enabled. You may want to add another input method to input other languages.

# Log:
1.  `date`:

        Tue Dec 22 15:21:24 CST 2015

2.  `~/.config/fcitx/log/`:

        total 4
        -rw-r--r-- 1 yang yang 1372 Jul 19 22:43 crash.log

3.  `~/.config/fcitx/log/crash.log`:

        =========================
        FCITX 4.2.8.5 -- Get Signal No.: 11
        Date: try "date -d @1437317011" if you are using GNU date ***
        ProcessID: 2248
        /usr/bin/fcitx(+0x1737)[0x7f0d422d0737]
        /lib/x86_64-linux-gnu/libc.so.6(+0x352f0)[0x7f0d414a92f0]
        /lib/x86_64-linux-gnu/libdbus-1.so.3(+0x25846)[0x7f0d40766846]
        /lib/x86_64-linux-gnu/libdbus-1.so.3(+0x25915)[0x7f0d40766915]
        /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xcdbe)[0x7f0d4074ddbe]
        /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xcfd7)[0x7f0d4074dfd7]
        /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xd015)[0x7f0d4074e015]
        /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xd163)[0x7f0d4074e163]
        /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xe438)[0x7f0d4074f438]
        /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_bus_remove_match+0x64)[0x7f0d4074c2b4]
        /usr/lib/x86_64-linux-gnu/fcitx/fcitx-dbus.so(+0x2d39)[0x7f0d4098bd39]
        /usr/lib/x86_64-linux-gnu/libfcitx-utils.so.0(+0xa014)[0x7f0d41a66014]
        /usr/lib/x86_64-linux-gnu/libfcitx-utils.so.0(fcitx_handler_table_free+0x24)[0x7f0d41a66344]
        /usr/lib/x86_64-linux-gnu/fcitx/fcitx-dbus.so(+0x2377)[0x7f0d4098b377]
        /usr/lib/x86_64-linux-gnu/libfcitx-core.so.0(+0x9048)[0x7f0d41e91048]
        /usr/lib/x86_64-linux-gnu/libfcitx-core.so.0(FcitxInstanceRun+0x210)[0x7f0d41e91480]
        /usr/bin/fcitx(+0x10cc)[0x7f0d422d00cc]
        /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f0d41494a40]
        /usr/bin/fcitx(_start+0x29)[0x7f0d422d0149]
上面说 **Environment variable GTK_IM_MODULE is "ibus" instead of "fcitx". Please check if you have exported it incorrectly in any of your init files.**

我已经设置

im-config -s fcitx
同时


求大神help!!!!!!!!!!!!!!!!!!!!!


加载中
1
eechen
poorghost
poorghost
回复 @BugScanner : 很有用。我删除了 ~/.config里面的fcitx文件夹就可以了。怀疑应该是哪里配置错了导致配置文件损害。
BugScanner
BugScanner
研究了很長時間,現在終於解決了,刪除`/.config文件夾裏面的fcitx即可,在在终端里面敲fcitx -d如果出现了DBus Service Already Exists的报错,重新安装sudo apt-get install --resintall fcitx-fontend-gtk2 fctix-fontend-gtk3就行了
0
泽泽爱美丽

握草,真的很牛逼,爬了不知道多少篇文章,终于找到这个解决方案,关键是在Ubuntu18上也适用。厉害厉害,就是不知道原理是啥,,。

0
z
zx993566077

十分感谢,花了一天时间折腾 fcitx 和 搜狗输入法,总算解决了。

现象和你的描述一样,不过我这里直接删除 ~/.config/fcitx 文件夹,然后重新运行 Fcitx 配置就可以了。

返回顶部
顶部