client 1.2.0 to 1.1.2x server over IPP: network printing regression

The error-log is rather large, since I tried different things. Hope it is helpful anyway.

Also getting the same problem. Breezy machines on the network can print but Dapper's broken.

At first I thought it was related to bug #43298 (CUPS does not have permission to write error_log) but I managed to fix that and still no joy.

error_log shows: E [07/May/2006:10:19:26 +0200] [Job 35] No %%BoundingBox: comment in header!
page_log: ML-1510 jason 35 [07/May/2006:10:19:29 +0200] total 0 - localhost
localhost - - [07/May/2006:10:19:26 +0200] "POST /printers/ML-1510 HTTP/1.1" 200 153982 - successful-ok
Syslog doesn't echo anything about printing.

On the server I get:
D [07/May/2006:10:32:56 +0200] StartJob() id = 149, file = 0/1
E [07/May/2006:10:32:56 +0200] Unable to convert file 0 to printable format for job 149!
I [07/May/2006:10:32:56 +0200] Hint: Do you have ESP Ghostscript installed?
D [07/May/2006:10:32:56 +0200] CancelJob: id = 149

I have just made the latest updates (10 May 2006) and tried again.
Using the System/Administration/Printing tool from Gnome gives the same results as reported above. Depending on the driver the print-job gets either paused or canceled.
I also tried http://localhost:631/ : Here I could send a testpage!!!
However only with the simple driver (standard PS-driver used for the Apple Laser-Writer-Select-360 (as a user guest)

With the (recommended) standard driver HP4200 the job got canceled just like described in my original bug-report. And the message "/usr/lib/cups/backend/http failed" is shown beside the printer.

Printing out of any Gnome-Applications (e.g. Evince) is still broken.

The problem persists after the latest updates (running cups 1.2.0 now)

Not sure if this is related: I cannot use http://localhost:631/ for configuring my printers. I am required to give a password after a change - but my password is not accepted. This used to work with Flight5.

Here is the standard error log after trying to print a testpage from gnome-cups-manager:

E [11/May/2006:10:13:16 +0200] Creating missing directory "/var/run/cups/certs"
E [11/May/2006:10:14:38 +0200] CUPS-Set-Default: Unauthorized
E [11/May/2006:10:14:50 +0200] cupsdAuthorize: pam_authenticate() returned 7 (Authentication failure)!
E [11/May/2006:10:14:50 +0200] CUPS-Set-Default: Unauthorized
E [11/May/2006:10:15:03 +0200] Resume-Printer: Unauthorized
E [11/May/2006:10:15:45 +0200] [Job 76] No %%BoundingBox: comment in header!
E [11/May/2006:10:15:46 +0200] [Job 76] Print file was not accepted (Bad Request)!
E [11/May/2006:10:15:46 +0200] PID 5145 (/usr/lib/cups/backend/http) stopped with status 1!

I just checked the error-log again and got this:
(I didn't touch printing since I posted my last comment)
Perhaps my problem is related to this bug:
https://launchpad.net/distros/ubuntu/+source/cupsys/+bug/43884

E [11/May/2006:10:29:28 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:28 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:28 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:33 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:33 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:33 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:33 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:38 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:38 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:38 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:38 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:43 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:43 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:43 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:43 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:48 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:48 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:48 +0200] cupsdAuthorize: Local authentication certificate not found!
E [11/May/2006:10:29:48 +0200] cupsdAuthorize: Local authentication certificate not found!
and so on

Not sure, but perhaps this bug is related:
https://launchpad.net/distros/ubuntu/+source/cupsys/+bug/43884
(however it is not on network-printing)

After the latest updates to cups1.2.0-ubuntu2 the problem seems to persist:
First trying to print a testpage from the network interface, using the recommended standard (PS) -driver for the HP4200 printer and then trying to print a testpage from gnome-cups-manager using the Apple driver results in the following error-log:

E [12/May/2006:19:31:35 +0200] Creating missing directory "/var/run/cups/certs"
E [12/May/2006:19:32:59 +0200] [Job 77] Print file was not accepted (Bad Request)!
E [12/May/2006:19:32:59 +0200] PID 5009 (/usr/lib/cups/backend/http) stopped with status 1!
E [12/May/2006:19:35:59 +0200] Pause-Printer: Unauthorized
E [12/May/2006:19:37:05 +0200] cupsdAuthorize: Local authentication certificate not found!
E [12/May/2006:19:37:05 +0200] cupsdAuthorize: Local authentication certificate not found!

lots of this

E [12/May/2006:19:37:56 +0200] cupsdAuthorize: Local authentication certificate not found!
E [12/May/2006:19:37:56 +0200] cupsdAuthorize: Local authentication certificate not found!
E [12/May/2006:19:38:01 +0200] [Job 78] No %%BoundingBox: comment in header!
E [12/May/2006:19:38:01 +0200] cupsdAuthorize: Local authentication certificate not found!
E [12/May/2006:19:38:01 +0200] cupsdAuthorize: Local authentication certificate not found!

E [12/May/2006:19:38:06 +0200] cupsdAuthorize: Local authentication certificate not found!
E [12/May/2006:19:38:06 +0200] cupsdAuthorize: Local authentication certificate not found!
E [12/May/2006:19:38:07 +0200] [Job 78] Print file was not accepted (Bad Request)!
E [12/May/2006:19:38:07 +0200] PID 5469 (/usr/lib/cups/backend/http) stopped with status 1!
E [12/May/2006:19:38:11 +0200] cupsdAuthorize: Local authentication certificate not found!
E [12/May/2006:19:38:11 +0200] cupsdAuthorize: Local authentication certificate not found!

and so on

With the latest updates (17/05/2006) my problem persists.

The problem described in the follwing bug report could be related (although the used backend is different):
https://launchpad.net/distros/ubuntu/+source/cupsys/+bug/45099/

@Jason

You need to have gs-eps installed.

@Christian

Why do you use http backend? Why not IPP? I'll investigate HTTP protocol a bit later today. Please, attach your /etc/cups/printers.conf.

I just tested Breezy as a CUPS server with Dapper as a CUPS client. I used default Breezy configs, but changed Listen localhost:631 to Listen 631, and added Allow from @LOCAL in <Location />. This must be done to enable sharing of printers in Breezy. I also enabled Browsing to see if my breezy printer will apear.

I used default configs in Dapper; but enabled browsing:

sudo /usr/share/cups/enable_browsing

Printer from Breezy was broadcasted and Dapper picked it up; without any manual configuration. Printing worked as expected.

Then I added new printer on Dapper with http://breezy:631/printers/printername URI and printing worked as expected.

I guess you have configuration error. I advise you to reinstall cupsys packages on Dapper (replacing your configs with default) and check configs of CUPS 1.1.x server. It must have Listen or Port set to 631. Browsing is optional, but Allow @LOCAL is a must under <Location /> directive.

Hi,

Ante Karamatić [2006-05-17 19:36 -0000]:
> I guess you have configuration error. I advise you to reinstall cupsys
> packages on Dapper (replacing your configs with default) and check
> configs of CUPS 1.1.x server. It must have Listen or Port set to 631.
> Browsing is optional, but Allow @LOCAL is a must under <Location />
> directive.

Just for the record, the default cups configuration in dapper now
already contains the 'Allow @LOCAL' directive (breezy doesn't,
though). So you only need to enable sharing and browsing with

  sudo /usr/share/cups/enable_sharing 1
  sudo /usr/share/cups/enable_browsing 1

on the server, and

  sudo /usr/share/cups/enable_browsing 1

on the client (enable_browsing works in breezy, enable_sharing is new
in dapper; on breezy you have to set the Port directive as Ante
described).

--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org

In a world without walls and fences, who needs Windows and Gates?

@Ante:
I use the http backend since the System Administrator at our institute advised me todo so. (An before cups 1.2.0 final everything worked fine).
Anyway, I just tried to configure using the IPP-backend with exactly the same problem. (so perhaps this is really the same problem like in Bug 45099)

I just reinstalled cupsys - and the problem persists. You can find the required cups.conf attached. I didn't enable browsing on my Dapper - but that shouldn't change anything, I guess.

Together with the System-Administrator of the cups-server I also checked the cups.conf of the server - and we didn't see any problem.

By the way the problem appears also using the cups1.2.0 client from the Fedora-5 the system used by our system administrator - so the problem seems not to be Ubuntu specific. By the way we could print one page (to our surprise) but we couldn't reproduce it :(

@Ante
The /etc/cups/printers.conf you have asked for.

Everything looks fine with your config. I guess this is server issue. If you can, please add server's cupsd.conf. And add server's and client's error_log and server's acces_log when printing fails.

Thanks.

btw IPP *is* HTTP and I'm still suspecting this is configuration issue, since HTTP and IPP protocols are well tested in all networks (Windows, OSX, CUPS1.1, CUPS1.2).

Here is the cupsd.conf from the printing server.

The error log (trying to print to the server from Cups1.2.0 on Fedora (of the System Administrators computer) gives this:
D [18/May/2006:10:56:34 +0200] AcceptClient() 11 from 130.104.186.13:631.
D [18/May/2006:10:56:34 +0200] ReadClient() 11 POST /printers/hplj4200 HTTP/1.1
D [18/May/2006:10:56:34 +0200] ProcessIPPRequest: 11 status_code=1
D [18/May/2006:10:56:34 +0200] CloseClient() 11
D [18/May/2006:10:56:34 +0200] AcceptClient() 11 from 130.104.186.13:631.
D [18/May/2006:10:56:34 +0200] ReadClient() 11 POST /printers/hplj4200 HTTP/1.1
E [18/May/2006:10:56:35 +0200] ReadClient() 11 IPP Read Error!
D [18/May/2006:10:56:35 +0200] SendError() 11 code=400
D [18/May/2006:10:56:35 +0200] AcceptClient() 13 from 130.104.186.13:631.
D [18/May/2006:10:56:35 +0200] ReadClient() 13 POST /printers/hplj4200 HTTP/1.1
D [18/May/2006:10:56:35 +0200] ProcessIPPRequest: 13 status_code=1
D [18/May/2006:10:56:35 +0200] CloseClient() 13

Possibly there are different issues here:
The System Administrator didn't manage to print via the cups print-server. However (again from cups 1.2.0 on Fedora 5) he could print to the printer directly via different (other) protocols. He tried UnixPrinter(LPD) and HP JetDirect and it worked without problems.
Trying to do the same thing from my Ubuntu Dapper didn't work - so maybe there is a more general problem with the setup on my computer.

Note that using the release candidate for cups1.2.0 everything worked fine on Ubuntu Flight 5.

Here is my error.log trying to print a testpage and using different backends:
E [18/May/2006:14:47:33 +0200] [Job 82] Unable to get printer status (client-error-forbidden)!
E [18/May/2006:14:47:43 +0200] [Job 82] Unable to get printer status (client-error-forbidden)!
E [18/May/2006:14:47:48 +0200] CUPS-Add-Modify-Printer: Unauthorized
E [18/May/2006:14:47:48 +0200] [Job 82] No %%BoundingBox: comment in header!
E [18/May/2006:14:47:48 +0200] PID 22490 (/usr/lib/cups/backend/ipp) crashed on signal 9!
E [18/May/2006:14:47:48 +0200] [Job 82] Unable to locate printer 'p'!
E [18/May/2006:14:47:48 +0200] PID 24460 (/usr/lib/cups/backend/socket) stopped with status 4!
E [18/May/2006:14:48:27 +0200] [Job 83] No %%BoundingBox: comment in header!
E [18/May/2006:14:48:27 +0200] [Job 83] Unable to send print file to printer: Broken pipe
E [18/May/2006:14:48:27 +0200] PID 24593 (/usr/lib/cups/backend/socket) stopped with status 1!
E [18/May/2006:14:48:34 +0200] [Job 83] No %%BoundingBox: comment in header!
E [18/May/2006:14:48:34 +0200] [Job 83] Unable to send print file to printer: Broken pipe
E [18/May/2006:14:48:34 +0200] PID 24625 (/usr/lib/cups/backend/socket) stopped with status 1!
E [18/May/2006:14:49:28 +0200] [Job 83] No %%BoundingBox: comment in header!
E [18/May/2006:14:49:28 +0200] PID 24770 (/usr/lib/cups/backend/lpd) stopped with status 1!
E [18/May/2006:14:49:38 +0200] Resume-Printer: Unauthorized

Servers conf is ok. In yours Dapper logs "Unable to get printer status (client-error-forbidden)!" is very indicative. This happens when you print to server? Your machine must have IP in 130.104.63.0/24, 130.104.186.0/23 or exactly 130.104.55.93. Or it has to be resolvable in ucl.ac.be domain.

And do you really have printer 'p' configured?

Unfortunately this error log has not been produced trying to print to via the server but trying to print to the printer directly via a different other protocols.
My machine has ip: 130.104.186.126 and I can ping to 01311135.ires.ucl.ac.be (so it is resolved, too - if I understand well).

Could it be that cups1.2.0 has problems if my computer-name is numeric?
How could I check if the cups-server can talk back to my computer?

So just to summarize:
1. my client cupsd.conf looks o.k.
2. the servers cupsd.conf looks o.k.
3. I can print from breezy, I could print from Dapper Flight5, but since update to Cups1.2.0 (standard config) I cannot print anymore.

Any suggestion on what else I could try?

And just for the record this is the error message I get when I try to print via the server using ipp:
E [19/May/2006:14:38:51 +0200] cupsdAuthorize: Local authentication certificate not found!
E [19/May/2006:16:37:25 +0200] CUPS-Add-Modify-Printer: Unauthorized
E [19/May/2006:16:37:40 +0200] [Job 86] No %%BoundingBox: comment in header!
E [19/May/2006:16:37:41 +0200] [Job 86] Print file was not accepted (Bad Request)!
E [19/May/2006:16:37:41 +0200] PID 8248 (/usr/lib/cups/backend/ipp) stopped with status 1!

Any idea what this "Local authentication certificate not found!" means?

I just discovered that cups has another debug-level.
Attached you can find the error_log of my cups client, when trying to print to the cups-server. I hope this is helpful.

d [19/May/2006:17:43:44 +0200] [Job 89] STATE: none
D [19/May/2006:17:43:44 +0200] [Job 89] printer-uri = "ipp://iddz1ux.econ.ucl.ac.be:631/printers/d113_hplj4200"
D [19/May/2006:17:43:44 +0200] [Job 89] requesting-user-name = "guest"
D [19/May/2006:17:43:44 +0200] [Job 89] job-name = "Test Page"
E [19/May/2006:17:43:45 +0200] [Job 89] Print file was not accepted (Bad Request)!
d [19/May/2006:17:43:45 +0200] [Job 89] STATE: none

This is relevant part. Print file was not accepted? debug2 of error.log on cups server would explain why your print file was not accpeted. Please, attach error.log (while LogLevel debug2) of server.

Dear Ante,
attached you will find the requested cups error_log of the cups-SERVER in debug2 mode.
I tried to print a test page via my cups-client using the http interface.
My ip is: 130.104.186.126
There is an accept client: 10 and an accept client 11 with my ip.
No idea which one is the relevant.
At the end of the error log there a printing task going trough (not from my computer) before (my) client 10 is closed.
By the way the cups-version on the server is cups 1.1.19 - but that shouldn't be a problem when using IPP-protocol, I guess?

If you can, could you try with daily LiveCD?

This is a long shot:

reinstall hpijs foomatic-db-hpijs (apt-get --reinstall install hpijs foomatic-db-hpijs)

Ok - I will download the daily LiveCD and try again.

What I already tried is the recommended reinstallation of hpijs and foomatic-db-hpijs but without any change.

By the way, the problem does not seem to be caused by the driver or ipp: Our system administrator gave me (temporary) write access the the printer directly. It is a HP LaserJet 4200 network printer which understands IPP - and guess what.
I could set up a ipp printer which talks to the printer directly via ipp - using the same driver as before and I can print!!
So the problem seems to be the communication between the cups1.2.0 client and the cups1.1.19 server. (our system administrator could not print over the server using a cups1.2.0 client on fedora 5, neither)

On Mon, 22 May 2006 14:38:30 -0000
Christian Göbel <email address hidden> wrote:

> administrator could not print over the server using a cups1.2.0
> client on fedora 5, neither)

That could be the fact that Cups1.2 was a bit broken. Dapper has some
fixes that FC5 doesn't, which fixes this issue. I tested 1.2 clients
with 1.x servers and that worked like a charm (after those fixes were
merged in Dapper; before them I coulnd't print either).

It could be some issue we are missing, so, I'm waiting for the results
of LiveCD to see what next we will do/try.

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

I am writing this from the live-cd session. Great.
Network is up.
I can ping the server.
I can ping the client.
I can look at the cups network interface of the server.
But I can NOT add a printer via the gnome-cups-manager.
First it seems that I can add the printer but finally the new printer does not show up.
Anny suggestions?

I will tak a look at the documentation on how to fully enable cups-network interface on my client and try to add a printer via the localhost:631

Without changing any permissions and trying to add a printer via the localhost:631 interface results in the following:
https://launchpad.net/distros/ubuntu/+source/cupsys/+bug/45500
This is with the daily (22/05/2006) live-cd.

On Mon, 22 May 2006 16:03:22 -0000
Christian Göbel <email address hidden> wrote:

> But I can NOT add a printer via the gnome-cups-manager.

Enable browsing on server and printer will apear automaticly (after
you enable LAN printer detection in gnome-cups-manager). You can't add
it since you can't write to CD.

Thanks for your effort.

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

Oh dear, that means that I have to convince our system administrator (tomorrow, since he has already left) to temporarily enable browsing on the server.
I will try that tomorrow.
Thank a lot for YOUR effort. :)

Dear Ante,
sorry, but there was no way to convince our system administrator to enable browsing on the print-server. :(
(Actually browsing is on - but there is a restrictive firewall which prevents that the computer can actually be browsed.) The print server has once been attacked by evil hackers and the administrator has developed some paranoia. He just refuses any modification/change of the firewall rules and he will not take the firewall down for some minutes. (The server manages printing for ca. 100 Windows computer).
Fortunately he found a way to enable printing for me. He setup a new print-server with cups 1.2.0 (fedora5) for me; and I can print using this sever. (I guess in the long run he will switch to cups 1.2.0 for the whole institute, anyway)

To sum up, this means that I can not test the print-setup with the live cd.
If I can do anything else, please let me know.

On Tue, 23 May 2006 09:09:28 -0000
Christian Göbel <email address hidden> wrote:

> sorry, but there was no way to convince our system administrator to
> enable browsing on the print-server. :( (Actually browsing is on -
> but there is a restrictive firewall which prevents that the computer
> can actually be browsed.) The print server has once been attacked by

Since I have tested 1.1.x and 1.2 cups in all combinations, and found
it working without problems, I can't confirm your problem.

On the other hand, you setup seems very complex (firewall rules,
etc...) it is possible that somewhere something is disabled/restricted,
that otherwise should be enabled. I'll leave this bug open, but there's
nothing I can do at the moment.

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

Ante,
have you once tried to add the printer from a cups-1.1.* server via the gnome-cups-manager WITHOUT the auto-detect of the LAN printers?
(just by copying the uri and choosing the print-driver)

As soon as Dapper is stable I will make a clean install on my laptop and try again. But it is like you said this is not a standard setup: In addition all printing demands pass by a quota backend. (written in perl - by our administrator - however he already checked that it is not his backend which causes the problems).
There must be some subtle changes between the release candidate and the final version of cups1.2.0 which is at the root of the problem.
Thanks a lot for your efforts.
Best regards

On Tue, 23 May 2006 10:54:24 -0000
Christian Göbel <email address hidden> wrote:

> have you once tried to add the printer from a cups-1.1.* server via
> the gnome-cups-manager WITHOUT the auto-detect of the LAN printers?
> (just by copying the uri and choosing the print-driver)

Yes, 2 weeks ago and now, again. It works.

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

Cups 1.2.1 has the following fix to ensure that cups1.2.x works well with old Cups version ("like Cups1.1.17") I don't know if this also applies to cups1.1.19, though. I didn't find the info in the change-log of previous cups version.

Copy/past from Cups1.2.1 announcement
"The scheduler no longer uses chunking in responses to clients - this caused problems with older versions of CUPS like 1.1.17 (PR #6143)"

Here is the link:
http://www.easysw.com/~mike/cups/newsgroups.php?s1711+gcups.commit+v1720+T0

Has this been applied to the cups1.2.0 of ubuntu?

As the current release cups 1.2.0-0ubuntu5, that patch has not been applied (see Changelog at:
http://changelogs.ubuntu.com/changelogs/pool/main/c/cupsys/cupsys_1.2.0-0ubuntu5/changelog )

I am updating all the bugs about issues printing from cups 1.2 client to cups 1.1.X server. Could you give me a description of the bug or error message? "network printing regression" is not very informative. Thanks.

@manu
I realy wonder what to put here - we already tried to find out what the problem is, but we didn't came up with a satifying conclusion.
Anyway here are some proposals (pick one if you like):

/usr/lib/cups/backend/http failed
or
Print file was not accepted (Bad Request)!
(/usr/lib/cups/backend/ipp) stopped with status 1!
or
upsdAuthorize: Local authentication certificate not found!

I am afraid of putting a misleading description.

@ Christian

the first step is to have clear what the error is. I cannot put

Print file was not accepted (Bad Request)!
(/usr/lib/cups/backend/ipp) stopped with status 1!

because that is bug 42513

I cannot either put

upsdAuthorize: Local authentication certificate not found!

because that is bug 45099

So, please, tell me what is different in this bug from those, or either we should mark this as a duplicate of one of them.

Sorry, Manu - the user cases described are too different. I am not a printing expert, I am just a user who is using dapper in an office environment.
I put a comment to bug 45099 some days ago, that his might be a duplicate.
Bug 42513 is talking about kdeprint and lpr - I don't even know exactly what that means.
So, yes, perhaps these three bugs are caused by the same issue - but I cannot evaluate that.
By the way: Ante, who tried to track the problem down and who knows about this three bugs didn't mark them as duplicates - I take that as evidence that even experts are not sure about this, so please don't expect ME to make claims like that. However I hope that I delivered all information which is necessary for an expert to say if this is the same issue.
Thanks for you effort! Sorry that I am so stupid. :(

Come on man, don't be that way! Was I harsh? Did I sound dictatorial? I really didn't mean it, so excuse me, please.

I am just another user, helping to keep bug reports clean and tidy, not printing expert or guru either. I was just asking whether you knew the difference, or whether you can point the duplicates. You don't know it. I don't know it. Nobody is stupid here.

Sorry again if I sounded harsh before.

Anyway, there is a experimental (HIGHLY EXPERIMENTAL and UNTESTED) package build by an user for bug 42513 here http://www.omat.nl/cups/

One user reported that it fixed his issue, however, other users reported that it gave more errors. You may tested it (at your own risk) and tell us your result.

Could you please try packages from http://www.grad.hr/~ivoks/ubuntu/cups. This is CUPS1.2 packaged for Dapper.

Thank you

Thanks a lot for providing the cups 1.2.1 packages - I will try them tomorrow.

Now for the record:
I just installed a fresh ubuntu 6.06 LTS on my harddisk and tried to install the printer (like described in the original bug-report).

I used gnome-cups-print manager and installed the printer using the ipp-protocol via the cups 1.1.* server.
I could print a first test-page from cups-gnome-manager!
Unfortunately I could NOT print any further testpages (neither form the network interface nor from the gnome-cups-manager). All printing jobs have been canceled like described in the original report.
So the issue might be the same as in bug 42513 where printing over IPP sometimes worked and sometimes not.

Hm... This is *not* how cups should work, but it seems to fix issues for me. In /etc/cups/cups.d/ports.conf rename Listen localhost:631 to Listen 631 and restart CUPS. This enables browsing and printing (to) printers on 1.1.2x server. I repeat, this is *not* how cups should work.

I'll compile upstream sources to see if this is upstream or ubuntu error.

No, "Listen" changes won't help. This is upstream bug. Browsing doesn't work correctly, but you should try manualy adding printer. Some users reported this to be a workaround for non-working browsing.

Just for the record:
I added the printer manually (like I have always done)

As promised I tested printing with the experimental cups1.2.1 packages:
After an apt-get update and apt-get upgrade
1) I deleted all printers
2) restarted cups
3) added the printer manually
4) tried to print a test-page from gnome-cups-manager - failed
5) tried to print a test-page from the web-interface - failed

It seems that the provided packages for cups1.2.1 do not solve my network printing regression problems.

Attached you will find the (standard) error_log provided by cups1.2.1. when I tried to print using http(ipp) backend to print over a cups1.1.* server.

@Christian
@ Ante

from your log, it seems to me this is a duplicate of bug 45099. I would wait Ante to confirm it, though.

No, it isn't. This are unofficial packages with SSL support, so certificate errors are expected. What's relevant in this log is "Print file was not accepted (Bad Request)".

Btw, "certificate errors" aren't important. I'm testing something and will report if I my doubts are true...

Actully, this bug is fixed, but printing is not :)

Can confirm print jobs 'auto-cancelling' with "Local authentication certificate not found" in /var/log/cups/error_log. This is a newly-upgraded dapper client printing to a breezy server via http (on same LAN, no firewalls or other complexities). Upgrading the client to 1.2.1 made no difference.
Upgrading the SERVER to dapper (and thus 1.2.0) also hasn't fixed things but that's another story, see #44931.

@WalterNicholls,

Sorry, my fault, as Ante said:
"Local authentication certificate not found" in /var/log/cups/error_log aren't important. What's relevant in this log is "Print file was not accepted (Bad Request)".

So sorry for the confusion. Also, Ante is working on this. Please, patience.

Final Hint: if you write "see bug 44931" instead of "see #44931", the web interface generates a nice link to the bug report.

Ante, if you are working on this, shouldn't it be assigned to you? Sorry if this is a silly question, I am not such an expert in Bug Squashing.

manu wrote:
> @WalterNicholls,
>
> Sorry, my fault, as Ante said:
> "Local authentication certificate not found" in /var/log/cups/error_log aren't important. What's relevant in this log is "Print file was not accepted (Bad Request)".
>
Yes, that's just the last error line of many ... I was just trying to
pick out which symptoms since the comments against this bug # mentioned
sevearl others. In some respects the important thing to say wasn't so
much what is actually going wrong, it's more "this is something that
Dapper broke" <g>
> So sorry for the confusion. Also, Ante is working on this. Please, patience.
>
I passed this ("patience") on to my wife, whose laptop it is that can't
print (mine is Windows XP still unfortunately). Her reply was along the
lines of "but I still need to print!" Needless to say she is eagerly
awaiting a resolution. Fortunately she can still access an alternative
different printer
> Final Hint: if you write "see bug 44931" instead of "see #44931", the
> web interface generates a nice link to the bug report.
>
I see thanks. I'm used to Trac which uses the # syntax.

Ok ok, I'm being patient now! Tempting as it is to downgrade both
machines (client and server) back to breezy...

- Walter

I'm working on it, but don't assigne me, everybody is welcome to participate :)

@Walter and other

please take a look at my last postings in bug 45099 for a temporery/final solution.

Thank you.

I just downgraded back to cups1.2.0 using the script provided at bug 45099.
Since I cannot enable browsing on the server I tried to add the recommended raw / queue.

Trying to print a testpage I got the usual:
Queue "/usr/lib/cups/backend/http failed"
So this doesn't seem to work for me.

@ Christian

Yup, your case is rather special :/ What version of CUPS is on that server? You should try with cups 1.2.1, but please wait untill I create new 1.2.1 packages...

@ante
The print server is running cups1.1.19 (on RedHat).

@ante
If you want me to test new cups packages just let me know.

@Christian

New packages :)

Could you add:

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

to /etc/apt/sources.list and do an update/upgrade? Please report results. Thank you.

The problems seem to persist with the new cups 1.2.1. package

Here is what I have done:
1. deleted all printers
2. installed cups 1.2.1. using apt-get update / upgrade
3. installed the network-printer manually using gnome-cups-manager and the recommended postscript-driver
4. changed the options of the printer (from letter to A4)
5. printing a testpage using: http://localhost:631/printers/ the following message appear beside the selected printer
"/usr/lib/cups/backend/http failed"

Here is the output from the (standard) error-log:
E [19/Jun/2006:09:43:53 +0200] cupsdAuthorize: Local authentication certificate not found!
E [19/Jun/2006:09:43:53 +0200] cupsdAuthorize: Local authentication certificate not found!
E [19/Jun/2006:09:45:16 +0200] [Job 105] Print file was not accepted (Bad Request)!
E [19/Jun/2006:09:45:16 +0200] PID 6772 (/usr/lib/cups/backend/http) stopped with status 1!
E [19/Jun/2006:09:54:23 +0200] Resume-Printer: Unauthorized

OK, can you do a simple test? Open your web browser, go to:

http://IP_OF_PRINTER_SERVER:631/printers/NAME_OF_PRINTER_QUEUE

and try printing test page from web interface.

I just went to the web-interface of the cups-server - selected the printer and
printed successfully a test-page.
(Remember that I could print testpages from Dapper flight5 and all previous Ubuntu versions)

All right...

Please, in /etc/init.d/cupsys, replace line:

start-stop-daemon --start --quiet --oknodo --pidfile "$PIDFILE" --exec $DAEMON

with line:

start-stop-daemon --start --quiet --oknodo --pidfile "$PIDFILE" --exec /usr/bin/strace $DAEMON &> /tmp/cupsys-strace

install strace package and restart CUPS. Try printing to remote printer and, when it fails (after minute or two), stop cups and attach /tmp/cupsys-strace. This could be a very large file :/

@ante
I tried to follow your description - however I was not sure what "printing to remote printer" means :-(
Here is what I have done:
1. I edited /etc/init.d/cupsys like required
2. stopped cupsys, started cupsys
3. tried to print a testpage from the web-interface of cups
4. Job has been paused after some seconds (like it always does)
5. I waited perhaps for one minuter before stopping the server again.

As you will see the strace-file is not too big. Hope this is helpful anyway.

I am running Fedora5 with Gnome and got to this bug sheet by Google
      /usr/lib/cups/backend/socket failed
I have been frustrated with Cups on Gnome for a long time - I don´t really know what the problem is, but my solution for hung print queue is to go into the print dialogs via http://localhost:631/ and turn off (sometimes is already off) and then start the affected printer. This seems to do the trick.

My printer is a HP 2100/M/TN and I am using jetdirect with ipp://xxx.xxx:9100/ to connect.

Might be related, hence why I'm not opening a new bug:

Xerox Tektronix Phaser6250 with inbuilt IPP support. Used to work fine in Breezy, no longer works in Dapper.

Tried:
 Deleting and manually adding all printers (Printer does not support browsing)
 Uninstalling cupsys (apt-get --purge remove cupsys) and then reinstalling all removed packages.
 "sudo foomatic-cleanupdrivers"
 "sudo /usr/share/cups/enable_browsing 1" (on the off chance that it might help)

Other notes:
 From /var/log/cups/error_log:
E [26/Jun/2006:11:42:54 +1000] [Job 239] No %%BoundingBox: comment in header!
E [26/Jun/2006:11:43:05 +1000] PID 10703 (/usr/lib/cups/backend/http) stopped with status 1!

(cupsdAuthorize certificate stuff as well, but apparently that's not a problem).

Driver:
 Using the Tektronix Phaser 850 driver (worked in Breezy and Hoary with this same printer) in Postscript mode (only mode supported).

Current Workaround:
 Shifted to LPR printing (which the Phaser supports).

I had the "/usr/lib/cups/backend/http failed" error when I used 'http' and I had the 'Unable to get printer status (client-error-forbidden)' error when I used 'ipp' as the protocol.

This all happened after I upgraded to Dapper (printing was working fine before that).

I found all my problems went away when I upgraded to cups1.2.1 from cups1.2.0. This is not an official release, so I got it from: http://packages.debian.org/testing/libs/libcupsys2

You need these packages installed in this order. The package manager will complain that there are older versions available in the channel.

libcupsys2
libcupsimage2
cupsys

This is the path I used to the printer when configuring:
http://192.168.x.x:631/ipp

Jen

This should help some subscribers here:

 cupsys (1.2.1-0ubuntu1) dapper-updates; urgency=low
 .
   * Upgrade to new upstream version 1.2.1 (backported from edgy):
     - fix for printing on Xerox IPP printers; Closes: LP#47387
     - fix for banners on single page
     - fix for custom page sizes (cups ignores them now in some cases)
     - fix for -u and -U switches for lpadmin
     - fix for printing on some Canon printers
     - fix for printing on CUPS server < 1.1.17 (RHEL3 and older)
       (partly fixes LP bug #42802)
     - couple of fixes for imagetoraster
   * Add debian/patches/00_r5643.dpatch: Pull some fixes from upstream SVN
     scheduled to go into 1.2.2:
     - The lpstat command did not use the correct character
       set when reporting the date and time (STR #1751)
     - The cupsaddsmb command and web interface did not update
       the Windows PPD files properly, resulting in corrupt
       PPD files for the Windows client to use (STR #1750)
     - The cupsd.conf man page didn't describe the Listen
       domain socket syntax (STR #1753)
     - The scheduler no longer tries to support more than
       FD_SETSIZE file descriptors.
     - The USB backend now reports a "no such device" error
       when using the old filename-based USB URIs instead of
       the "success" error.
     - Increased the HTTP and IPP read timeouts to 10 seconds,
       as 1 second was too short on congested networks (STR
       #1719)
     - Fixed another file descriptor leak when printing raw
       files (STR #1736)
     - The scheduler didn't always choose the least costly
       filter.
     - Fixed parsing of IPv6 addresses in Allow, Deny,
       BrowseAllow, BrowseDeny, and BrowseRelay directives
       (STR #1713)
     - Special cases for the "localhost" hostname did not
       work, causing printing to not work when the /etc/hosts
       file did not contain a localhost entry (STR #1723)
     - Updated the Spanish translation (STR #1720)
     - Reverse-order page output was broken when N-up or
       landscape orientations were used (STR #1725)
     - The parallel, serial, socket, and USB backends needed
       print data before they would report back-channel data,
       causing problems with several new drivers (STR #1724)
   * Ship /etc/cups/ssl directory. Closes: LP#44931
   * Removed debian/patches/svn*.dpatch, these were backported from 1.2.1 in
     1.2.0-0ubuntu3.
   * debian/cupsys.init.d: Add missing log_end_msg. Closes: LP#48116
   * Bump up shlibs to >= 1.2.1 for compatibility safety.

I updated the cups packages via the Update Manager.
Now the new 1.2.1-0ubuntu1 packages are installed.

I installed a printer using the http backend - and got the usual error.

Here is the output of the (standard) cups error_log when I tried to print a test-page from the gnome-cups-manger directly after installing the printer:

E [08/Jul/2006:16:25:45 +0200] Creating missing directory "/var/run/cups/certs"
E [08/Jul/2006:16:55:10 +0200] CUPS-Add-Modify-Printer: Unauthorized
E [08/Jul/2006:16:55:18 +0200] CUPS-Delete-Printer: Unauthorized
E [08/Jul/2006:16:55:38 +0200] [Job 8] No %%BoundingBox: comment in header!
E [08/Jul/2006:16:55:40 +0200] [Job 8] Print file was not accepted (Bad Request)!
E [08/Jul/2006:16:55:40 +0200] PID 6600 (/usr/lib/cups/backend/http) stopped with status 1!

 cupsys (1.2.2-0ubuntu1) edgy; urgency=low
 .
   * Merge to Debian unstable:
     - This gets rid of /etc/cups/conf.d/ again and re-merges the separate
       browsing and ports settings to /etc/cups/cupsd.conf again. Separating
       was nice for preserving an unchanged conffile for the most important
       settings, but it broke KDE and the web interface and generated way too
       many bugs. Closes: LP#37892, LP#50804, LP#53582
    * Update to new upstream version 1.2.2 (UVF exception granted by by Matt
      Zimmerman):
      - Fixes printing to 1.1.x servers. Closes: LP#42513, LP#42802
      - Fixes parsing of some PostScript files which previously generated empty
        pages. Closes: LP#51432
      - Fixes parsing of network masks. Closes: LP#52390
      - Lots of more fixes, see upstream changelog.
   * debian/cupsys.preinst: Drop some obsolete migration bits for
     Breezy->Dapper upgrade.
   * debian/control: Add libdbus-1-dev build dependency to enable dbus support.
   * debian/cupsys.examples: Do not ship .svn files (upstream Makefiles install
     them).
   * cupsys.postinst: Fix permissions of cupsd.conf to be writable by user
     cupsys world-readable.
   * debian/local/enable_{sharing,browsing}, {sharing,browsing}_status: Adapt
     to new single configuration file format.
   * debian/rules: Clean cups/raster.h symlink to unbreak source package build.
   * Add debian/patches/ubuntu-disable-browsing.dpatch: Disable browsing by
     default to avoid open port and stay compatible to previous releases.

Fix is appropriate for dapper-updates, too.

sysv-rc (>= 2.86.ds1-14.1ubuntu2) is not available in dapper....

I just now have made my first print in Dapper in combination with old cupsserver and KDE! Thanks for this package!

Hi Tom,

Tom Albers [2006-07-24 11:15 -0000]:
> sysv-rc (>= 2.86.ds1-14.1ubuntu2) is not available in dapper....

Erm, of course it is not. I released the package for edgy so far, the
dapper task is still open. We will test 1.2.2 a bit and then update
dapper in some days if all goes well.

 cupsys (1.2.2-0ubuntu0.6.06) dapper-updates; urgency=low
 .
   * New upstream bugfix release:
      - Fixes printing to 1.1.x servers. Closes: LP#42513, LP#42802
      - Fixes parsing of some PostScript files which previously generated empty
        pages. Closes: LP#51432
      - Fixes parsing of network masks. Closes: LP#52390
      - Lots of more fixes, see upstream changelog.
   * Dropped debian/patches/00_r{5643,5660}.dpatch: Upstream now.
   * debian/patches/02_configure.dpatch,
     debian/patches/09_runasuser_autoconf.dpatch: Adapted to new upstream
     version (taken from current edgy package).