Mac-Shared Canon iP4300 printer no longer prints after upgrade to Jaunty 9.04

Bug #369438 reported by JMFTheVCI
8
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: cups

Previously on Intrepid 8.10 I could connect and print to my Canon iP4300 printer which is being shared on my iMac.
Since the upgrade (update-manager -d and then various updates since) I no longer see the printer.
I have to manually add the printer whereas previously the printer was magically discovered.
I add the printer as Network Printer > IPP > Provide host IP and the print queue is listed.
Verify says "the print share is not accessible".
I carry on and pick the correct driver. I can choose the printer to print to but /var/log/cups/error_log shows repeated lines of [Job xx] recoverable: Unable to connect to printer; will retry in 30 seconds...

This printer is working. It prints from the Mac and from Win XP (Bonjour) and *was* working fine on intrepid.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Lpstat:
 device for Canon-PIXMA-iP4300: ipp://Jason-Julie.local:631/printers/iP4300
 device for gbbaslci: ipselect://xemeaprt25.megacenter.de.ibm.com:7050/gbbaslci
 device for gbnhblz4: ipselect://xemeaprt24.megacenter.de.ibm.com:7048/gbnhblz4
 device for PDF: cups-pdf:/
MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
Package: cups 1.3.9-17ubuntu3
Papersize: a4
PpdFiles:
 generic: Generic PostScript printer
 gbnhblz4: Generic PostScript printer
 Canon-PIXMA-iP4300: Canon PIXMA iP4300 - CUPS+Gutenprint v5.2.3 Simplified
 gbbaslci: IBM EMEA Infoprint Color 1354 PS A4
 PDF: Generic CUPS-PDF Printer
ProcCmdLine: root=UUID=765e9485-1f4f-4f2c-a9b4-2ef70cc27137 ro quiet splash nc10-fb
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: cups

Revision history for this message
JMFTheVCI (jmfthevci) wrote :
Revision history for this message
JMFTheVCI (jmfthevci) wrote :

FIX! - By changing the printer driver to "Generic" - "Raw Queue" I can now print to my printer.
Why this should work rather than a device specific driver I have no idea.
Why this issue should show itself as a certificate error is the bug.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Your server's print queue already has the driver for your printer. So you can send PostScript, PDF, images, or text to it and the CUPS on the server converts your file to the printer's format. If you set up a printer driver also on your client, the printer's native format will be sent into the queue on the server, and this is an unknown format for CUPS and therefore the CUPS on the server refuses to print the job (this is a protection against paper waisting by sending for example an MP3 file to a printer, both accidentally or intendedly).

If system-config-printer identifies an IPP share on a server as a CUPS queue it usually does not ask for manufacturer and model. So I am wondering why it asked you in this case. Note also that I do not have a Mac. So I could test this feature only by setting up IPP queues pointing to Linux CUPS servers.

Revision history for this message
JMFTheVCI (jmfthevci) wrote : Re: [Bug 369438] Re: Mac-Shared Canon iP4300 printer no longer prints after upgrade to Jaunty 9.04

Till,

The issue was that the ipp was not detected properly. I could enter the
IP address of the iMac and it would show me the iP4300. But whatever
resulted by picking the iP4300 it kept prompting me for the drivers.

I am absolutely certain that the previous print manager tool on Intrepid
found the iP4300 and just dealt with it. I did not even have to point to
the iMac's IP address.

Jason

Till Kamppeter wrote:
> Your server's print queue already has the driver for your printer. So
> you can send PostScript, PDF, images, or text to it and the CUPS on the
> server converts your file to the printer's format. If you set up a
> printer driver also on your client, the printer's native format will be
> sent into the queue on the server, and this is an unknown format for
> CUPS and therefore the CUPS on the server refuses to print the job (this
> is a protection against paper waisting by sending for example an MP3
> file to a printer, both accidentally or intendedly).
>
> If system-config-printer identifies an IPP share on a server as a CUPS
> queue it usually does not ask for manufacturer and model. So I am
> wondering why it asked you in this case. Note also that I do not have a
> Mac. So I could test this feature only by setting up IPP queues pointing
> to Linux CUPS servers.
>
>

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Old bug Ubuntu 9.04 no longer supported, please upgrade to 14.04 LTS or higher and let us know if this is still happening.

Changed in cups (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in cups (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.