Your message dated Sat, 6 Jan 2018 11:10:08 -0500
with message-id <20180106161008.bb2rjzt6wo425...@zeta.ryanak.ca>
and subject line Re: Bug#886465: rxvt-unicode: external 'screen' claims "Cannot
find terminfo entry for 'rxvt-unicode-256color'."
has caused the Debian Bug report #886465,
regarding rxvt-unicode: external 'screen' claims "Cannot find terminfo entry
for 'rxvt-unicode-256color'."
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
886465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rxvt-unicode
Version: 9.22-2, 9.22-3
Severity: important
Dear Maintainer,
After upgrading rxvt-unicode to 9.22-2, its TERM value has been changed from
'rxvt-unicode' to 'rxvt-unicode-256color'.
When I log in to a Debian server without ncurses-term installed, and try to
run 'screen' inside the server, it claims
> Cannot find terminfo entry for 'rxvt-unicode-256color'
and fails to start. Also 'less' claims
> WARNING: terminal is not fully functional
and works just like a dumb terminal.
Workaround: "export TERM='rxvt-unicode'" if your shell is bash
Personally I do not like this approach because I think the 'rxvt-unicode'
package should work well as 'rxvt-unicode' out of the box.
Regards,
--
YOSHINO Yoshihito <yy.y.ja...@gmail.com>
-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8),
LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages rxvt-unicode depends on:
ii base-passwd 3.5.44
ii libc6 2.25-6
ii libfontconfig1 2.12.6-0.1
ii libfreetype6 2.8.1-1
ii libgcc1 1:7.2.0-18
ii libgdk-pixbuf2.0-0 2.36.11-1
ii libglib2.0-0 2.54.2-5
ii libperl5.26 5.26.1-3
ii libstartup-notification0 0.12-5
ii libx11-6 2:1.6.4-3
ii libxft2 2.3.2-1+b2
ii libxrender1 1:0.9.10-1
ii ncurses-term 6.0+20171125-1
Versions of packages rxvt-unicode recommends:
ii fonts-dejavu 2.37-1
ii fonts-vlgothic [fonts-japanese-gothic] 20141206-4
rxvt-unicode suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
tags 886465 + wontfix
thanks
Hi,
Thanks for the bug report.
On Sat, Jan 06, 2018 at 09:12:27PM +0900, YOSHINO Yoshihito wrote:
> After upgrading rxvt-unicode to 9.22-2, its TERM value has been changed from
> 'rxvt-unicode' to 'rxvt-unicode-256color'.
This was deliberate, please see the rationale in bug #848284 [0].
> Workaround: "export TERM='rxvt-unicode'" if your shell is bash
> Personally I do not like this approach because I think the 'rxvt-unicode'
> package should work well as 'rxvt-unicode' out of the box.
You have two other options (described in urxvt(7)) which you might find more
palatable:
1) Set the resource
URxvt.termName: rxvt-unicode
2) Manually install the rxvt-unicode-256color entry on the remote host. Here
are the steps from urxvt(7), modified for your case:
REMOTE=remotesystem.domain
infocmp rxvt-unicode-256color | \
ssh $REMOTE 'export TMPF=`mktemp` && mkdir -p ~/.terminfo \
&& cat >${TMPF} && tic ${TMPF} && rm ${TMPF}'
Best wishes,
Ryan
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848284
--
|_)|_/ Ryan Kavanagh | GPG: 4E46 9519 ED67 7734 268F
| \| \ https://ryanak.ca/ | BD95 8F7B F8FC 4A11 C97A
signature.asc
Description: PGP signature
--- End Message ---
