Your message dated Sat, 23 Apr 2005 03:33:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#305955: fixed in ratpoison 1.3.0-6
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; 23 Apr 2005 04:30:33 +0000
>From [EMAIL PROTECTED] Fri Apr 22 21:30:33 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl254-118-016.nyc1.dsl.speakeasy.net (mudskipper.vireo.org) 
[216.254.118.16] 
        by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
        id 1DPCHZ-0003d7-00; Fri, 22 Apr 2005 21:30:31 -0700
Received: from stew by cuttle with local (Exim 4.34)
        id 1DPBcZ-0004uL-LS; Fri, 22 Apr 2005 23:47:55 -0400
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Mike O'Connor <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: tmpwm puts ratpoison into an infinite loop
X-Mailer: reportbug 3.2
Date: Fri, 22 Apr 2005 23:47:55 -0400
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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: ratpoison
Version: 1.3.0-5
Severity: normal

If you try to use the tmpwm command but pass it as an argument, a path
to a non-existant file, ratpoison goes into an infinite loop waiting for
the child process (which was never started) to exit.  

This is easily fixed by this simple patch:

diff src/actions.c.orig src/actions.c
3252c3252
<     } while (child != pid);
---
>     } while ((child != -1) && (child != pid));

I'm forarding a patch upstream as well.

-stew


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages ratpoison depends on:
ii  libc6                    2.3.2.ds1-20    GNU C Library: Shared libraries an
ii  libreadline5             5.0-10          GNU readline and history libraries
ii  libx11-6                 4.3.0.dfsg.1-10 X Window System protocol client li
ii  libxext6                 4.3.0.dfsg.1-10 X Window System miscellaneous exte
ii  xlibs                    4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu

-- no debconf information

---------------------------------------
Received: (at 305955-close) by bugs.debian.org; 23 Apr 2005 07:45:40 +0000
>From [EMAIL PROTECTED] Sat Apr 23 00:45:40 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DPFKe-0000FA-00; Sat, 23 Apr 2005 00:45:40 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DPF8k-0006U4-00; Sat, 23 Apr 2005 03:33:22 -0400
From: Jonathan Walther <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#305955: fixed in ratpoison 1.3.0-6
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sat, 23 Apr 2005 03:33:22 -0400
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-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
X-Spam-Level: 

Source: ratpoison
Source-Version: 1.3.0-6

We believe that the bug you reported is fixed in the latest version of
ratpoison, which is due to be installed in the Debian FTP archive:

ratpoison_1.3.0-6.diff.gz
  to pool/main/r/ratpoison/ratpoison_1.3.0-6.diff.gz
ratpoison_1.3.0-6.dsc
  to pool/main/r/ratpoison/ratpoison_1.3.0-6.dsc
ratpoison_1.3.0-6_i386.deb
  to pool/main/r/ratpoison/ratpoison_1.3.0-6_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Walther <[EMAIL PROTECTED]> (supplier of updated ratpoison package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


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

Format: 1.7
Date: Sat, 23 Apr 2005 00:15:52 -0700
Source: ratpoison
Binary: ratpoison
Architecture: source i386
Version: 1.3.0-6
Distribution: unstable
Urgency: low
Maintainer: Jonathan Walther <[EMAIL PROTECTED]>
Changed-By: Jonathan Walther <[EMAIL PROTECTED]>
Description: 
 ratpoison  - Simple window manager with no fat library dependencies
Closes: 305955
Changes: 
 ratpoison (1.3.0-6) unstable; urgency=low
 .
   * Applied Mike O'Connor's fix for tmpwm race.  Closes: #305955
Files: 
 6861d7842037a071ae489eed2b150b20 825 x11 extra ratpoison_1.3.0-6.dsc
 b744b3830f87a50d8109fbf926589e19 24731 x11 extra ratpoison_1.3.0-6.diff.gz
 82d677620fc16de8def8f3aa48efcbbb 116366 x11 extra ratpoison_1.3.0-6_i386.deb

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

iQCVAwUBQmn2jcK9HT/YfGeBAQK/CwQAl18CJ2KsqKGZVtxLTFxHMVPAluk1vO1I
+Krlh2g1ZU7tUCRCMeyzriAU3cgSb3U/MG6ujr/wr3J0a4mC8VM39EP4C/rl+mU/
c9HHNkL2v6TS59kxnHNeGxPcWMF1f7kYlQ+brQOK9LINl4mBJxzMnNBSivGsT7tD
Q/VQuBU4mPw=
=4Hq8
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to