github-starred/nvitop

Fork 0

mirror of https://github.com/XuehaiPan/nvitop.git synced 2026-05-15 14:15:55 -06:00

[GH-ISSUE #118] [Question] ERROR: Failed to initialize `curses` (setupterm: could not find terminfo database) #72

New issue

Closed

opened 2026-05-05 03:24:30 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 03:24:30 -06:00

Owner

Originally created by @yyfcc17 on GitHub (Jan 1, 2024).
Original GitHub issue: https://github.com/XuehaiPan/nvitop/issues/118

Originally assigned to: @XuehaiPan on GitHub.

Required prerequisites

I have read the documentation https://nvitop.readthedocs.io.
I have searched the Issue Tracker that this hasn't already been reported. (comment there if it has.)
I have tried the latest version of nvitop in a new isolated virtual environment.

Questions

after i run nvitop, i got this error

i think this issue is related to miniconda env, i encountered this error twice.

i packed my miniconda env, and transfered to another computer to unpack and recreate the env, it is on the second computer, i had this issue.
i changed my miniconda path, then i got this issue, before this operation, nvitop runs perfectly.

it is easy to reproduce, you can investigate into it.

thanks for creating this greate tool.

Originally created by @yyfcc17 on GitHub (Jan 1, 2024). Original GitHub issue: https://github.com/XuehaiPan/nvitop/issues/118 Originally assigned to: @XuehaiPan on GitHub. ### Required prerequisites - [X] I have read the documentation <https://nvitop.readthedocs.io>. - [X] I have searched the [Issue Tracker](https://github.com/XuehaiPan/nvitop/issues) that this hasn't already been reported. (comment there if it has.) - [X] I have tried the latest version of nvitop in a new isolated virtual environment. ### Questions after i run nvitop, i got this error i think this issue is related to miniconda env, i encountered this error twice. 1. i packed my miniconda env, and transfered to another computer to unpack and recreate the env, it is on the second computer, i had this issue. 2. i changed my miniconda path, then i got this issue, before this operation, nvitop runs perfectly. it is easy to reproduce, you can investigate into it. thanks for creating this greate tool.

gitea-mirror

2026-05-05 03:24:30 -06:00

closed this issue
added the
cli / tui

question
labels

gitea-mirror commented

2026-05-05 03:24:33 -06:00

Author

Owner

@XuehaiPan commented on GitHub (Jan 1, 2024):

Duplicate of #38.

transfered to another computer

@yyfcc17 Do you set the TERM environment variable properly in your shell environment? You can try:

export TERM="xterm-256color"
export TERMINFO="${CONDA_PREFIX}/share/terminfo"
nvitop

@XuehaiPan commented on GitHub (Jan 1, 2024): Duplicate of #38. > transfered to another computer @yyfcc17 Do you set the `TERM` environment variable properly in your shell environment? You can try: ```bash export TERM="xterm-256color" export TERMINFO="${CONDA_PREFIX}/share/terminfo" nvitop ```

gitea-mirror commented

2026-05-05 03:24:34 -06:00

Author

Owner

@yyfcc17 commented on GitHub (Jan 2, 2024):

i think this issue is related to miniconda env, i encountered this error twice.

i packed my miniconda env, and transfered to another computer to unpack and recreate the env, it is on the second computer, i had this issue.

i changed my miniconda path, then i got this issue, before this operation, nvitop runs perfectly.

export TERM="xterm-256color"
export TERMINFO="${CONDA_PREFIX}/share/terminfo"
nvitop

this can solve the first situation, but still not working for the second.

and i think it is not the reason for this issue, because i have installed nvitop in another env in miniconda, in this env, nvitop works well.

i think maybe the move operation / change dir operation breaks the link to terminfo or something like that.

@yyfcc17 commented on GitHub (Jan 2, 2024): > i think this issue is related to miniconda env, i encountered this error twice. > > 1. i packed my miniconda env, and transfered to another computer to unpack and recreate the env, it is on the second computer, i had this issue. > 2. i changed my miniconda path, then i got this issue, before this operation, nvitop runs perfectly. > ``` shell export TERM="xterm-256color" export TERMINFO="${CONDA_PREFIX}/share/terminfo" nvitop ``` this can solve the first situation, but still not working for the second. and i think it is not the reason for this issue, because i have installed nvitop in another env in miniconda, in this env, nvitop works well. i think maybe the `move operation / change dir operation` breaks the link to terminfo or something like that.

gitea-mirror commented

2026-05-05 03:24:35 -06:00

Author

Owner

@yyfcc17 commented on GitHub (Jan 2, 2024):

issue solved.

the conda ncurses package is broken, need to reinstall.

for my case:

rm -rf miniconda3/pkgs/ncurses-6.4-h6a678d5_0
conda install -c conda-forge ncurses

then nvitop works again.

@yyfcc17 commented on GitHub (Jan 2, 2024): issue solved. the conda `ncurses` package is broken, need to reinstall. for my case: ```shell rm -rf miniconda3/pkgs/ncurses-6.4-h6a678d5_0 conda install -c conda-forge ncurses ``` then nvitop works again.

gitea-mirror commented

2026-05-05 03:24:35 -06:00

Author

Owner

@lhyscau commented on GitHub (Mar 5, 2024):

Duplicate of #38.

transfered to another computer

@yyfcc17 Do you set the TERM environment variable properly in your shell environment? You can try:
export TERM="xterm-256color"
export TERMINFO="${CONDA_PREFIX}/share/terminfo"
nvitop

WTF! It works! Thanks!

@lhyscau commented on GitHub (Mar 5, 2024): > Duplicate of #38. > > > transfered to another computer > > @yyfcc17 Do you set the `TERM` environment variable properly in your shell environment? You can try: > > ```shell > export TERM="xterm-256color" > export TERMINFO="${CONDA_PREFIX}/share/terminfo" > nvitop > ``` WTF! It works! Thanks!

gitea-mirror referenced this issue

2026-05-05 03:26:55 -06:00

[PR #92] [MERGED] feat(exporter): add Prometheus exporter #157