Difference between revisions of "Fbterm"
Weng Xuetian (talk | contribs) |
Weng Xuetian (talk | contribs) m (Text replacement - "<translate1>" to "<translate>") |
||
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | <languages /> | + | <languages/> |
<translate> | <translate> | ||
| Line 7: | Line 7: | ||
|screenshot = [[File:fcitx-fbterm.png|200px]] | |screenshot = [[File:fcitx-fbterm.png|200px]] | ||
|caption2 = fbterm support for fcitx | |caption2 = fbterm support for fcitx | ||
| − | |version = 0. | + | |version = 0.2.0 |
|programming language = C | |programming language = C | ||
|dependency = fbterm | |dependency = fbterm | ||
| Line 16: | Line 16: | ||
== Intro == <!--T:2--> | == Intro == <!--T:2--> | ||
Let you use fcitx under [http://code.google.com/p/fbterm/ fbterm]. | Let you use fcitx under [http://code.google.com/p/fbterm/ fbterm]. | ||
| + | |||
| + | This wiki page is written for fcitx-fbterm 0.2.0 or higher. | ||
== Prepare == <!--T:3--> | == Prepare == <!--T:3--> | ||
| Line 23: | Line 25: | ||
sudo setcap 'cap_sys_tty_config+ep' /usr/bin/fbterm # required to let fbterm get key-sequence | sudo setcap 'cap_sys_tty_config+ep' /usr/bin/fbterm # required to let fbterm get key-sequence | ||
| + | <!--T:17--> | ||
And add your account to video group with (use ls -l /dev/fb0 to check the user group): | And add your account to video group with (use ls -l /dev/fb0 to check the user group): | ||
| − | sudo gpasswd -a <your username> video | + | <!--T:18--> |
| + | sudo gpasswd -a <your username> video | ||
<!--T:5--> | <!--T:5--> | ||
| − | or | + | or (it's NOT safe because it sets setuid.) |
<!--T:6--> | <!--T:6--> | ||
| − | sudo chmod u+s /usr/bin/fbterm | + | sudo chmod u+s /usr/bin/fbterm |
| − | + | <!--T:7--> | |
Notice, if you don't use KMS (Kernel mode settings, in other words, open source display driver), you must start fbterm with root. | Notice, if you don't use KMS (Kernel mode settings, in other words, open source display driver), you must start fbterm with root. | ||
| − | === | + | === When fcitx is already running under X === <!--T:15--> |
| − | For example, if your X is :0 ( | + | For example, if your X is :0 (this is the default case for desktop user). |
| − | + | You can use | |
| − | + | ||
| + | <!--T:8--> | ||
fcitx-fbterm-helper | fcitx-fbterm-helper | ||
| + | |||
| + | To start fbterm. If your display is not 0, for example, it's running as :1, you can use | ||
| + | |||
| + | fcitx-fbterm-helper -d 1 | ||
| + | |||
| + | to override it. | ||
<!--T:9--> | <!--T:9--> | ||
| − | If no error | + | If there is no error, then everything should work, one additional thing you need pay attention is, fbterm hardcodes Ctrl+Space as input method trigger key, this is not controlled by fcitx and not changable. |
| − | === Without X or have problem === <!--T:10--> | + | === Without X or have some problem === <!--T:10--> |
fcitx-fbterm-helper -l | fcitx-fbterm-helper -l | ||
<!--T:11--> | <!--T:11--> | ||
| − | It will launch | + | It will launch new fcitx. And fcitx will be killed when fbterm ends. |
| − | + | If there is already a fcitx running, fcitx-fbterm-helper will refuse to work, you can use | |
| − | |||
| − | + | killall fcitx | |
| − | |||
| − | + | to kill existing fcitx. | |
| − | |||
| − | == | + | == Troubleshoot == <!--T:16--> |
If you meet some trouble about keyboard not reaction, screen artifacts, you can first try Ctrl+Alt+E (force fbterm to exit), if this doesn't work and you have enabled magic key (sysctl, kernel.sysrq = 1), you can try only sysrq + r (not the full reisub!), this will force keyboard input to forward to kernel, then you can switch between tty. | If you meet some trouble about keyboard not reaction, screen artifacts, you can first try Ctrl+Alt+E (force fbterm to exit), if this doesn't work and you have enabled magic key (sysctl, kernel.sysrq = 1), you can try only sysrq + r (not the full reisub!), this will force keyboard input to forward to kernel, then you can switch between tty. | ||
</translate> | </translate> | ||
Latest revision as of 22:54, 2 February 2016
 | |
| Version | 0.2.0 |
|---|---|
| Dependency | fbterm |
| Written In | C |
| License | GPLv2 |
| Website | http://github.com/fcitx/fcitx-fbterm |
Intro
Let you use fcitx under fbterm.
This wiki page is written for fcitx-fbterm 0.2.0 or higher.
Prepare
In order to make fbterm can use input method.
sudo setcap 'cap_sys_tty_config+ep' /usr/bin/fbterm # required to let fbterm get key-sequence
And add your account to video group with (use ls -l /dev/fb0 to check the user group):
sudo gpasswd -a <your username> video
or (it's NOT safe because it sets setuid.)
sudo chmod u+s /usr/bin/fbterm
Notice, if you don't use KMS (Kernel mode settings, in other words, open source display driver), you must start fbterm with root.
When fcitx is already running under X
For example, if your X is :0 (this is the default case for desktop user).
You can use
fcitx-fbterm-helper
To start fbterm. If your display is not 0, for example, it's running as :1, you can use
fcitx-fbterm-helper -d 1
to override it.
If there is no error, then everything should work, one additional thing you need pay attention is, fbterm hardcodes Ctrl+Space as input method trigger key, this is not controlled by fcitx and not changable.
Without X or have some problem
fcitx-fbterm-helper -l
It will launch new fcitx. And fcitx will be killed when fbterm ends.
If there is already a fcitx running, fcitx-fbterm-helper will refuse to work, you can use
killall fcitx
to kill existing fcitx.
Troubleshoot
If you meet some trouble about keyboard not reaction, screen artifacts, you can first try Ctrl+Alt+E (force fbterm to exit), if this doesn't work and you have enabled magic key (sysctl, kernel.sysrq = 1), you can try only sysrq + r (not the full reisub!), this will force keyboard input to forward to kernel, then you can switch between tty.