[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#347774: marked as done (does not handle resize on startup properly (same as #146210?))

Your message dated Wed, 23 Jan 2008 10:59:58 +0100
with message-id <20080123095958.GA13352@pcpool00.mathematik.uni-freiburg.de>
and subject line Xterm's tty resizing changed in 226
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: xterm
Version: 208-1
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

it appears as if that old bug has reappeared. When the windowmanager
gives back a different ConfigureNotify than what was initially
requested, the shell process needs to be sent a SIGWINCH.

   Simon

- -- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-amd64-k8
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)

Versions of packages xterm depends on:
ii  libc6                     2.3.5-11       GNU C Library: Shared libraries an
ii  libfontconfig1            2.3.2-1.1      generic font configuration library
ii  libfreetype6              2.1.10-1       FreeType 2 font engine, shared lib
ii  libice6                   6.9.0.dfsg.1-2 Inter-Client Exchange library
ii  libncurses5               5.5-1          Shared libraries for terminal hand
ii  libsm6                    6.9.0.dfsg.1-2 X Window System Session Management
ii  libx11-6                  6.9.0.dfsg.1-2 X Window System protocol client li
ii  libxaw8                   6.9.0.dfsg.1-2 X Athena widget set library
ii  libxext6                  6.9.0.dfsg.1-2 X Window System miscellaneous exte
ii  libxft2                   2.1.7-1        FreeType-based font drawing librar
ii  libxmu6                   6.9.0.dfsg.1-2 X Window System miscellaneous util
ii  libxrender1               1:0.9.0.2-1    X Rendering Extension client libra
ii  libxt6                    6.9.0.dfsg.1-2 X Toolkit Intrinsics
ii  xlibs-data                6.9.0.dfsg.1-2 X Window System client data
ii  zlib1g                    1:1.2.3-9      compression library - runtime

Versions of packages xterm recommends:
ii  xutils                    6.9.0.dfsg.1-2 X Window System utility programs

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iQCVAwUBQ8Z7EVYr4CN7gCINAQKV+QP8D6Crc3qqHtdfN06gFsDYiQD7/9YcGq+m
dyT09NOI+vQ62F1kEMRDfpjQ8j94sxV8VhChBDmHmqZtCe7jyO9OWr73lqhRMYCH
blqE1A3lZK/4kHIO9Zk6KB9K4jCmSfcJcmDFCitsJOV76m2JdHBmjBgdW53CncC1
K4i7YYNbF1s=
=Z1/o
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Package: xterm
Version: 226-1

Xterm's Changelog contains in the description of 226:

* modify logic which resets/updates the screensize on the child process side of the
  pseudo-terminal to do this only if a successful handshake was received, e.g., as
  determined by the waitForMap resource (prompted by reports by Emanuele Giaquinta
  and Bernhard R Link, but see also patch #177 and patch #159.

And I personally can no longer reproduce this. Thus I take the liberty to close
the two bug reports about this.

Hochachtungsvoll,
	Bernhard R. Link

P.S: Note that 228' Changelog contains more changes:

* amend changes to handshake in patch #226 to accommodate Solaris, which relies on
  the extra setting of the terminal size after I/O initialization. Do this by adding
  new resource ptySttySize, which is false for Linux and MacOS X, i.e., true for for
  Solaris and other SVR4 platforms, as well as FreeBSD (reports by David Wood, Renato
  Botelho).

So if the non-Linux architectures had the same bug, it might not be necessarily
fixed for those.

--- End Message ---
Reply to: