cupsys does not print
 

Two systems: amd64 and i386. Both ran Sid. printer is networked with
192.168.200.150. Added printer via localhost:631 as a network (LPD)
printer url is lpd://192.168.200.150/lpt1.

The printer comes to life, the data light blinks (Samsung ML-1430) then
the server stops making noise but the data light keeps blinking. No
paper comes out.

re-installed i386 to stable, re-add the printer via gnome-cups-manager,
tested, same results. So this is not a Sid issue.

tested from a win box, prints fine.

tested from ubuntu live (thinking maybe the Hawkings tech. print server
was going bad), prints fine.

This worked a month ago on Sid (amd64 box) before I test drove ubuntu.

I don't see any obvious bug reports.

I don't see a flood of messages coming across here.

Nothing in the cups error log:

E [04/Apr/2008:14:04:57 -0400] PID 26233 (/usr/lib/cups/backend/lpd)
stopped with status 1!
E [04/Apr/2008:14:06:54 -0400] CUPS-Add-Modify-Printer: Unauthorized
E [04/Apr/2008:14:19:57 -0400] CUPS-Add-Modify-Printer: Unauthorized
E [04/Apr/2008:14:19:59 -0400] CUPS-Add-Modify-Printer: Unauthorized

all messages there are accounted for.

the print jobs just stays in the print spool.

All this is very strange. I have not had this issue before (though I
have had printing killed in sid, never in sid and stable). What to do?




--
Damon L. Chesser
damon@damtek.com



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Re: cupsys does not print
 

On 04/04/2008, Damon L. Chesser <damon@damtek.com> wrote:
> Two systems: amd64 and i386. Both ran Sid. printer is networked with
> 192.168.200.150. Added printer via localhost:631 as a network (LPD) printer
> url is lpd://192.168.200.150/lpt1.
>
> The printer comes to life, the data light blinks (Samsung ML-1430) then the
> server stops making noise but the data light keeps blinking. No paper comes
> out.

In the administration page of Cups, is the printer in correct state?
I.e., not stopped?

Have you tried to increase the verbosity level to 'debug'? Otherwise,
some messages useful for troubleshooting may have been lost.


> This worked a month ago on Sid (amd64 box) before I test drove ubuntu.

Can you recover the configuration file of Cups for that installation,
e.g., a backup?


Regards,
Bernardo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Re: cupsys does not print
 

Bernardo Dal Seno wrote:
> On 04/04/2008, Damon L. Chesser <damon@damtek.com> wrote:
>
>
SNIP
>
> Can you recover the configuration file of Cups for that installation,
> e.g., a backup?
>
>
> Regards,
> Bernardo
>
>
>
Bernardo,

Thanks for replying. Cups is set up correctly. Cups reports the job as
printed.

No, I can't restore the config, but I have deleted it and re-added the
printer with both localhost:631 and with the gnome-cups-manager to no avail.

I have re-installed ubuntu 7.10 (I needed to print) and filed a bug
report with ubuntu 8.04.

IF (big if) this is a bug, it has to have something to do with the
security patches just released as stable is now unusable by me also.

The only other thing I can think of is my printserver (Hawking
Technology HPS1P) is just a little flaky, allowing win to print
(different code) but not the newest Lin. Nothing else makes sense,
nobody else is reporting an issue (I could be the only Linux user using
a Samsung ML1430 w/HPS1P printserver).

So far, the bug workers have not asked for more details.

--
Damon L. Chesser
damon@damtek.com



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Re: cupsys does not print: update
 

Damon L. Chesser wrote:
> Two systems: amd64 and i386. Both ran Sid. printer is networked
> with 192.168.200.150. Added printer via localhost:631 as a network
> (LPD) printer url is lpd://192.168.200.150/lpt1.
>
> The printer comes to life, the data light blinks (Samsung ML-1430)
> then the server stops making noise but the data light keeps blinking.
> No paper comes out.
>
> re-installed i386 to stable, re-add the printer via
> gnome-cups-manager, tested, same results. So this is not a Sid issue.
>
> tested from a win box, prints fine.
>
> tested from ubuntu live (thinking maybe the Hawkings tech. print
> server was going bad), prints fine.
>
> This worked a month ago on Sid (amd64 box) before I test drove ubuntu.
>
> I don't see any obvious bug reports.
>
> I don't see a flood of messages coming across here.
>
> Nothing in the cups error log:
> E [04/Apr/2008:14:04:57 -0400] PID 26233 (/usr/lib/cups/backend/lpd)
> stopped with status 1!
> E [04/Apr/2008:14:06:54 -0400] CUPS-Add-Modify-Printer: Unauthorized
> E [04/Apr/2008:14:19:57 -0400] CUPS-Add-Modify-Printer: Unauthorized
> E [04/Apr/2008:14:19:59 -0400] CUPS-Add-Modify-Printer: Unauthorized
>
> all messages there are accounted for.
>
> the print jobs just stays in the print spool.
>
> All this is very strange. I have not had this issue before (though I
> have had printing killed in sid, never in sid and stable). What to do?
>
>
>
>
Ok, found out it is kernel related. re-installed stable and did NO
updates (even security updates), tested cupsys, it worked. Did security
updates, got a new kernel.

output of uname -a for both kernels:

Linux dam-main-deb 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007
x86_64 GNU/Linux
Linux dam-main-deb 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008
x86_64 GNU/Linux


The new kernel did not print to cupsys printer, but the spool (blinking
lights and network activity) looks like it is transmitting very slowly.
Eventually the printer will print an error report. This takes so long,
only once have I gotten one.

Ok, so 2.6.24-1 is bad for me. I grabbed the latest kernel source from
kernel.org and made a kernel (2.6.25). Same issue.

So, what do I do now, who do I file a bug report to? This is not a
debian patch (kernel.org source had same issue), not a cupsys bug. Same
package load out works with 2.6.22 but not with >2.6.22.

btw, at this point I am on Sid with a 2.6.22-3-amd64 kernel or a 2.66.25
custom kernel (used 2.6.22 config to make)

I am at a loss as how to fix this, any would be appreciated.

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


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Re: cupsys does not print: update
 

Damon L. Chesser wrote:
> Damon L. Chesser wrote:
>> Two systems: amd64 and i386. Both ran Sid. printer is networked
>> with 192.168.200.150. Added printer via localhost:631 as a network
>> (LPD) printer url is lpd://192.168.200.150/lpt1.
>>
>> The printer comes to life, the data light blinks (Samsung ML-1430)
>> then the server stops making noise but the data light keeps
>> blinking. No paper comes out.
>>
>> re-installed i386 to stable, re-add the printer via
>> gnome-cups-manager, tested, same results. So this is not a Sid issue.
>>
>> tested from a win box, prints fine.
>>
>> tested from ubuntu live (thinking maybe the Hawkings tech. print
>> server was going bad), prints fine.
>>
>> This worked a month ago on Sid (amd64 box) before I test drove ubuntu.
>>
>> I don't see any obvious bug reports.
>>
>> I don't see a flood of messages coming across here.
>>
>> Nothing in the cups error log:
>> E [04/Apr/2008:14:04:57 -0400] PID 26233 (/usr/lib/cups/backend/lpd)
>> stopped with status 1!
>> E [04/Apr/2008:14:06:54 -0400] CUPS-Add-Modify-Printer: Unauthorized
>> E [04/Apr/2008:14:19:57 -0400] CUPS-Add-Modify-Printer: Unauthorized
>> E [04/Apr/2008:14:19:59 -0400] CUPS-Add-Modify-Printer: Unauthorized
>>
>> all messages there are accounted for.
>>
>> the print jobs just stays in the print spool.
>>
>> All this is very strange. I have not had this issue before (though I
>> have had printing killed in sid, never in sid and stable). What to do?
>>
>>
>>
>>
> Ok, found out it is kernel related. re-installed stable and did NO
> updates (even security updates), tested cupsys, it worked. Did
> security updates, got a new kernel.
>
> output of uname -a for both kernels:
>
> Linux dam-main-deb 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007
> x86_64 GNU/Linux
> Linux dam-main-deb 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008
> x86_64 GNU/Linux
>
>
> The new kernel did not print to cupsys printer, but the spool
> (blinking lights and network activity) looks like it is transmitting
> very slowly. Eventually the printer will print an error report. This
> takes so long, only once have I gotten one.
>
> Ok, so 2.6.24-1 is bad for me. I grabbed the latest kernel source
> from kernel.org and made a kernel (2.6.25). Same issue.
>
> So, what do I do now, who do I file a bug report to? This is not a
> debian patch (kernel.org source had same issue), not a cupsys bug.
> Same package load out works with 2.6.22 but not with >2.6.22.
>
> btw, at this point I am on Sid with a 2.6.22-3-amd64 kernel or a
> 2.66.25 custom kernel (used 2.6.22 config to make)
>
> I am at a loss as how to fix this, any would be appreciated.
>
I filed a bug report against the debian kernel and also against ubuntu
cupsys (just covering my bases). Installed fc8, had the same issues. I
could not print with any kernel >2.6.23. A kernel dev got a hold of me
and asked me to change /proc/sys/net/ipv4/tcp_frto to 0 (set via
/etc/sysctl.conf so as to take effect on every boot: net.ipv4.tcp_frto = 0)

This worked. However at this time, a stock kernel config will issue
this same error to me. There are some other applications effected (a
quick google for tcp_frto will show you, .http://mwh.geek.nz/ ) I am
posting this here on the off chance some one is experiencing some
strange network behavior and this will them. To test echo 0
>/proc/sys/net/ipv4/tcp_frto then test your issue.

At this time, kernel devs are working on a solution.

HTH

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


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Re: cupsys does not print: update
 

Damon L. Chesser wrote:
> Damon L. Chesser wrote:
>> Damon L. Chesser wrote:
>>> Two systems: amd64 and i386. Both ran Sid. printer is networked
>>> with 192.168.200.150. Added printer via localhost:631 as a network
>>> (LPD) printer url is lpd://192.168.200.150/lpt1.
>>>
>>> The printer comes to life, the data light blinks (Samsung ML-1430)
>>> then the server stops making noise but the data light keeps
>>> blinking. No paper comes out.
>>>
>>> re-installed i386 to stable, re-add the printer via
>>> gnome-cups-manager, tested, same results. So this is not a Sid issue.
>>>
>>> tested from a win box, prints fine.
>>>
>>> tested from ubuntu live (thinking maybe the Hawkings tech. print
>>> server was going bad), prints fine.
>>>
>>> This worked a month ago on Sid (amd64 box) before I test drove ubuntu.
>>>
>>> I don't see any obvious bug reports.
>>>
>>> I don't see a flood of messages coming across here.
>>>
>>> Nothing in the cups error log:
>>> E [04/Apr/2008:14:04:57 -0400] PID 26233 (/usr/lib/cups/backend/lpd)
>>> stopped with status 1!
>>> E [04/Apr/2008:14:06:54 -0400] CUPS-Add-Modify-Printer: Unauthorized
>>> E [04/Apr/2008:14:19:57 -0400] CUPS-Add-Modify-Printer: Unauthorized
>>> E [04/Apr/2008:14:19:59 -0400] CUPS-Add-Modify-Printer: Unauthorized
>>>
>>> all messages there are accounted for.
>>>
>>> the print jobs just stays in the print spool.
>>>
>>> All this is very strange. I have not had this issue before (though
>>> I have had printing killed in sid, never in sid and stable). What
>>> to do?
>>>
>>>
>>>
>>>
>> Ok, found out it is kernel related. re-installed stable and did NO
>> updates (even security updates), tested cupsys, it worked. Did
>> security updates, got a new kernel.
>>
>> output of uname -a for both kernels:
>>
>> Linux dam-main-deb 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007
>> x86_64 GNU/Linux
>> Linux dam-main-deb 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008
>> x86_64 GNU/Linux
>>
>>
>> The new kernel did not print to cupsys printer, but the spool
>> (blinking lights and network activity) looks like it is transmitting
>> very slowly. Eventually the printer will print an error report.
>> This takes so long, only once have I gotten one.
>>
>> Ok, so 2.6.24-1 is bad for me. I grabbed the latest kernel source
>> from kernel.org and made a kernel (2.6.25). Same issue.
>>
>> So, what do I do now, who do I file a bug report to? This is not a
>> debian patch (kernel.org source had same issue), not a cupsys bug.
>> Same package load out works with 2.6.22 but not with >2.6.22.
>>
>> btw, at this point I am on Sid with a 2.6.22-3-amd64 kernel or a
>> 2.66.25 custom kernel (used 2.6.22 config to make)
>>
>> I am at a loss as how to fix this, any would be appreciated.
>>
> I filed a bug report against the debian kernel and also against ubuntu
> cupsys (just covering my bases). Installed fc8, had the same issues.
> I could not print with any kernel >2.6.23. A kernel dev got a hold of
> me and asked me to change /proc/sys/net/ipv4/tcp_frto to 0 (set via
> /etc/sysctl.conf so as to take effect on every boot:
> net.ipv4.tcp_frto = 0)
>
> This worked. However at this time, a stock kernel config will issue
> this same error to me. There are some other applications effected (a
> quick google for tcp_frto will show you, .http://mwh.geek.nz/ ) I am
> posting this here on the off chance some one is experiencing some
> strange network behavior and this will them. To test echo 0
> >/proc/sys/net/ipv4/tcp_frto then test your issue.
>
> At this time, kernel devs are working on a solution.
>
> HTH
>
FYI, I tested out the patch for the 2.6.24-1 kernel and it now works
(patch is not available publicly AFAIK). I asked Ilpo Jarvined (kernel
developer) when it will be published: He said 2.6.26 will have it and a
version of 2.6.25 will have it (maybe .4 or .5) and he did not know if
2.6.24 would get it. It seems only a small amount of users are effected
by it.

As usual,

HTH

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


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org