[Bug 262863] www/amfora: post-install hint on how to resolve crash on startup if TERM not recognized [#300]
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 27 Mar 2022 14:20:08 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262863
Bug ID: 262863
Summary: www/amfora: post-install hint on how to resolve crash
on startup if TERM not recognized [#300]
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: lcook@freebsd.org
Reporter: keen.year0891@fastmail.com
Flags: maintainer-feedback?(lcook@freebsd.org)
Assignee: lcook@freebsd.org
A Go dependency compiled into amfora will crash at startup when it doesn’t
recognize the terminal type declared in TERM. Investigated with amfora’s
author, and reported to the upstream dependencies. (See
https://github.com/makeworld-the-better-one/amfora/issues/300 and mentions
there.)
In my case specifically for running under tmux, installing the ncurses port
resolved the crash. This has to do with missing terminfo data, though
installing the terminfo-db port alone did not help.
Steps to reproduce:
1. On a clean FreeBSD 13.0-RELEASE system, install amfora and tmux from ports
or pkg
2. Run tmux, or export TERM=tmux-256color
3. Run amfora
Expected results:
Amfora starts
Actual results:
Go runtime crashes and prints a stack trace
Suggested workaround: Call out that additional data from ncurses may be needed
in a post-install message; or, add ncurses as a dependency to cover any
terminfo that may not be bundled as expected.
My system: 13.0-RELEASE-p6 FreeBSD 13.0-RELEASE-p6 #0: Mon Jan 10 06:33:27 UTC
2022
root@arm64-builder.daemonology.net:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC
arm64
% amfora -v
Amfora v1.9.2
Commit: 61d8645
Built by: unknown
--
You are receiving this mail because:
You are the assignee for the bug.