Your message dated Sun, 13 Mar 2005 17:55:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Check if the bug persists in the new version
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; 15 Jun 2002 00:16:01 +0000
>From [EMAIL PROTECTED] Fri Jun 14 19:16:01 2002
Return-path: <[EMAIL PROTECTED]>
Received: from houseofdistraction.com [206.63.251.121]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 17J1EX-0005zf-00; Fri, 14 Jun 2002 19:16:01 -0500
Received: from (chubby.vnw.com) [216.220.192.132]
by houseofdistraction.com with esmtp (Exim 3.12 #1 (Debian))
id 17J1ET-0001kl-00; Fri, 14 Jun 2002 17:15:57 -0700
Received: from jeffb by chubby.vnw.com with local (Exim 3.35 #1 (Debian))
id 17J1Dy-0007MG-00; Fri, 14 Jun 2002 17:15:26 -0700
From: [EMAIL PROTECTED]
Subject: xscreensaver: xscreensaver corrupts the xscreensaver image directory
setting at startup
To: [EMAIL PROTECTED]
X-Mailer: bug 3.3.10.1
Message-Id: <[EMAIL PROTECTED]>
Sender: Jeff <[EMAIL PROTECTED]>
Date: Fri, 14 Jun 2002 17:15:26 -0700
Delivered-To: [EMAIL PROTECTED]
Package: xscreensaver
Version: 3.34-3
Severity: normal
It changes the imageDirectory entry from a valid directory to
imageDirectory: �&[EMAIL PROTECTED]&[EMAIL PROTECTED]
I can change it back in the control panel and it writes it back out but then
next time it starts up it recorrupts it.
-- System Information
Debian Release: 3.0
Kernel Version: Linux chubby.vnw.com 2.4.18-chubby03 #1 Tue May 28 09:06:26 PDT
2002 i686 unknown
Versions of the packages xscreensaver depends on:
ii libc6 2.2.5-6 GNU C Library: Shared libraries and Timezone
ii libpam0g 0.72-35 Pluggable Authentication Modules library
ii xlibs 4.1.0-17 X Window System client libraries
ii xscreensaver-g 3.34-3 GNOME binaries for xscreensaver
xscreensaver-nognome Not installed or no info
---------------------------------------
Received: (at 150031-done) by bugs.debian.org; 13 Mar 2005 16:55:04 +0000
>From [EMAIL PROTECTED] Sun Mar 13 08:55:04 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.charite.de [160.45.207.131]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DAWMp-0003B2-00; Sun, 13 Mar 2005 08:55:03 -0800
Received: from postamt.charite.de (postamt-ext.charite.de [160.45.207.132])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
by mail.charite.de (Postfix) with ESMTP id 13D112209DD;
Sun, 13 Mar 2005 17:55:06 +0100 (CET)
Received: by postamt.charite.de (Postfix, from userid 7945)
id 9C1CE220A97; Sun, 13 Mar 2005 17:55:00 +0100 (CET)
Date: Sun, 13 Mar 2005 17:55:00 +0100
From: Ralf Hildebrandt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Check if the bug persists in the new version
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: amavisd-new at charite.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-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 45
Current are 3.34 and/or 4.16, and since you filed the bug against an
older version I'd like to ask you to verify if the bug persists in the
new version as well.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
