[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#473888: marked as done (cups does not print multi file jobs remotely)

Your message dated Wed, 2 Apr 2008 11:38:38 +0200
with message-id <20080402093838.GE9007@piware.de>
and subject line Re: [Pkg-cups-devel] Bug#473888: cups does not print multi file jobs remotely
has caused the Debian Bug report #473888,
regarding cups does not print multi file jobs remotely
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
473888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473888
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cupsys
Version: 1.2.7-4etch3
Severity: Important

Severity is important, because "Key functionality is not working" is set in 
the corresponding CUPS bug tracking system. see below.


echo first file | mpage > first.ps
echo second file | mpage > second.ps

on a machine that is running cups locally and the printers are attached 
locally, you can do:

lp first.ps second.ps

and both files get printed.


but let's say you have 2 machines. Both are running cups. they are connected 
by browsing. the server machine has the printer attached locally. now on the 
client you do

lp first.ps second.ps

just nothing happens. he sais that a job is created, but nothing happens.
if instead you do

lp first.ps
lp second.ps

then both get printed correctly.

the same issue applies if you print your jobs with kprinter from the kde 
project and probably all other cups printing interfaces.

on this page (CUPS STR #2673) you see a report about that problem.
http://www.cups.org/str.php?L2673

the things described there show exactly the same phenomenon. also the logfile 
they show there closely matches the one i have. the IPP backend gets not even 
started.

--- End Message ---
--- Begin Message --- 
Version: 1.3.6-1

I close this bug in unstable/testing, it is fixed there. I still leave
it open in Etch.

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: