A permanent solution to the garbled candidate words of Sogou input method in Ubuntu 18.04.03 (under a specific situation)

question:

Under Linux, the Sogou input method is still very conscientious. There are no ads or anything. When the built-in lbus is not easy to use, installing Sogou is basically the only and very good choice. It was installed in the Ubuntu14.04 system before. Sogou is very normal and easy to use. However, after switching to 18.04.3, I installed the search input method and found that the candidate word panel has garbled characters. The specific manifestation is: Normally, if you press shift twice in succession, garbled characters will appear. When the code is garbled, press shift twice in succession and it will become normal.

I have been looking for methods for a long time. Most of them involve deleting some of Sogou's own configuration folders, restarting fcitx, etc. But maybe in some cases it is not so complicated. The following is a method used by others [1]. I have tried this method and it is temporary. Basically, after restarting, this problem will still occur from time to time. It is particularly annoying. The candidate words can only be guessed at which position. bits to enter...

 In fact, if you look closely, you will see that the panel is not Sogou's panel at all, but fcitx's own panel, which means that some components of Sogou's own panel did not start automatically, causing problems.

Solution:

The following is a solution to a specific situation, which may not be applicable to all, but because my system is new, there will basically be no other messy problems, and all the modified dependencies are installed.

Looking at my fcitx panel, I was being smart and thought about using Sogou first, and then put Sogou Pinyin first. I didn't see the following note: "The first input method will be inactive. Usually you need to put the keyboard or keyboard-layout name first ".

According to the prompts, adjust "Sogou Pinyin" to the second position , as shown in the picture below, the world is clean... After that, shift can be switched at will, and there has been no problem again.

references:

[1]  https://blog.csdn.net/ordream/article/details/84312367Examples   of other people’s solutions

Guess you like

Origin blog.csdn.net/u012057432/article/details/103321735