Package Details: fbterm 1.7_5-5

Git Clone URL: (read-only, click to copy)
Package Base: fbterm
Description: Framebuffer terminal emulator
Upstream URL:
Keywords: console emulator fbterm framebuffer terminal tty
Licenses: GPL2
Conflicts: fbterm
Provides: fbterm
Submitter: ivanp7
Maintainer: ivanp7
Last Packager: ivanp7
Votes: 5
Popularity: 0.72
First Submitted: 2021-05-19 12:15 (UTC)
Last Updated: 2023-09-23 04:45 (UTC)

Pinned Comments

ivanp7 commented on 2022-01-16 16:27 (UTC) (edited on 2022-01-16 18:24 (UTC) by ivanp7)

I have applied the proposed "configurable color palette" patch. Now the colors may be specified in the configuration file using numbered parameters color-num=RRGGBB.


ivanp7 commented on 2021-11-27 21:50 (UTC)

I changed my mind. $XDG_CONFIG_HOME/fbterm/fbtermrc is now an allowed configuration location along with the old $XDG_CONFIG_HOME/fbtermrc. Old location is used only when $XDG_CONFIG_HOME/fbterm/ does not exist.

ivanp7 commented on 2021-05-20 11:46 (UTC) (edited on 2021-05-20 13:13 (UTC) by ivanp7)

To set a wallpaper in fbterm, you'll need fbv package (framebuffer image viewer). Execute the following instructions right before launching fbterm (works in POSIX-compliant shell like dash):

# hide cursor
echo -ne "\e[?25l"
# display fullscreen-stretched image and quit viewer without screen refreshing
fbv -ciuker "$WALLPAPER_FILE" << EOF
# use current screen state as a wallpaper

ivanp7 commented on 2021-05-20 11:35 (UTC) (edited on 2021-09-25 01:37 (UTC) by ivanp7)

To enable 256 color mode properly, do export TERM=fbterm-256color AFTER fbterm starts and then attach to a tmux session. If TERM is not linux upon fbterm launch, it will fail. Tmux is needed because fbterm provides escape codes that differ from broadly used codes, so tmux serves as an abstraction layer.

Unlike vanilla fbterm, in this version the configuration file is located at $XDG_CONFIG_HOME/fbtermrc or $HOME/.config/fbtermrc if XDG_CONFIG_HOME is unset or empty (the original placement is $HOME/.fbtermrc). Also, the configuration file is not forcibly recreated anymore. For default configuration, see /etc/fbterm/fbtermrc.example.

Latest Comments

1 2 3 Next › Last »

Erwin_Iosef commented on 2024-02-27 17:26 (UTC)

Hello, ivanp7, I installed fbterm and did all the steps necessary but I'm unable to configure it, there is no fbtermrc file generated and even the rc file I created myself on the home directory,has no effect on changing the font colour, size, etc. The only thing I'm able to change is the wallpaper. But that is due to fbv. I don't know if this the right place for posting issues, or what info I should provide but I hope you can help me, many thanks for creating this package.

MShrimp4 commented on 2023-09-05 23:00 (UTC)

I automated thx1138's solution. (For someone building with yay, just do yay --editmenu -S fbterm and apply this solution.)

@L41 add:

sed -i -e 's#SUBDIRS = .*#SUBDIRS = src im doc#g' Makefile

ivanp7 commented on 2023-08-19 00:39 (UTC) (edited on 2023-08-19 00:43 (UTC) by ivanp7)

It is the tic command, for some weird reason it writes to both $TERMINFO and /usr/share/terminfo. I couldn't figure out why and how to prevent this behavior, so went with the straightforward way (it worked for me the last time I checked). If you guys find a solution, I'll update the PKGBUILD.

me_231231 commented on 2023-08-16 17:23 (UTC) (edited on 2023-08-16 17:23 (UTC) by me_231231)

This package does not build properly:

make[2]: Nothing to be done for 'install-exec-am'.
tic fbterm
"fbterm", line 2, terminal 'fbterm-256color': /usr/share/terminfo/f: permission denied
make[2]: *** [Makefile:424: install-data-local] Error 1
make[2]: Leaving directory '/home/dk/.cache/paru/clone/fbterm/src/fbterm-1.7/terminfo'
make[1]: *** [Makefile:317: install-am] Error 2
make[1]: Leaving directory '/home/dk/.cache/paru/clone/fbterm/src/fbterm-1.7/terminfo'
make: *** [Makefile:378: install-recursive] Error 1

Why does the it require access to /usr/share/terminfo/f during the build stage?

thx1138 commented on 2023-07-29 01:47 (UTC)

tic fbterm
"fbterm", line 2, terminal 'fbterm-256color': /usr/share/terminfo/f: permission denied
fbterm/src/fbterm-1.7/terminfo$ cat

EXTRA_DIST = fbterm

       tic fbterm
  mkdir -p tic
  TERMINFO=$srcdir/$_gitname-$_majorver/tic tic terminfo/fbterm

It looks like both the PKGBUILD and the stock in fbterm-1.7/terminfo are running tic on terminfo/fbterm, but running tic from the Makefile, without first resetting the TERMINFO= directory, tic tries to access the filesystem outside of the BUILDDIR directory.

You could run makepkg -o, then edit the toplevel Makefile to remove the "terminfo" subdirctory from the list:

SUBDIRS = src im doc

and then makepkg -ei. It's not elegant, but it works.

phil2sat commented on 2023-07-26 09:33 (UTC) (edited on 2023-07-26 09:36 (UTC) by phil2sat)

I get a strange error while doin makepkg:

make[2]: Für das Ziel „install-exec-am“ ist nichts zu tun.
tic fbterm
"fbterm", line 2, terminal 'fbterm-256color': /usr/share/terminfo/f: permission denied
make[2]: *** [Makefile:424: install-data-local] Fehler 1
make[2]: Verzeichnis „/tmp/pkgbuild-0/fbterm/src/fbterm-1.7/terminfo“ wird verlassen
make[1]: *** [Makefile:317: install-am] Fehler 2
make[1]: Verzeichnis „/tmp/pkgbuild-0/fbterm/src/fbterm-1.7/terminfo“ wird verlassen
make: *** [Makefile:378: install-recursive] Fehler 1

I read something about that cant install terminfo and recompiled a patched ncurses which should resolv the issue but unfortunately does not.

Any suggestions?

ivanp7 commented on 2022-09-25 18:43 (UTC)

@Neubulae This package has little difference from debian vanilla, the patches do not modify core behavior of fbterm.

Neubulae commented on 2022-09-25 07:45 (UTC) (edited on 2022-09-25 10:10 (UTC) by Neubulae)

does this follow the same procedure as enabling fast scrolling for vanilla fbterm? Edit: The real reason I asked this question is because I am using an AMDGPU on a 2K, 144Hz screen, which, for whatever reason, suffers bad performance. I wonder how do I circumvent this problem. Following the procedure listed on uvesafb page gives me an fbterm -v output of EFI VGA instead of amdgpudrmfb and that gives me a better performance, but that also prevents me from booting into GDM either. I don't actually understand what's going on and I don't know how to proceed further.

m040601 commented on 2022-09-01 01:47 (UTC) (edited on 2022-09-05 01:01 (UTC) by m040601)

I have ressurected the Archwiki "fbterm" page from the dead. There is now a proper place to put all these tiny important bits of information about fbterm in Arch. Things like tips, ticks, differences to upstream introduced by this PKGBUILD patches etc.

Please help us make that a great usefull page.

@ivanp: Could you check that all the very important notes you "pinned" and posted here are there if relevant.

It still needs some updating and editing, reviewed by someone more knowleageble than me. Especially for the delicate intrincacies of patches, terminfo, etc.

Hope this can serve better all of those cli/framebuffer Arch fans. We're a very very tiny minority. So it's not easy to find usefull/correct/updated information on the Big Internet.

For specific, Framebufffer ONLY, things a much better use can be made of the Archwiki. So that the ticks, tips, and modern usage possibilities dont get lost in a giant page listing all the other CLI/TUI apps and tools, that are not framebuffer specific.

ivanp7 commented on 2022-01-17 12:34 (UTC)

Fixed screen_render.cpp, updated fbtermrc.example and manpage.