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

Bug#116286: marked as done (CUPS race condition with socket:// method [Fwd: cups ordering..])

Your message dated Sun, 1 Jun 2008 23:09:06 +0200
with message-id <20080601210906.GB6509@piware.de>
and subject line Cleaning up old bug reports
has caused the Debian Bug report #116286,
regarding CUPS race condition with socket:// method [Fwd: cups ordering..]
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.)


-- 
116286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=116286
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cupsys
Version: 1.1.10-3
Apparently CUPS makes seperate connections to the printer for the cover page and actual job when you use the socket method. As a result, if multiple users connect to a given printer with the socket:// method, there is race condition where another job can slip in between the cover page and the job it goes with.
The solution would be to make one connection to the printer and then send both the cover page and the print job over it. 

-------- Original Message --------
Subject: cups ordering..
Date: Thu, 18 Oct 2001 10:09:52 -0400
To: bristucc@sw.starentnetworks.com



Just had an interesting thing happen...

I was printing from linux, someone else was printing from windows..

and they were printed in this order:

my cover page
his cover page
his pages
my pages


is cups sending the job as two parts?

--- End Message ---
--- Begin Message --- 
Dear bug submitter,

This bug was reported against a very old version of cups (older than
in the current stable Debian version "Etch"). About a year ago,
Martin-Eric Racine asked for feedback whether the bug still applied to
the current Debian Etch version, but we did not get any feedback. In
order to not keep around old, hardware-specific, and inactive bugs
around forever, I close this bug now.

Please report back if you still experience the problem with the
current version in Etch; if you can test Lenny/unstable, that would be
highly appreciated, of course. I will reopen this bug then.

Thank you for your report!

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: