Bug#196679: marked as done (kdebase: all kde chars are boxes)
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; 8 Jun 2003 22:35:30 +0000
>From robb@alphalink.com.au Sun Jun 08 17:35:29 2003
Return-path: <robb@alphalink.com.au>
Received: from mail2.alphalink.com.au [202.161.124.194]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19P8l6-0000Ti-00; Sun, 08 Jun 2003 17:35:29 -0500
Received: from debian.me.null (d32-ps1-mel.alphalink.com.au [202.161.105.160])
by mail2.alphalink.com.au (8.12.9/8.9.3) with ESMTP id h58MZLk4010654
for <submit@bugs.debian.org>; Mon, 9 Jun 2003 08:35:23 +1000
Received: by debian.me.null (Postfix, from userid 1000)
id 126102D824; Mon, 9 Jun 2003 08:32:21 +1000 (EST)
From: me <rob21@linuxmail.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: kdebase: all kde chars are boxes
X-Mailer: reportbug 1.50
Date: Mon, 09 Jun 2003 08:32:21 +1000
Message-Id: <20030608223221.126102D824@debian.me.null>
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-4.8 required=4.0
tests=BAYES_10,FROM_ENDS_IN_NUMS,HAS_PACKAGE
version=2.53-bugs.debian.org_2003_05_24
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_05_24 (1.174.2.15-2003-03-30-exp)
Package: kdebase
Version: 4:3.1.2-1
Severity: important
Hi,
The only charactors in kde are box chars. For example logoff appears
as 6 box chars. I read on kde mailing lists that this is qt default
behaviour when it does not know what to do.
Rob.
-- System Information
Debian Release: 2.2
Architecture: i386
Kernel: Linux debian 2.4.21-rc1-ac3 #1 Fri May 2 17:51:55 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages kdebase depends on:
ii kappfinder 4:3.1.2-1 KDE Application Finder
ii kate 4:3.1.2-1 KDE Advanced Text Editor
ii kcontrol 4:3.1.2-1 KDE Control Center
ii kdebase-bin 4:3.1.2-1 KDE Base (binaries)
ii kdebase-data 4:3.1.2-1 KDE Base (shared data)
ii kdebase-kio-plugins 4:3.1.2-1 KDE I/O Slaves
ii kdeprint 4:3.1.2-1 KDE Print
ii kdesktop 4:3.1.2-1 KDE Desktop
ii kfind 4:3.1.2-1 KDE File Find Utility
ii khelpcenter 4:3.1.2-1 KDE Help Center
ii kicker 4:3.1.2-1 KDE Desktop Panel
ii klipper 4:3.1.2-1 KDE Clipboard
ii kmenuedit 4:3.1.2-1 KDE Menu Editor
ii konqueror 4:3.1.2-1 KDE's advanced File Manager, Web B
ii konqueror-nsplugins 4:3.1.2-1 Netscape plugin support for Konque
ii konsole 4:3.1.2-1 KDE X terminal emulator
ii kpager 4:3.1.2-1 KDE Desktop Pager
ii kpersonalizer 4:3.1.2-1 KDE Personalizer
ii ksmserver 4:3.1.2-1 KDE Session Manager
ii ksplash 4:3.1.2-1 KDE Splash Screen
ii ksysguard 4:3.1.2-1 KDE System Guard
ii ktip 4:3.1.2-1 Kandalf's Useful Tips
ii kwin 4:3.1.2-1 KDE Window Manager
ii libkonq4 4:3.1.2-1 Core libraries for KDE's file mana
---------------------------------------
Received: (at 196679-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: 196679-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: 12
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: