Ubuntu
linux package

  1. Bug #213081
  2. Comment #59

Comment 59 for bug 213081

Revision history for this message
Brian Burch (brian-pingtoo) wrote : Re: [Bug 213081] Re: CUPS does not print to LPD printer

Stefan Bader wrote:
> Thanks you for your report. However I think you should create a new one against
> cups. The bug here was about some TCP/IP issues that could not be solved with
> an increased timeout.
>
> That said, Brian, how are you feeling about this? As the exact reason could not
> be pinpointed and probably is more than could be argued to backport into a
> released version and IIRC you had it solved with Intrepid, should we close this
> one?

Hi, Stefan. I thought you had lost interest in this bug because I
haven't heard anything for several months. I still have all my notes,
but couldn't get further without help.

Here is the current situation as far as I see it...

1. The latest Intrepid kernel really does have the TCP/IP fix that
resolves my original problem.

2. The latest Hardy kernel is probably still broken - I have followed
your kernel fixes (especially TCP/IP) and haven't spotted anything that
looked relevant. However, I haven't run a test to confirm my beliefs
because....

3. The bypass I reported with the bug definitely works with the latest
Hardy kernel, so my Hardy systems (I still have a couple) run fine with
my printer.

4. Menno's problem does not sound like mine - if a print job was big
enough to stall, then it would never complete. Even a reboot would leave
the job queued and printing would hang again. Besides, he is using the
latest Intrepid kernel, where the bug is fixed (point 1 above).

I think Menno should open a new bug report - perhaps stating that it is
definitely NOT a duplicate of 213081.

I'm not sure what to do about 213081. It is fixed in Intrepid, but it
was reported against Hardy which is an LTS release with another year or
so of life. I think the circumvention is fine - do you have a bug status
something like "bypass available"?

I agree with Leann's original thought that we shouldn't waste a lot of
time back-porting the Intrepid fix. I was prepared to research the code
differences, but I couldn't get the tools to work and Leann didn't reply
to my questions. If you think it is important enough to help me get
started, then I'll give it another try.

Regards,

Brian