Difference between revisions of "Fbterm"
Weng Xuetian (talk | contribs) (Marked this version for translation) |
Weng Xuetian (talk | contribs) |
||
| Line 39: | Line 39: | ||
=== With X running, and run as same user with X === <!--T:15--> | === With X running, and run as same user with 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). |
| − | + | <!--T:8--> | |
| − | export DISPLAY=:0 | + | export DISPLAY=:0 |
fcitx-fbterm-helper | fcitx-fbterm-helper | ||
<!--T:9--> | <!--T:9--> | ||
| − | If no error output, it | + | If there is no error output, it should work. |
=== Without X or have problem === <!--T:10--> | === Without X or have problem === <!--T:10--> | ||
Revision as of 16:39, 16 May 2013
 | |
| Version | 0.1.3 |
|---|---|
| Dependency | fbterm |
| Written In | C |
| License | GPLv2 |
| Website | http://github.com/fcitx/fcitx-fbterm |
Intro
Let you use fcitx under fbterm.
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
sudo chmod u+s /usr/bin/fbterm # not-safe because of it set setuid.
Launch fbterm
Notice, if you don't use KMS (Kernel mode settings, in other words, open source display driver), you must start fbterm with root.
With X running, and run as same user with X
For example, if your X is :0 (this is the default case for desktop user).
export DISPLAY=:0 fcitx-fbterm-helper
If there is no error output, it should work.
Without X or have problem
fcitx-fbterm-helper -l
It will launch a new dbus daemon and new fcitx. There is a message indicating that there should be only fcitx running. So run
killall fcitx
before you start execute fcitx-fbterm-helper.
Unreleased fcitx-fbterm 0.1.4's fcitx-fbterm-helper can kill dbus-daemon and fcitx when fbterm quits, you can grab the script here. It's ok to run it from anywhere so you don't need to replace the system script.
Trouble
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.