client 1.2.0 to 1.1.2x server over IPP: Only RAW printing works

other problems related to interaction between 1.2 clients and 1.1.2 ipp servers:

bug 42513
bug 41593

I can confirm this.

OK... It works now. But it didn't few days ago :) What version of CUPS do you have?

I have Ubuntu Dapper's latest 1.2.0 cups and I am trying to print IPP to
a SuSE 10 machine running CUPS 1.1.23.

The SuSE machine hosts the printer, and it is not a connection issue.
As I can remotely query that cups server and the printer is listed. My
bug report shows relevant? output I think. Please get back if you need
ANY amount of help and diagnostic information. Before Dapper went 1.2.0
it worked fine :(

Using the http backend I experience similar problems.
Printing over a cups 1.1.2. server (on RH) is broken with Dapper's 1.2.0 cups.
(printing worked problem-free with all previous versions of Ubuntu)

You can find the bug-report here (not sure if it is a duplicate):
https://launchpad.net/distros/ubuntu/+source/cupsys/+bug/42802

Can you:

- enable browsing on SuSE server
- set Listen or Port on SuSE to @LOCAL
- reinstall cupsys package (like dpkg --force-confnew -i /var/cache/apt/cupsys_1.2.0-0ubuntu5_i386.deb)

run, as root:

sudo /usr/share/cups/enable_browsing 1

Wait for a 30 seconds and then run gnome-cups-manager and check if printers apear on lists.

Make that /var/cache/apt/archives/cupsys_1.2.0-0ubuntu5_i386.deb

Ante Karamatić has packaged CUPS 1.2.1 for Dapper
http://www.grad.hr/~ivoks/ubuntu/cups

This packages may not fix this issue and they are *experimental*, use them *at your own risk*. It's worth to try, though. Please, report back.

Don't work for me. After installing suggested packages I try to add printer with kde printer wizard and at the point where I should choose printer model the list is empty.

Do:

sudo foomatic-cleanupdrivers

and then try adding printer.

https://launchpad.net/distros/ubuntu/+source/kcontrol/+bug/42123

I'm running Dapper after upgrading in place from Breezy. AFAIK, I have the default printing setup.

I have the same problem discussed above, and was able to successfully print using cupsdoprint -P <printer> -H <host> <file> after unsuccessfully trying cupsdoprint -H <host> -P <printer> <file>

The server error log indicates the first command tried (-H -P) resulted in an IPP Read Error!. It also indicates that the print from software (e.g., Evolution) is sending an unprintable file. Here's the server error_log starting with last Evolution-based bug through the successful cupsdoprint:

I [04/Jun/2006:09:14:08 -0500] Adding start banner page "none" to job 497.
I [04/Jun/2006:09:14:08 -0500] Adding end banner page "none" to job 497.
I [04/Jun/2006:09:14:08 -0500] Job 497 queued on 'HP952' by 'remroot'.
E [04/Jun/2006:09:14:08 -0500] Unable to convert file 0 to printable format for job 497!
I [04/Jun/2006:09:14:08 -0500] Hint: Do you have ESP Ghostscript installed?
I [04/Jun/2006:09:14:08 -0500] Hint: Try setting the LogLevel to "debug".
I [04/Jun/2006:09:22:43 -0500] Started "/usr/lib/cups/cgi-bin/printers.cgi" (pid=3533)
I [04/Jun/2006:09:23:00 -0500] Started "/usr/lib/cups/cgi-bin/printers.cgi" (pid=3541)
E [04/Jun/2006:09:28:36 -0500] ReadClient: 6 IPP Read Error!
I [04/Jun/2006:09:28:56 -0500] Adding start banner page "none" to job 498.
I [04/Jun/2006:09:28:56 -0500] Adding end banner page "none" to job 498.
I [04/Jun/2006:09:28:56 -0500] Job 498 queued on 'HP952' by 'rdb'.
I [04/Jun/2006:09:28:56 -0500] Started filter /usr/lib/cups/filter/texttops (PID 3638) for job 498.
I [04/Jun/2006:09:28:56 -0500] Started filter /usr/lib/cups/filter/pstops (PID 3639) for job 498.
I [04/Jun/2006:09:28:56 -0500] Started filter /usr/lib/cups/filter/foomatic-rip (PID 3640) for job 498.
I [04/Jun/2006:09:28:56 -0500] Started backend /usr/lib/cups/backend/hp (PID 3641) for job 498.

Since browsing doesn't seem to work, I added my RAW printer (Windows printer) and successfully printed a test page and printed successfully from Evolution.

sudo foomatic-cleanupdrivers

That solved my problem:
https://launchpad.net/distros/ubuntu/+source/cupsys/+bug/43884

I was able to add printer with ubuntu cups packages, now everything works OK.

Please confirm you installed cups 1.2.1 packages.

Sorry I ment ubuntu packages in official repository, so 1.2.0-0ubuntu.5

Please confirm you installed cups 1.2.1 packages.

Umm... your problem isn't related to this bug. This is problem with cups 1.2 client printing to cups1.1 servers. Your issue is problem with kcontrol and kde printing not finding drivers.

I may have filed with the wrong bug; however, it appears to be a 1.2
client to 1.1 server problem. In Breezy, the printers were found (and
worked just fine) when browsing for printers. Browsing also works on
FC4 client with 1.1 & server 1.1.

It is definitely *not* a KDE problem, because I'm not running KDE. I
run some gnome services on top of XFCE.

On Sun, 2006-06-04 at 19:06 +0000, Ante Karamatić wrote:
> Umm... your problem isn't related to this bug. This is problem with cups
> 1.2 client printing to cups1.1 servers. Your issue is problem with
> kcontrol and kde printing not finding drivers.
>

I may have filed with the wrong bug, or Ante is speaking to two people causing crosstalk.

I have a 1.2 client to 1.1 server problem. In Breezy, the printers were found (and worked just fine) when browsing for printers. Browsing also works on FC4 client with 1.1 & server 1.1.

My issue isn't a KDE problem, because I don't run KDE. I run some gnome services on top of XFCE.

My comments were for cyracks.

@Tuxi:

Problems with cups1.2 client and 1.1.x servers are fixed in 1.2.1. I packaged 1.2.1 cups for dapper. Please add:

deb http://www.grad.hr/~ivoks/ubuntu/cups ./

to you /etc/apt/sources.list, do an apt-get update with apt-get upgrade, and browsing should work. Please report changes. Thank you.

I upgraded the cups client from http://www.grad.hr/~ivoks/ubuntu/cups and the problem remains.

my cups server is a 1.1.23

any ideas?

You can't print on your cups server or your logs are full of "cupsdAuthorize: Local authentication certificate not found"?

I upgraded the cups client from http://www.grad.hr/~ivoks/ubuntu/cups and the problem remains.

my cups server is a 1.1.23

any ideas?

I may have filed with the wrong bug, or Ante is speaking to two people causing crosstalk.

I have a 1.2 client to 1.1 server problem. In Breezy, the printers were found (and worked just fine) when browsing for printers. Browsing also works on FC4 client with 1.1 & server 1.1.

My issue isn't a KDE problem, because I don't run KDE. I run some gnome services on top of XFCE.

I've installed the cups client from deb http://www.grad.hr/~ivoks/ubuntu/cups ./. Using gnome-cups-manager showed all the printers on the print server. I tried a test print to a browsed printer from gnome-cups-manager and tried to print to the same printer from Evolution. The server shows no activity on any of the cups logs on the print server.

I can only print on the manually installed printer.

I upgraded the cups client from http://www.grad.hr/~ivoks/ubuntu/cups and the problem remains.

my cups server is a 1.1.23

any ideas?

OK, thanks for your testing.

@Tuxi
@JcM

After installing the packages of cups 1.2.1, is the server log still full of "cupsdAuthorize: Local authentication certificate not found" messages or is there something new there? Thanks.

(there must be some error in Malone, since this report is full of repeated comments from JcM)

OK. certificate issues are irrelevant. They only meen CUPS can't use SSL. This errors aren't responisible for "unable to print". With latest packages from grad.hr, you will also get certificate errors, but please ignore them.

@Ante

Oh, I didn't know that. I am really sorry for the confusion then. Perhaps, I should modify the description of this bug to "unable to print".

I upgraded the cups client from http://www.grad.hr/~ivoks/ubuntu/cups and the problem remains.

my cups server is a 1.1.23

any ideas?

@JcM

I think you have a problem in your mail, you are sending the same mail over and over.

OK. First of all, "Local authentication certificate not found" are errors one can get if he/she doesn't have proper Dapper CUPS packages. Or he has proper packages, but has wrong /etc/cups/cupsd.conf (check for line Encryption required).

All of you, who can enable browsing on you CUPS 1.1.x servers - enable it. This is the most easiest, fastest, and the best workaround for this bug (acutlly, this is how it should be done). I'll create a web page that would be a HOWTO for this task. After you enable sharing on your CUPS server, enable browsing too on your dapper box (gnome-cups-manager -> Global Settings -> Detect LAN printers). Printers from your pre1.2.0 CUPS server should automagicaly appear.

Those who can't or won't enable browing on their server or/and client still can print. When adding your printer, select "Raw" for vendor and then "Queue" for driver (this is only for those who add printer over IPP or HTTP protocol, not for local or smb printers). Selecting anything else results in error. This is a bug.

Before doing anything, make sure you have cupsd.conf from distribution. You can get it at http://www.grad.hr/~ivoks/ubuntu/cups/cupsd.conf and replace yours with it or compare them.

Those who installed packages from http://www.grad.hr/~ivoks/ubuntu/cups should revert to old packages. If you don't know how, wait for hour or two and I'll post a link to HOWTO for this task.

Everything mentioned here was tested with cups 1.1.20 on MacOSX and Dapper CUPS 1.2.

http://www.grad.hr/~ivoks/ubuntu/cups/downgrade_cups is a script that will downgrad all the packages from my repository to official Ubuntu packages. It will also clear /etc/apt/sources.list from my repository. Download it and run it like:

chmod +x downgrade_cups
sudo ./downgrade_cups

http://www.grad.hr/~ivoks/ubuntu/cups/HOWTO-enable-browsing is Q&D HOWTO for enabling browsing on your servers.

Please report your results.

Raw/Queue Works! thanks :)

@Ante

I reverted cups on the client using your script and have confirmed that my cupsd.conf is the same as in your link.

The results are the same as yesterday. I see the printers in gnome-cups-manager on the client. When I send a test print to a browsed queue, the server has no record in any of the cups logs of conversing with the client.

Tuxi, do you have ubuntu-desktop package installed?

OK .. I downgraded both client and server to 1.2.0-ubuntu, was still unable to print, but after deleting the printer and re-adding it (with exact same name), everything is working perfectly now. This isn't going to solve problems for people who can't upgrade their server but it does work for us. Thanks all.

@arp, Tuxi, JcM

Could you tell me what printer do you have, and which driver did you use? This seems to be a driver issue. If you all say Samsung/Xerox... :) Could you all change LogLevel to debug2, restart cups, chose corect driver (not Raw), and attach error_log here after you try printing something.

@Tuxi, JcM

Did you try with Raw/Queue drivers? Any results?

@Walter

You problem could be caused by different naming convention in Breezy and Dapper, since removing and adding printer worked out this problem. I still have to investigate this, but that wouldn't be first case of that behaviour. What printer do you have? Is it HP?

@ Christian

This looks like an issue with (really) old CUPS, and that is fixed in cups 1.2.1. I'll create some packages just for you to test them, ok?

@ everybody

Issue with "certificate" is a bug, but it's not the reason why printer(s) don't print. Thank you all for your help.

@Ante,

I have ubuntu-desktop loaded.

Don't browsed queues get the PPD from the server? The other client (cups 1.1.23 on both server and client, both Fedora Core 4) appears to get the PPD information from the server.

The printer in question is an HP 952C inkjet printer. The server is configured using the HPLIP drivers. For the RAW print queue, I used the HPLIP 0.9.7 driver.

When looking at browsed queues the Paper and Advanced tabs have no information. I don't know whether this is normal or not; I didn't check in Breezy, and FC4 doesn't seem to have gnome-cups-manager.

Hi,

Just to confirm I have the same problem. My print server is running Debian stable with cupsys version 1.1.23-10sarge and I upgraded the client from breezy to dapper. Printing worked fine before the upgrade but doesn't work anymore. On the server with debug level set to "debug2" I get the following messages.

My problem is that I don't know how to configure my printer in order to use "RAW" printing? Could someone post a short explanation on how to do this?

cheers

Stephane

d [09/Jun/2006:03:59:56 +0200] IsAuthorized: auth = 0, satisfy=0...
d [09/Jun/2006:03:59:56 +0200] POST /printers/HL2040
d [09/Jun/2006:03:59:56 +0200] CONTENT_TYPE = application/ipp
d [09/Jun/2006:03:59:56 +0200] ReadClient: 10 con->data_encoding = length, con-
E [09/Jun/2006:03:59:57 +0200] ReadClient: 10 IPP Read Error!
D [09/Jun/2006:03:59:57 +0200] SendError: 10 code=400 (Bad Request)
D [09/Jun/2006:03:59:57 +0200] CloseClient: 10
d [09/Jun/2006:03:59:57 +0200] CloseClient: Removing fd 10 from InputSet and Ou

@pop / Stephane

On your server, create a print queue that just passes the output from the client to the printer. This is how Windows print queues need to be set up.

On the client point at the server's RAW (Windows) queue and select the appropriate print driver. Example gnome-cups-manager, add printer, network printer (cups printer with RAW queue URI), select printer type, etc.

Tuxi,

thanks for your advice. I tried with no luck. My printer is a brother HL-2040 and seems to require the Brother linux drivers. I installed these on the client and set the printer address to the raw queue on the server but the test page just "prints" four blank pages...

I then decided to upgrade the cupsd server to version 1.2.1 (from source to avoid any depency problem with my debian stable installation). The install went OK, I had to reconfigure the printer, reinstall the Brother driver etc... etc... and this seems to have fixed the problem. I wasted half-a-day however and I have a source-only package on my otherwise clean debian stable machine....

So, I think it's a serious bug, it's certainly a regression from breezy...

thanks for your help

Stephane

@ Tuxi

Yes, browsed printers should work, but not manually added printers. If you want to get browsed printers, you should enable browsing on your dapper. If you want to set it up manually, you should choose Raw, for now. When you choose raw, you don't get any special/normal options (like change paper size, resolution, etc...).

@ pop

Yes, it is serious bug, and we are working on it.

Tuxi,

thanks for your advice. I tried with no luck. My printer is a brother HL-2040 and seems to require the Brother linux drivers. I installed these on the client and set the printer address to the raw queue on the server but the test page just "prints" four blank pages...

I then decided to upgrade the cupsd server to version 1.2.1 (from source to avoid any depency problem with my debian stable installation). The install went OK, I had to reconfigure the printer, reinstall the Brother driver etc... etc... and this seems to have fixed the problem. I wasted half-a-day however and I have a source-only package on my otherwise clean debian stable machine....

So, I think it's a serious bug, it's certainly a regression from breezy...

thanks for your help

Stephane

I am also having a problem with this bug, and can't seem to print to my Samsung network printer.

As I am using Kubuntu, the KDE Print Manager doesn't have a "Queue" option when you choose raw for IPP printers... which leaves me without any way to print!

OK, since some of you reported that 1.2.1 fixed issue for them, could you try whit these packages? Add:

deb http://www.grad.hr/~ivoks/ubuntu/cups/1.2.1 ./

to /etc/apt/sources.list, update and try setting your printer again.

Good luck :/

I am also having a problem with this bug, and can't seem to print to my Samsung network printer.

As I am using Kubuntu, the KDE Print Manager doesn't have a "Queue" option when you choose raw for IPP printers... which leaves me without any way to print!

The provided packages don't help for the "Bad Request" issue in Bug
Report 42516
https://launchpad.net/distros/ubuntu/+source/cupsys/+bug/42513

sinder@l42:~$ lpr -Px1 bla.ps
sinder@l42:~$ lpr -Px1 bla.ps
sinder@l42:~$ lpr -Px1 bla.ps
sinder@l42:~$ lpr -Px1 bla.ps
sinder@l42:~$ lpr -Px1 bla.ps
sinder@l42:~$ lpr -Px1 bla.ps
sinder@l42:~$ lpr -Px0 bla.ps
sinder@l42:~$ lpr -Px0_single bla.ps
lpr: Bad Request
sinder@l42:~$ lpr -Px1_single bla.ps
lpr: Bad Request
sinder@l42:~$ lpr -Px1_single bla.ps
lpr: Bad Request
sinder@l42:~$ lpr -Px1_single bla.ps
lpr: Bad Request

So a few times it works but in general it doesn't.

Here the technical infos:

Client:
Package: cupsys-client
Source: cupsys
Version: 1.2.1-2ubuntu1.1

Server (Redhat EL AS 4 Update 3):
$ rpm -qa|grep cups
cups-libs-1.1.22-0.rc1.9.10
cups-1.1.22-0.rc1.9.10
cups-devel-1.1.22-0.rc1.9.10

On Tue, 20 Jun 2006 08:53:21 -0000
Andreas Sindermann <email address hidden> wrote:

> sinder@l42:~$ lpr -Px0_single bla.ps
> lpr: Bad Request
> sinder@l42:~$ lpr -Px1_single bla.ps
> lpr: Bad Request
> sinder@l42:~$ lpr -Px1_single bla.ps
> lpr: Bad Request
> sinder@l42:~$ lpr -Px1_single bla.ps
> lpr: Bad Request
>
> So a few times it works but in general it doesn't.

It looks to me that only printers x0_single and x1_single don't work.
Is there any apecific configuration for those printers?

--
Ante Karamatic | 0xD3BDA225 | 0x0A4A0161
<email address hidden> | <email address hidden> | ivoks.blogspot.com
"Tomorrow is my day off, so please stay off the powder!"

It's the same driver (PPD file provided by Xerox) with slightly
different settings (in one case the duplexer is disabled
 (x1_single/x0_single), in the other case longe edge flipping is
configured), but in general the behavior seems to become better:

sinder@l42:~$ lpr -Px1_single bla.ps
sinder@l42:~$ lpr -Px1_single bla.ps
lpr: Bad Request
sinder@l42:~$ lpr -Px1_single bla.ps
sinder@l42:~$ lpr -Px1_single bla.ps
sinder@l42:~$ lpr -Px1_single bla.ps
sinder@l42:~$ lpr -Px1_single bla.ps
sinder@l42:~$ lpr -Px1_single bla.ps
sinder@l42:~$ lpr -Px1_single bla.ps
sinder@l42:~$ lpr -Px1_single bla.ps
sinder@l42:~$ lpr -Px1_single bla.ps

The print servers' logfile (error_log) is added as an attachment.

This bug is also reported upstream:
http://www.cups.org/str.php?L1717

This problem seems to fixed upstream some weeks ago - and the fix should already be integrated in Cups1.2.2.
Do you still have the reported problem when printing to a 1.1.2x server over IPP using the latest Cups packages?
If not I suggest to close this bug.

If I try to use browsed queues, the print server has no entries in any
of the cups logs, and I get no prints.

I consider this bug to still be open.

On Thu, 2006-08-10 at 10:24 +0000, Christian Göbel wrote:
> This problem seems to fixed upstream some weeks ago - and the fix should already be integrated in Cups1.2.2.
> Do you still have the reported problem when printing to a 1.1.2x server over IPP using the latest Cups packages?
> If not I suggest to close this bug.
>

Referring to the title of this bug (IPP: Only RAW printing works) I have the same problem here with a DeskJet-890C printer. It is connected to my desktop computer and accessing it via IPP with my laptop fails if I choose the normal procedure to install the printer (i.e. Printer --> Network --> IPP:/server/printers/DekJet-890C --> Selection Driver HPLIP 0.9.7) Then the output is always
 -12345X@PJL ENTER LANGUAGE=PCL3GUI
in the first line followed by some lines of variable garbage.
On both systems (server and laptop) Dapper has been installed and both use the same versions of cups related packages.

$ dpkg -l | grep cups
ii cupsys 1.2.2-0ubuntu0.6.06
ii cupsys-bsd 1.2.2-0ubuntu0.6.06
ii cupsys-client 1.2.2-0ubuntu0.6.06
ii cupsys-driver-gutenprint 5.0.0~rc2-0ubuntu6
ii gnome-cups-manager 0.31-1.1ubuntu13
ii libcupsimage2 1.2.2-0ubuntu0.6.06
ii libcupsys2 1.2.2-0ubuntu0.6.06
ii libgnomecups1.0-1 0.2.2-1ubuntu5.1
ii libgnomecupsui1.0-1c2a 0.31-1.1ubuntu13

There are NO errors in /var/cups/error_log.

The printer only works via IPP after I installed a printer in RAW mode as described above.

I might be worth noting that this problem only occurs AFTER updating the laptop from HOARY TO DAPPER last week. Before that time printing went fine the usual way (i.e. no RAW printer needed). The server, which is my dekstop computer actually, has been updated since release of Dapper and was kept up to date since then.
So it's a pretty good guess that it hast something to do with the client. The Dapper installation on the laptop computer were a complete re-install. There are no remnants of Hoary whatsoever.

Kind regards
Peter

Can you try CUPS 1.2.3, which was recently introduced in Edgy? This should fix your problem.

As far as I am concerned the bug is gone in Edgy: cups-1.2.4-2ubuntu3 for both client and server works as expected without the "RAW-workaround".

Sorry if the following information only confuses the issue, but for what its worth, here goes nothing etc..

I have a dapper box as home server with Epson Stylus Photo RX425 connected via USB and local printing works fine. I have the cupsd listening on an additional port and configured to allow only authenticated SSL connections to it. Printing from windows XP clients also seems to work provided that "AuthType Basic" is enabled and cupsys has access to system passwords.

The hardest thing was to get by dapper laptop printing to the dapper server. One issue is that both the documentation (e.g. DeviceURI format) and the GUI are a bit terse. Inputting an URI in form

  https://user:password@server:port/printers/etc

gave no errors but got silently converted to

  ipp://https://user:password@server:port/printers/etc

When printing a test page the GUI just indicated that the printer got paused at some point, but from the web UI (http://localhost:613/) one can see that the printing is failing because host "https" cannot be found. So I changed the DeviceURI directly in printers.conf to remove the ipp:// prefix, but this does not work either because /usr/lib/cups/backend/https does not exist.

So would symlinking ipp to https be acceptable? I ended up adding encryption=always to the URI as in:

  ipp://user:password@server:port/printers/etc?encryption=always

but was still not able to print with the 1.2.2 dapper cupsys packages. The error log contained a lot of those "Local authentication certificate not found" errors mentioned here but I do not know whether those are related. I finally recompiled the edgy cupsys for my dapper laptop and now I can print. The server error log still has complaints about "Bad request line" but those errors occur also for the windows clients.

Hmm.. maybe a summary would be some enhacement wishes:

- more verbose documentation for the DeviceURI
- more verbose/input validation for the GUI
- update dapper cupsys to 1.2.4?
- allow "AuthType Basic" with a password source separate from the system one

[Expired for cupsys (Ubuntu) because there has been no activity for 60 days.]