Summary: | app-misc/tmux-2.6 with sys-libs/ncurses-6.1-r1: open terminal failed: missing or unsuitable terminal: screen-256color | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dennis Schridde <dschridde+gentoobugs> |
Component: | Current packages | Assignee: | Gentoo Shell Tools project <shell-tools> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | abovill, alexander, arne_bab, basdebakker, chris, djc, esigra, gentoo-bugs, gentoo.2019, jbaldassari, julien.sanchez, kingjon3377, mark+gentoobugs, pacho, simon.vanderveldt+gentoo, tuxmind.bug, vylaern |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=648114 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 648114, 652080 | ||
Attachments: | ncurses-compat-6.1_p20190609.ebuild |
Description
Dennis Schridde
2018-02-24 18:18:51 UTC
Same here, in my case it's xterm-256color which won't work via ssh: tmux open terminal failed: missing or unsuitable terminal: xterm-256color There may be two workarounds: In case your affected user still has running tmux sessions, you need to use a different TERM setting: TERM="xterm-color" tmux If you want to get rid of this "workaround", close all tunning tmux sessions and you should be able to start tmux with *-256color TERM setting again. (In reply to Lars Wendler (Polynomial-C) from comment #2) > There may be two workarounds: > > In case your affected user still has running tmux sessions, you need to use > a different TERM setting: > > TERM="xterm-color" tmux > > If you want to get rid of this "workaround", close all tunning tmux sessions > and you should be able to start tmux with *-256color TERM setting again. s/tunning/running/ I had similar problem with games-roguelike/dwarf-fortress. When I was trying to start TEXT mode, I had such error: Error opening terminal: xterm-256color Downgrading ncurses from 6.1-r2 into 6.0-r1 temporary solved my problems. is tmux-2.7 also affected by this? Just wanted to leave a reminder of [ GLSA 201804-13 ] ncurses https://forums.gentoo.org/viewtopic-t-1080010.html /usr/share/terminfo/s/screen-256color should be a symlink to ../../../../etc/terminfo/s/screen-256color, and obviously you should have the real file at /etc/terminfo/s/screen-256color. please check those paths exist. if they don't, please attach the full build log of ncurses. *** Bug 651644 has been marked as a duplicate of this bug. *** although to re-iterate Lars' point from comment #3, are you connecting to an existing session or does this show up when creating a new one ? if it's an existing session, i think we're just going to say you need to restart all your sessions. or `reboot` if you're lazy :p. I'm coming from the gradle issue (https://bugs.gentoo.org/651644), I have /etc/terminfo/s/screen-256color and /usr/share/terminfo/s/screen-256color is a symlink to it. So far only exporting TERM=xterm-color seems to work as a workaround. Default value I have for it is xterm-256color Same as @simon here I had a similar issue with xterm-256color and gradle, I was able to resolve this with sys-libs/ncurses-6.1-r2 enabling tinfo USE flag and making sure to remove any old preserved libs (for me this was libncurses.so.5 & libncurses.so.5.9) Tested with gradle-bin-3.1 and gradle-3.4.1 (In reply to David from comment #12) > I had a similar issue with xterm-256color and gradle, I was able to resolve > this with sys-libs/ncurses-6.1-r2 enabling tinfo USE flag and making sure to > remove any old preserved libs (for me this was libncurses.so.5 & > libncurses.so.5.9) > > Tested with gradle-bin-3.1 and gradle-3.4.1 That fixed it for me as well, thank you for the hint. Tested with gradle-bin-4.7 from an overlay. https://github.com/gradle/gradle/issues/4426 The upstream has re-open the issue but there is further progress at the moment. I think this problem is an internal ncurses ABI problem. ncursers 5.9 cannot understand the newer xterm-256color terminfo. I took ncurses-6.1_p20190609.ebuild and converted it to ncurses-compat-6.1_p20190609.ebuild by copiimg the configure logic in 5.9 plus added --with-abi-version=5.9 and built that. Got new *.so.5 libs and now apps using *.so.5 libs understands xterm-256color If this new ncurses-compat pkg is 100 % ABI compatible against the older ncurses-compat-5.9 remains to be seen ... Created attachment 592886 [details]
ncurses-compat-6.1_p20190609.ebuild
This is my converted package
(In reply to Joakim Tjernlund from comment #16) > Created attachment 592886 [details] > ncurses-compat-6.1_p20190609.ebuild > > This is my converted package ncurses-compat-6.1_p20190609 is now in the tree Thanks a lot for ncurses-compat-6.1_p20190609! It really helped me with binary Gradle 6.4-20200409155744+0000 |