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

Bug#478062: marked as done (Kernel >2.6.22.3-amd64 will not print to cups network printer)

Your message dated Sun, 21 Dec 2008 01:12:33 +0100
with message-id <20081221001233.GA14513@galadriel.inutil.org>
and subject line Re: Fix FRTO+NewReno problem (Was: Re: This has a work around)
has caused the Debian Bug report #478062,
regarding Kernel >2.6.22.3-amd64 will not print to cups network printer
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.)


-- 
478062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478062
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package:  linux-image-2.6.24-1-amd64

Version:  2.6.24-6
no errors are logged in /var/log/cups. I print to a network printer via cups in lpd://192.168.200.150/lpt1 format. Printer is Samsung ML1430 w/Hawkings Tech. HPS1P 10/100M parallel Print Server.
No print jobs are completed when I send them to the printer in any kernel image > 2.6.24-1-amd64. I even compiled my own from 2.6.25 sources (to by pass any debian patch that may be the problem) from kernel.org. Same issue.
I once left the printer/job run for hours and received a "job timed out" error from the printer. Network monitoring indicates the job is being sent, just very very slowly (grellm network graph).
Prints just fine in 2.6.22-3-amd64 kernel. Worked up until about a month ago in stable and unstable with all available linux-images-2.6-amd64. Problem also seen in ubuntu.
cupsys 1.3.7-5 cupsys-common 1.3.7-5 cupsys-bsd 1.3.7-5 libcupsimage2 1.3.7-5 
libcupsys2              1.3.7-5
I am out of trouble shooting steps to run. I can and will do any tests you suggest. I have run stable, testing and unstable and all show the same behavior. Ubuntu 7.10 works, 8.04 does not. Same package loadout with 2.6.22-3-amd64 works, anything greater does not. I suspect what ever the cause is upstream as 2.6.25 sources compiled with kpkg also does not work. 
/var/log/cups/error.log:

root@dam-main:/home/damon# tail -f /var/log/cups/error_log
E [26/Apr/2008:11:07:59 -0400] CUPS-Add-Modify-Printer: Unauthorized
E [26/Apr/2008:11:08:01 -0400] CUPS-Add-Modify-Printer: Unauthorized
E [26/Apr/2008:11:30:58 -0400] Purge-Jobs: Unauthorized
E [26/Apr/2008:11:30:59 -0400] Purge-Jobs: Unauthorized
E [26/Apr/2008:11:33:22 -0400] Purge-Jobs: Unauthorized
E [26/Apr/2008:11:33:52 -0400] PID 11861 (/usr/lib/cups/backend/lpd) stopped with status 1! 
E [26/Apr/2008:11:35:28 -0400] Cancel-Job: Unauthorized

-----------------end--------------------
^the unauthorized error is from adding the cups printer from the web URL. the lpd error is from resetting the printer, and restarting cupsys to clear the queue. At this point cups has been running for 1:20 min from a OO doc printing to the cups printer. The page never printed, but the printer was blinking as if receiving data and is unavailable for other clients to print to. 




--
Damon L. Chesser
damon@damtek.com
http://www.linkedin.com/in/dchesser

--- End Message ---
--- Begin Message --- 
Version: 2.6.26-1

On Mon, May 12, 2008 at 01:08:09PM +0300, Ilpo Järvinen wrote:

> ps. ...you could have at least considered reporting upstream a bit
> earlier if some problem goes away/appears by changing kernel version
> (especially since you already tried some non-distro kernels and found
> them non-working), it might help to catch devs attention who hardly
> hang much around distro bug trackers :-).
>
> --
> [PATCH] [TCP] FRTO: Fix fallback to conventional recovery

This was commit a1c1f281b84a751fdb5ff919da3b09df7297619f, which is
present in 2.6.26. I'm marking this version as closed, if you
reencounter the bug, please reopen.

Cheers,
        Moritz

--- End Message ---
Reply to: