Your message dated Tue, 23 Aug 2005 22:45:42 +1000
with message-id <[EMAIL PROTECTED]>
and subject line fixed font problem now fixed
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; 5 Jul 2004 16:25:43 +0000
>From [EMAIL PROTECTED] Mon Jul 05 09:25:43 2004
Return-path: <[EMAIL PROTECTED]>
Received: from rwcrmhc13.comcast.net [204.127.198.39]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BhWHn-00051v-00; Mon, 05 Jul 2004 09:25:43 -0700
Received: from pcp483125pcs.oakrdg01.tn.comcast.net
(pcp04534741pcs.oakrdg01.tn.comcast.net[68.34.212.107])
by comcast.net (rwcrmhc13) with SMTP
id <20040705162508015003f215e>
(Authid: freelsjd);
Mon, 5 Jul 2004 16:25:10 +0000
Subject: xprint server not starting for Debian/Sid system
From: "James D. Freels" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Content-Type: text/plain
Organization: self
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6
Date: Mon, 05 Jul 2004 12:25:01 -0400
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.1 required=4.0 tests=BAYES_44,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: xprt-common
Version: 0.0.9.final-3
Upon starting xprint with /etc/init.d/xprint, I receive the following
error message on a current Debian/Sid system:
fea_home# /etc/init.d/xprint start
/etc/init.d/xprint: Old server registry found, cleaning-up...
Stopping Xprint servers: Xprt.
Starting Xprint servers: Xprt.
However, the Xprt does not keep running, and I do not know why. As a
result, I cannot print from mozilla which now requires xprint and no
longer support Postscript/Default as a printer type.
I am using lprng on this machine because cups is not support with the
Lexmark z23 printer (which is supposed to be Linux compatible).
The lpr command is working fine. I have added the following to
the end of /etc/Xprint/en_US/print/attributes/printer:
#
# added by jdf 7/5/2004 for fea_home
#
*xp-spooler-command: /usr/bin/lpr -Plp -K%copy-count%
I cannot even print to a file as a work around until the server is
running !
Found no similar problem listed on debian-user
--
James D. Freels, Ph.D.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
---------------------------------------
Received: (at 257731-done) by bugs.debian.org; 23 Aug 2005 12:45:47 +0000
>From [EMAIL PROTECTED] Tue Aug 23 05:45:47 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smta09.mail.ozemail.net [203.103.165.130]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E7Y9z-0002iE-00; Tue, 23 Aug 2005 05:45:47 -0700
Received: from pug.anu.edu.au ([203.103.48.11]) by smta09.mail.ozemail.net
with ESMTP
id <[EMAIL PROTECTED]>;
Tue, 23 Aug 2005 12:45:45 +0000
Received: from drew by pug.anu.edu.au with local (Exim 4.52)
id 1E7Y9u-0002Az-GU; Tue, 23 Aug 2005 22:45:42 +1000
Subject: fixed font problem now fixed
From: Drew Parsons <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: The Debian Project
Date: Tue, 23 Aug 2005 22:45:42 +1000
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3
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-Level:
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-CrossAssassin-Score: 2
I believe the "could not open default font 'fixed'" problem is now
solved, so I'm closing these bugs.
The bug seems to be occuring when fonts.alias or fonts.dir is present in
an otherwise empty directory. The file references the "fixed" font, but
the font ain't there. Solution is to delete (or repair) the broken font
directory.
Drew
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
