Am 19.06.2018 um 11:07 schrieb w...@chaos.in-kiel.de:
> I regularly connect (via mosh) to remote machine from my desktop and
> reattach to a "screen" there. For some time now, screen on the remote
> machine reports
>
> Cannot find terminfo entry for 'xterm-256color'.
>
> and quits.
>
> After some searching around the web and finding out that
>
> export TERM=xterm-color
>
> before connecting to the remote machine helps,
Not directly relevant for this bugreport, but you most likely do not
want to set $TERM to xterm-color as it lacks many features. A better
choice would be TERM=xterm.
> but not liking that
> workaround, I tried moving /lib/terminfo/x/xterm-256color aside and
> adding a symling xterm-256color -> xterm-color. This made the above
> misbehaviour disappear.
Just to be sure I understand the problem correctly: you did that on the
remote machine, right?
> I therefore guess the problem is not /lib/terminfo/x/xterm-256color
> not being found, but it being broken somehow, but I lack knowledge to
> investigate further.
The file is certainly not broken, unless it became corrupted on your
system, which is possible but not very likely. A more likely
explanation follows.
In ncurses 6.1 a new terminfo format has been introduced which is used
by the various *-256color entries, and older versions of the tinfo
library do not understand it. In the Debian package appropriate Breaks
were added to deal with incompatibilities, but if your screen package
uses a local version of the tinfo/ncurses library this won't help. I
suspect this might be the case here.
> Some more package versions:
>
> screen 4.6.2-1+b1
> libtinfo6 6.1+20180210-4
> ncurses-term 6.1+20180210-4
>
> If there's any further questions or test steps to try, I'll happily help.
Please show the output of these commands on the remote machine:
screen -v
which screen
ldd $(which screen)
TIA,
Sven
