{"id":2361,"date":"2017-10-27T01:06:32","date_gmt":"2017-10-26T17:06:32","guid":{"rendered":"https:\/\/www.csslayer.info\/wordpress\/?p=2361"},"modified":"2017-10-28T14:25:19","modified_gmt":"2017-10-28T06:25:19","slug":"how-to-use-fcitx-on-ubuntu-17-10","status":"publish","type":"post","link":"https:\/\/www.csslayer.info\/wordpress\/fcitx-dev\/how-to-use-fcitx-on-ubuntu-17-10\/","title":{"rendered":"How to use fcitx on Ubuntu 17.10"},"content":{"rendered":"

Since ubuntu moves to GNOME 3, there’s some difference if you want to use fcitx. It’s not hard to do, but need some manual tweak on user configurations.<\/p>\n

Here is the instruction about how to use fcitx on a fresh installed ubuntu 17.10 system. Personally I just choose English as system language for this instruction, but it should make no difference.<\/p>\n

So first of all, you will need to install fcitx and the input method you want anyway.<\/p>\n

sudo apt-get install fcitx fcitx-mozc<\/pre>\n
Under GNOME the old im-config seems not working because GNOME only supports ibus and they don’t want any other input method related system to use it. We’ll need to set the environment variable manually because of that.<\/p>\n
I used to recommend people use ~\/.xprofile. but since this file is X only, I’d suggest to use .pam_environment file to set the variable.<\/p>\n
On a freshly installed ubuntu 17.10, you will not have ~\/.pam_environment file. So you can use<\/p>\n
gedit ~\/.pam_environment<\/pre>\n
to edit and create this file with following content.<\/p>\n
XMODIFIERS DEFAULT=@im=fcitx\r\nGTK_IM_MODULE DEFAULT=fcitx\r\nQT_IM_MODULE DEFAULT=fcitx<\/pre>\n
Then, you’ll also need to add an autostart entry to start fcitx. Search “Startup applications Preferences” and add an new entry for fcitx.<\/p>\n
\"\"<\/a><\/p>\n
After that, you’ll already be able to get Fcitx working. But I still recommend you to install this extension for better experience under GNOME. https:\/\/extensions.gnome.org\/extension\/261\/kimpanel\/<\/a>. It also provides extra functionality on correctly setting keyboard layout under GNOME with fcitx.\u00a0Otherwise any keyboard layout group change outside mutter will be reset to mutter’s internal value. (See https:\/\/bugzilla.gnome.org\/show_bug.cgi?id=756543#c18<\/a> for more information)<\/p>\n
Unfortunately, it’s hard to install gnome shell extension from browser in a default installation.<\/p>\n
To use firefox you may follow the instruction on the website and install firefox extension. (I have no idea why Ubuntu doesn’t include this package and use firefox as default browser, probably this issue is worth a bug report.) You’ll also need to install<\/p>\n
sudo apt-get install chrome-gnome-shell<\/pre>\n
Or you can use gnome’s browser<\/p>\n
sudo apt-get install epiphany-browser<\/pre>\n
To install extension from browser. That are many other way to install gnome shell extensions so I’m not gonna to cover it all.<\/p>\n
\"\"<\/a>P. S.<\/p>\n
My system does not gives me Wayland session for some reason, so I can’t test the GNOME wayland on Ubuntu 17.10. But just to let you know, as described in my last post, you may use fcitx on GNOME’s wayland session. Though, to get the input method window displayed at right location you currently will need to use fcitx’s master branch and use kimpanel extension.<\/p>\n","protected":false},"excerpt":{"rendered":"
Since ubuntu moves to GNOME 3, there’s some difference if you want to use fcitx. It’s not hard to do, but need some manual tweak on user configurations. Here is the instruction about how to use fcitx on a fresh … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[44],"tags":[12,17],"class_list":["post-2361","post","type-post","status-publish","format-standard","hentry","category-fcitx-dev","tag-fcitx","tag-ubuntu"],"_links":{"self":[{"href":"https:\/\/www.csslayer.info\/wordpress\/wp-json\/wp\/v2\/posts\/2361","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.csslayer.info\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.csslayer.info\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.csslayer.info\/wordpress\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.csslayer.info\/wordpress\/wp-json\/wp\/v2\/comments?post=2361"}],"version-history":[{"count":5,"href":"https:\/\/www.csslayer.info\/wordpress\/wp-json\/wp\/v2\/posts\/2361\/revisions"}],"predecessor-version":[{"id":2375,"href":"https:\/\/www.csslayer.info\/wordpress\/wp-json\/wp\/v2\/posts\/2361\/revisions\/2375"}],"wp:attachment":[{"href":"https:\/\/www.csslayer.info\/wordpress\/wp-json\/wp\/v2\/media?parent=2361"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.csslayer.info\/wordpress\/wp-json\/wp\/v2\/categories?post=2361"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.csslayer.info\/wordpress\/wp-json\/wp\/v2\/tags?post=2361"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}