Subject: Re: port-amd64/34282: console color is broken on amd64 when using pkgsrc/misc/screen on amd64
To: None <port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: Thomas Dickey <dickey@radix.net>
List: netbsd-bugs
Date: 10/04/2006 12:45:02
The following reply was made to PR port-amd64/34282; it has been noted by GNATS.

From: Thomas Dickey <dickey@radix.net>
To: George Georgalis <george@galis.org>
Cc: Thomas Dickey <dickey@radix.net>, gnats-bugs@NetBSD.org
Subject: Re: port-amd64/34282: console color is broken on amd64 when using pkgsrc/misc/screen on amd64
Date: Wed, 4 Oct 2006 08:43:34 -0400

 --wq9mPyueHGvFACwf
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Wed, Oct 04, 2006 at 11:56:08AM +0000, George Georgalis wrote:
 > On Wed, Oct 04, 2006 at 06:04:10AM -0400, Thomas Dickey wrote:
 > >On Tue, Oct 03, 2006 at 08:15:32PM +0000, George Georgalis wrote:
 > >> I've localized the problem to the .Xdefaults entry:
 > >
 > >The report was for "OOPS", which would come from an application running
 > >within xterm (or whatever terminal).  There's no mechanism that would
 > >make xterm send "OOPS" by itself that I can think of.
 >=20
 > My report was for ANY use of color control sequences (eg colorls,
 > vim, etc) within screen generate a literal "OOPS" instead, when
 > connecting to amd64.  Removing "xterm*colorRVMode: true" from
 > Xdefaults FIXES the problem. at the expense of disabling a
 > feature I want.
 
 But a termcap application can't tell if xterm has the resource set.
 It is the termcap application that sends the "OOPS".
 
 The likely explanation for the "OOPS" is mishandling of a truncated termcap,
 e.g., if some color information is missing.  NetBSD's termcap implementation
 substitutes an address for the missing information.  Recent discussion of t=
 his
 problem hints that the size of the address data is a factor, e.g., there co=
 uld
 be a buffer overflow due to the added bits (not a bug in xterm ;-).
 
 However, none of the comments made on the mailing lists have identified the
 problem other than the oblique comment that it has been fixed in some versi=
 on.
 (Since no analysis has been presented, it is unlikely that it is fixed).
 
 --=20
 Thomas E. Dickey
 http://invisible-island.net
 ftp://invisible-island.net
 
 --wq9mPyueHGvFACwf
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (SunOS)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQFFI6xwtIqByHxlDocRAg/NAJwIHTEO/NHnND+UlGYlftQjhoycugCdGs7T
 aRne6DLKsFr/pPjZp0F9k8E=
 =3Ziv
 -----END PGP SIGNATURE-----
 
 --wq9mPyueHGvFACwf--