Your message dated Mon, 20 Jun 2005 21:54:34 +0200
with message-id <[EMAIL PROTECTED]>
and subject line [Fwd: Re: Status?]
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; 31 Jan 2002 14:13:11 +0000
>From [EMAIL PROTECTED] Thu Jan 31 08:13:11 2002
Return-path: <[EMAIL PROTECTED]>
Received: from (sentinel.licquia.org) [24.183.88.187] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 16WHxe-0004sw-00; Thu, 31 Jan 2002 08:13:10 -0600
Received: from server1.internal.licquia.org (server.internal.licquia.org 
[192.168.50.3])
        by sentinel.licquia.org (Postfix) with ESMTP id 888C745003
        for <[EMAIL PROTECTED]>; Thu, 31 Jan 2002 09:13:10 -0500 (EST)
Received: by server1.internal.licquia.org (Postfix, from userid 1000)
        id 7AADD2C1602; Thu, 31 Jan 2002 09:13:10 -0500 (EST)
Date: Thu, 31 Jan 2002 09:13:10 -0500
From: Jeff Licquia <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: [CUPS] Problems when CUPS
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.3.25i
X-Debbugs-CC: [EMAIL PROTECTED], Neil Durant <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]

Package: cupsys
Version: 1.1.12-4
Severity: normal

On Thu, Jan 31, 2002 at 07:57:02AM -0500, Neil Durant wrote:
> I've recently set up CUPS to work with my HP Laserjet 1100, and have 
> successfully printed postscript files with it.  However, if I try to 
> print virtually anything other than a postscript file, it fails to be 
> printed and I get the following error in the log:
> 
> I [...] Job 108 queued on 'LaserJet' by 'neil'.
> I [...] Listening to 0:631
> I [...] Configured for up to 100 clients.
> I [...] LoadPPDs: Read "/etc/cups/ppds.dat", 1530 PPDs...
> I [...] LoadPPDs: No new or changed PPDs...
> E [...] Unable to convert file 0 to printable format for job 108!
> 
> Subsequently, even if I try to print a postscript file, nothing is 
> printed, and I get a similar message.  The only way I have found to get 
> printing working again is through the web configuration interface, going 
> to "Printers", and modifying my printer, just clicking "Continue" all 
> the way through until it's fully reconfigured (with identical settings). 
> Printing then subsequently works fine again for postscript.
> 
> Sometimes I also find the CUPS daemon has stopped running, and so I have 
> to restart it manually.
> 
> I'm using CUPS 1.1.12-4 with cupsomatic-ppd / foomatic, on a Debian 
> Woody system, and they were installed by apt-get.
> 
> If anyone could shed some light on this, I would be most grateful!!!!!

I will take a look at this as soon as I can (probably this weekend).

I've submitted your message as a bug in Debian's bug tracking system.
Please be sure to send at least a CC to the bug report (the address
will look like <number>@bugs.debian.org), so I can keep track of any
feedback or other issues better.

You should also be able to see any new information by pointing a
browser at http://bugs.debian.org/<number>, or
http://bugs.debian.org/cupsys for other bugs in Debian's cupsys
packages.

---------------------------------------
Received: (at 131699-done) by bugs.debian.org; 20 Jun 2005 19:57:28 +0000
>From [EMAIL PROTECTED] Mon Jun 20 12:57:28 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mailservice.tudelft.nl [130.161.131.5] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DkSOe-0007sw-00; Mon, 20 Jun 2005 12:57:28 -0700
Received: from localhost (localhost [127.0.0.1])
        by rav.antivirus (Postfix) with ESMTP id 1AD49800CF
        for <[EMAIL PROTECTED]>; Mon, 20 Jun 2005 21:56:58 +0200 (CEST)
Received: from localhost (x118.decis.nl [130.161.177.118])
        by mx4.tudelft.nl (Postfix) with ESMTP id 8873A800C5
        for <[EMAIL PROTECTED]>; Mon, 20 Jun 2005 21:56:57 +0200 (CEST)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
        by localhost (Postfix) with ESMTP id 8891F10DD0F
        for <[EMAIL PROTECTED]>; Mon, 20 Jun 2005 21:54:35 +0200 (CEST)
Subject: [Fwd: Re: Status?]
From: Thomas Hood <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Type: text/plain
Date: Mon, 20 Jun 2005 21:54:34 +0200
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at tudelft.nl
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: 

Thanks for the update.  :)

-------- Forwarded Message --------
From: Neil Durant <[EMAIL PROTECTED]>
To: Thomas Hood <[EMAIL PROTECTED]>
Subject: Re: Status?
Date: Mon, 20 Jun 2005 20:46:07 +0100
Hi Thomas,

Thomas Hood wrote:
> Neil Durant originally wrote:
> > I've recently set up CUPS to work with my HP Laserjet 1100, and have 
> > successfully printed postscript files with it.  However, if I try to 
> > print virtually anything other than a postscript file, it fails to be 
> > printed and I get the following error in the log:
> 
> What is the status of this bug three years later?

For a while I did all my printing via postscript files, so it wasn't a
problem.  Then a while ago I printed things other than postscript files,
and everything just worked fine, so I guess the bug got fixed somewhere
along the line!

Best regards,

Neil
-- 
Thomas Hood <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to