Your message dated Sat, 10 Sep 2005 13:02:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#324527: bash: does not propagete SIGWINCH
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 22 Aug 2005 15:56:20 +0000
>From [EMAIL PROTECTED] Mon Aug 22 08:56:20 2005
Return-path: <[EMAIL PROTECTED]>
Received: from atrey.karlin.mff.cuni.cz [195.113.31.123] (postfix)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E7Eeq-0002ZD-00; Mon, 22 Aug 2005 08:56:20 -0700
Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 11501)
id 44FF34B40BD; Mon, 22 Aug 2005 17:55:55 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Miroslav Rudisin <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: bash: does not propagete SIGWINCH
X-Mailer: reportbug 3.8
Date: Mon, 22 Aug 2005 17:55:55 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: bash
Version: 2.05b-26
Severity: normal
Resizing terminal window (remote login with ssh) does not emit SIGWINCH to
active application (mc, mutt, ...). Only environment is updated (stty -a). This
could be problem in another system component, because some other shells (dash,
sash) does not work too. But I found others (ksh, tcsh, zsh) works well. It
happened on two indenpendent machines right after upgrade.
Resizing terminal works in this execution ordering
* ssh -> tcsh (login shell) -> (app)
* ssh -> bash -> tcsh -> (app)
* ssh -> bash -> tcsh -> bash -> (app)
But does not in this
* ssh -> bash (login shell) -> (app)
* ssh -> bash -> bash -> (app)
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.31-rc1
Locale: LANG=C, LC_CTYPE=cs_CZ (charmap=ISO-8859-2)
Versions of packages bash depends on:
ii base-files 3.1.2 Debian base system miscellaneous f
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libncurses5 5.4-4 Shared libraries for terminal hand
ii passwd 1:4.0.3-31sarge5 change and administer password and
-- no debconf information
---------------------------------------
Received: (at 324527-done) by bugs.debian.org; 10 Sep 2005 11:02:43 +0000
>From [EMAIL PROTECTED] Sat Sep 10 04:02:42 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EE386-0006oi-00; Sat, 10 Sep 2005 04:02:42 -0700
Received: from mailhost.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.17.13])
by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id NAA08544;
Sat, 10 Sep 2005 13:02:40 +0200 (MEST)
Received: from localhost (localhost [127.0.0.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id D1C6CFD4D;
Sat, 10 Sep 2005 13:02:39 +0200 (MEST)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
id 23307-29; Sat, 10 Sep 2005 13:02:38 +0200 (MEST) 11332
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP;
Sat, 10 Sep 2005 13:02:38 +0200 (MEST)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id j8AB2ch8006218;
Sat, 10 Sep 2005 13:02:38 +0200 (MEST)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Sat, 10 Sep 2005 13:02:38 +0200
To: Miroslav Rudisin <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: Bug#324527: bash: does not propagete SIGWINCH
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
That's documented. Please use
shopt -s checkwinsize
Miroslav Rudisin writes:
> Package: bash
> Version: 2.05b-26
> Severity: normal
>
> Resizing terminal window (remote login with ssh) does not emit SIGWINCH to
> active application (mc, mutt, ...). Only environment is updated (stty -a).
> This could be problem in another system component, because some other shells
> (dash, sash) does not work too. But I found others (ksh, tcsh, zsh) works
> well. It happened on two indenpendent machines right after upgrade.
>
> Resizing terminal works in this execution ordering
> * ssh -> tcsh (login shell) -> (app)
> * ssh -> bash -> tcsh -> (app)
> * ssh -> bash -> tcsh -> bash -> (app)
>
> But does not in this
> * ssh -> bash (login shell) -> (app)
> * ssh -> bash -> bash -> (app)
>
> -- System Information:
> Debian Release: 3.1
> Architecture: i386 (i686)
> Kernel: Linux 2.4.31-rc1
> Locale: LANG=C, LC_CTYPE=cs_CZ (charmap=ISO-8859-2)
>
> Versions of packages bash depends on:
> ii base-files 3.1.2 Debian base system miscellaneous
> f
> ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries
> an
> ii libncurses5 5.4-4 Shared libraries for terminal
> hand
> ii passwd 1:4.0.3-31sarge5 change and administer password
> and
>
> -- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
