[cups] I cannot print using the Canon TS6000 series – CUPS+Gutenprint v5.2.13-2 driver.

[Bill]

Brian:

     Sorry, new to this.  Trying to report my observations re Xsane, 
sane, and CUPS and getting the addresses crossed.   Could use a "site 
map" or "flow chart"!

     Hopefully, I have added the correct address for this subject!

     In the response from Gernot Hassenpflug, the Canon maintainer from 
the gutenprint project, it looks like there will be support for this driver

in the near future.

Bill

******************************************

$ lpstat -l -e
Canon_Gutenprint_Driver permanent 
ipp://localhost/printers/Canon_Gutenprint_Driver 
usb://Canon/TS6200%20series?serial=30644B&interface=1
Canon_Pixma_TS6220 permanent ipp://localhost/printers/Canon_Pixma_TS6220 
usb://Canon/TS6200%20series?serial=30644B&interface=1
$ lpstat -t
scheduler is running
system default destination: Canon_Pixma_TS6220
device for Canon_Gutenprint_Driver: 
usb://Canon/TS6200%20series?serial=30644B&interface=1
device for Canon_Pixma_TS6220: 
usb://Canon/TS6200%20series?serial=30644B&interface=1
Canon_Gutenprint_Driver accepting requests since Tue 26 Feb 2019 
11:03:04 AM EST
Canon_Pixma_TS6220 accepting requests since Tue 26 Feb 2019 10:45:14 AM EST
printer Canon_Gutenprint_Driver is idle.  enabled since Tue 26 Feb 2019 
11:03:04 AM EST
printer Canon_Pixma_TS6220 is idle.  enabled since Tue 26 Feb 2019 
10:45:14 AM EST

**********************************************


On 3/4/19 9:41 AM, Brian Potkin wrote:
> Bill,
>
> You sent your last two mails only to me. I bounced them to the list.
> Please post to the list.
>
>
> On Mon 04 Mar 2019 at 08:24:01 -0500, Bill wrote:
>
>> Brian:
>>
>>      If I select "Canon_Pixma_TS6220" (which has driver "Canon TS6200 series
>> Ver.5.70"), the printer prints OK.  But if I select
> Please give the outputs of 'lpstat -l -e' and 'lpstat -t'.
>
>> "Canon_Gutenprint_Driver" (same printer as the former, but with driver
>> "Canon TS6000 series - CUPS+Gutenprint v5.2.13),
>> then the printer does not print.
> I think this is the wrong driver.
>