Ubuntu
cupsys package

  1. Dapper (6.06)
  2. Bug #55828
  3. Comment #15

Comment 15 for bug 55828

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote : Re: PJL output from 1.2.2-0ubtuntu0.6.06 client over IPP

> I merged /etc/cups/cups.d/browse.conf and ports.conf into
> /etc/cups/cupsd.conf, commented out the data in those two
> files and restarted cups. I tried to create a new printer using
> the KDE printer manager
> (ipp://server:631/printers/printername), selected the correct
> model and gave it the correct PPD file (from /etc/cups/ppd/)
> but it does exactly the same. Prints a few lines of garbage.

Does KDE printer manager ask for a PPD when setting up a network printer? As explained above the problem is that network printers normally don't need a PPD!

> I also tried the lpadmin way and that produced a printer that at > least can print, but somehow broke all admin interfaces on the
> two Dappers.

> Now, when I try to check out http://localhost:631 and view my
> printers I just get a page with "Bad request" where the printers
> should be, so now it's more broken than before.

This is probably bug #42513, which was fixed in cupsys 1.2.2-0ubuntu0.6.06. You probably did a downgrade to 1.2.0.
Please make sure you have cupsys 1.2.2-0ubuntu0.6.06.

> Trying to rename the printer with the KDE printer tool gives me > a simple error dialog with: "Unable to change printer
> properties. Error received from manager:
> client-error-not-found". No sane information is shown about
> the printer either, it is recognized as a "Local printer" insted of >an ipp:// printer as it should be.

KDE 3.5.2 print manager is broken when used with CUPS 1.2 due to KDE 3.5.2 using private CUPS API, more info here: http://www.kdedevelopers.org/node/1901.

> Pascal, thanks a lot for your patient help. I think we just need
> to wait for the CUPS folks to fix the bugs and then I probably > need to reinstall the systems in order to get it working as it
> should. This should teach me to blindly apply package
> upgrades. :(

Please don't blame the wrong people here. The problems are caused by KDE, Mike Sweet has informed the KDE people in advance and they haven't dealt with the problem when it was there. In the meanwhile the problem has been fixed but you will have to wait for Edgy to see these fixes.

But you should be able to use your printer with the CUPS web interface in KDE 3.5.2 and lpadmin as described above to setup your IPP printer!