Package: cupsys
Version: 1.1.22-8 & 1.1.23-2

when Printing with printers using ipp over https://, I get 100% of CPU 
utilization after the job is sent.

On Admin-Panel (http://localhost:631/printers/hp-laserjet) the printers first 
stauts after issuing a printjob is

"Printer does not support IPP/1.1, trying IPP/1.0..."

after some seconds or minutes o sending the data it says

": Print file accepted - job ID 41."

and CPU utilization goes up and is caused py a process called "https" (when 
using "top"-command)

This process is stopped when I cancel the Printjob which at this time is back 
in "pending since..."-mode although it has already been sent to the hardware 
and is going to be printed.

My backend-configuration is as follows:

debian:/usr/lib/cups/backend# ls -l
total 108
-rwxr-xr-x  1 root root 10412 Oct  5 21:33 canon
-rwxr-xr-x  1 root root 10532 Oct  5 21:33 epson
lrwxrwxrwx  1 root root     3 Jan 13 17:19 http -> ipp
lrwxrwxrwx  1 root root     3 Nov 12 00:12 https -> ipp
-rwxr-xr-x  1 root root 19708 Jan 12 11:02 ipp
-rwxr-xr-x  1 root root 15964 Jan 12 11:02 lpd
-rwxr-xr-x  1 root root  8136 Jan 12 11:02 parallel
-rw-r--r--  1 root root  5896 Jan 12 11:02 scsi
-rw-r--r--  1 root root  8608 Jan 12 11:02 serial
lrwxrwxrwx  1 root root    17 Jan 13 17:20 smb -> /usr/bin/smbspool
-rwxr-xr-x  1 root root  7740 Jan 12 11:02 socket
-rwxr-xr-x  1 root root 10320 Jan 12 11:02 usb

This is the printers config:
(printers.conf)
...
<DefaultPrinter hp-laserjet>
Info HP LaserJet 8000 Series PS
Location SomeLocation
DeviceURI https://user:[EMAIL PROTECTED]/printers/ein-ps/.printer
State Stopped
StateMessage Paused
Accepting Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
</Printer>
...

The printer is a remote printer connected to a central (MS-Windows? dont really 
know...) printingserver using IPP over https.

I'm using the ppd files from package foomatic-filters-ppds and for the above 
printer: *FoomaticIDs: HP-LaserJet_8000 Postscript

Kernel: Linux version 2.4.27 ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 
1:3.3.5-5))
Debian Sarge

The problem appeared from cupsys version 1.1.22-8 on. Older versions worked 
with no problems.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to