Bug#197425: marked as done (kicker: Clock applet doesn't like Central Daylight Time)
Your message dated Sun, 16 Jan 2005 21:03:18 -0500
with message-id <200501162103.24654.christopher.martin@utoronto.ca>
and subject line Bug no longer relevant, so closing
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 2003 00:53:42 +0000
>From alvanson@shaw.ca Sat Jun 14 19:53:34 2003
Return-path: <alvanson@shaw.ca>
Received: from h24-66-4-21.wp.shawcable.net (adrastea) [24.66.4.21]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19RLm1-0007no-00; Sat, 14 Jun 2003 19:53:33 -0500
Received: from alvanson by adrastea with local (Exim 4.20)
id 19RLlZ-0000SC-Sl; Sat, 14 Jun 2003 19:53:05 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Evan A. Thompson" <alvanson@shaw.ca>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: kicker: Clock applet doesn't like Central Daylight Time
X-Mailer: reportbug 2.10.1
Date: Sat, 14 Jun 2003 19:53:05 -0500
Message-Id: <E19RLlZ-0000SC-Sl@adrastea>
Sender: Evan Thompson <alvanson@adrastea>
X-BadReturnPath: alvanson@adrastea rewritten as alvanson@shaw.ca
using "From" header
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0
tests=BAYES_20,HAS_PACKAGE
version=2.53-bugs.debian.org_2003_06_10
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_06_10 (1.174.2.15-2003-03-30-exp)
Package: kicker
Version: 4:3.1.2-1
Severity: normal
I'm not very sure which package the normal KDE clock applet is in, but
however:
The clock on my panel just doesn't want to stick with CDT. Right now,
it is 19:51, and `date` verifies that the OS itself knows what time it
is. However, my KDE clock says it's 22:51 yet is set to "Local
Timezone."
No other program seems to have this trouble.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux adrastea 2.4.20-ck #1 Sun May 4 15:26:38 CDT 2003 i686
Locale: LANG=en_CA, LC_CTYPE=en_CA
Versions of packages kicker depends on:
ii kdelibs4 4:3.1.2-2 KDE core libraries
ii libart-2.0-2 2.3.12-1 Library of functions for 2D graphi
ii libc6 2.3.1-17 GNU C Library: Shared libraries an
ii libfam0c102 2.6.10-1 client library to control the FAM
ii libgcc1 1:3.3-3 GCC support library
ii libkonq4 4:3.1.2-1 Core libraries for KDE's file mana
ii libpng12-0 1.2.5.0-4 PNG library - runtime
ii libqt3c102-mt 3:3.1.1-8 Qt GUI Library (Threaded runtime v
ii libstdc++5 1:3.3-3 The GNU Standard C++ Library v3
ii xlibs 4.2.1-8 X Window System client libraries
ii zlib1g 1:1.1.4-12 compression library - runtime
-- no debconf information
---------------------------------------
Received: (at 197425-done) by bugs.debian.org; 17 Jan 2005 02:03:29 +0000
>From christopher.martin@utoronto.ca Sun Jan 16 18:03:29 2005
Return-path: <christopher.martin@utoronto.ca>
Received: from tomts25-srv.bellnexxia.net [209.226.175.188]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CqMEo-0002G9-00; Sun, 16 Jan 2005 18:03:26 -0800
Received: from [192.168.0.100] ([70.49.17.55])
by tomts25-srv.bellnexxia.net
(InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP
id <20050117020322.SUTX25979.tomts25-srv.bellnexxia.net@[192.168.0.100]>;
Sun, 16 Jan 2005 21:03:22 -0500
From: Christopher Martin <christopher.martin@utoronto.ca>
Reply-To: Christopher Martin <christopher.martin@utoronto.ca>
To: 89622-done@bugs.debian.org,
107756-done@bugs.debian.org,
116585-done@bugs.debian.org,
121344-done@bugs.debian.org,
121933-done@bugs.debian.org,
123535-done@bugs.debian.org,
131545-done@bugs.debian.org,
145376-done@bugs.debian.org,
156949-done@bugs.debian.org,
193124-done@bugs.debian.org,
201189-done@bugs.debian.org,
203709-done@bugs.debian.org,
219906-done@bugs.debian.org,
237042-done@bugs.debian.org,
243956-done@bugs.debian.org,
253700-done@bugs.debian.org,
180352-done@bugs.debian.org,
194398-done@bugs.debian.org,
196679-done@bugs.debian.org,
196723-done@bugs.debian.org,
197369-done@bugs.debian.org,
197425-done@bugs.debian.org,
198152-done@bugs.debian.org,
198306-done@bugs.debian.org,
200314-done@bugs.debian.org,
202685-done@bugs.debian.org,
205009-done@bugs.debian.org,
207556-done@bugs.debian.org,
209305-done@bugs.debian.org,
211542-done@bugs.debian.org,
212925-done@bugs.debian.org,
216073-done@bugs.debian.org,
216929-done@bugs.debian.org,
217300-done@bugs.debian.org,
217717-done@bugs.debian.org,
222662-done@bugs.debian.org,
227199-done@bugs.debian.org,
231688-done@bugs.debian.org,
232501-done@bugs.debian.org,
234111-done@bugs.debian.org,
234656-done@bugs.debian.org,
238813-done@bugs.debian.org
Subject: Bug no longer relevant, so closing
Date: Sun, 16 Jan 2005 21:03:18 -0500
User-Agent: KMail/1.7.1
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <200501162103.24654.christopher.martin@utoronto.ca>
Delivered-To: 197425-done@bugs.debian.org
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: 15
Hello,
This bug is being closed because of its age and the vanishingly small
chance that it is still relevant to the current KDE packages, as it was
clearly since fixed, a random unreproducible bug that never had enough of
a follow-up to be useful, or else was forwarded upstream, where it was
marked fixed some time ago.
In case I'm mistaken, please do re-open the bug report in question, and
explain how the report is still relevant.
Thanks,
Christopher Martin
Reply to: