Bug#89622: marked as done (session manager works with all dockapps except 'wmusic -w')
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; 14 Mar 2001 17:26:41 +0000
>From vaughan@tensor.nssl.noaa.gov Wed Mar 14 11:26:33 2001
Return-path: <vaughan@tensor.nssl.noaa.gov>
Received: from tensor.nssl.noaa.gov [129.15.67.219]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14dF2d-0006EX-00; Wed, 14 Mar 2001 11:26:31 -0600
Received: (from vaughan@localhost)
by tensor.nssl.noaa.gov (8.11.3/8.11.3/Debian 8.11.2-1) id f2EHQWQ21956;
Wed, 14 Mar 2001 11:26:32 -0600
Message-Id: <200103141726.f2EHQWQ21956@tensor.nssl.noaa.gov>
From: "Thomas E. Vaughan" <vaughan@tensor.nssl.noaa.gov>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: session manager works with all dockapps except 'wmusic -w'
X-Reportbug-Version: 1.14
X-Mailer: reportbug 1.14
Date: Wed, 14 Mar 2001 11:26:32 -0600
Delivered-To: submit@bugs.debian.org
Package: kdebase
Version: 4:2.1.0.1-2
Severity: normal
Although the KDE session manager remembers positions and command-line
arguments for wmMoonClock, mwWeather, wmtop, wmifs, wmmon, etc., it does
not handle wmusic properly. Unlike the other dock apps in debian, wmusic
links against libdockapp1 (or against a version of libdockapp distributed
with the upstream source). The wmusic author claims that all of the
properties necessary for session management are present. Further, wmusic
seems to be session managed properly under GNOME and WindowMaker. So there
seems to be a problem with the KDE session management.
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux tensor 2.4.2 #2 Tue Feb 27 10:23:02 CST 2001 i686
Versions of packages kdebase depends on:
ii debianutils 1.15 Miscellaneous utilities specific t
ii kdebase-libs 4:2.1.0.1-2 KDE libraries amd modules for kdeb
ii kdelibs3 4:2.1.0.1-2 KDE core libraries (runtime files)
ii kdelibs3-crypto 4:2.1-final-1 KDE core libraries (Crypto Modules
ii libc6 2.2.2-1 GNU C Library: Shared libraries an
ii libjpeg62 6b-1.3 The Independent JPEG Group's JPEG
ii libkonq3 4:2.1.0.1-2 Core libraries for KDE's file mana
ii libpam-modules 0.72-16 Pluggable Authentication Modules f
ii libpam0g 0.72-16 Pluggable Authentication Modules l
ii libpng2 1.0.8-1 PNG library - runtime
ii libqt2-gl 2:2.3.0-final-1 Qt GUI Library (Open GL Version).
ii libqt2-gl [libqt2] 2:2.3.0-final-1 Qt GUI Library (Open GL Version).
ii libstdc++2.10-glibc2. 1:2.95.3-6 The GNU stdc++ library
ii libutahglx1 [libgl1] 0.0-cvs-20010214-1 Utah-GLX - shared library required
ii xfree86-common 4.0.2-7 X Window System (XFree86) infrastr
ii xlibs 4.0.2-7 X Window System client libraries
ii zlib1g 1:1.1.3-12 compression library - runtime
---------------------------------------
Received: (at 89622-done) by bugs.debian.org; 17 Jan 2005 02:03:31 +0000
>From christopher.martin@utoronto.ca Sun Jan 16 18:03:31 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: 89622-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: 42
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: