Canon 6650 CUPS debug (prints black page)

[Dave]

CUPS output using command line (lp) produces nearly full black page output. (Solid black field). Output using evince or libreoffice is ok.
64 bit drivers provided by Canon were RPM only, so they were converted to .deb with alien. This went normally. I can print with evince and libreoffice without issue. Printing from command line (lp filename.pdf) will produce the error whereas printing from a pdf GUI app (same file) will print ok.
http://pastebin.ca/2315773
D [19/Feb/2013:14:15:13 -0800] Loading printer Canon_6650...
D [19/Feb/2013:14:15:13 -0800] load_ppd: Loading /var/cache/cups/Canon_6650.data...
D [19/Feb/2013:14:15:13 -0800] Calling DeleteDevice(cups-Canon_6650)
D [19/Feb/2013:14:15:13 -0800] failed to DeleteDevice: org.freedesktop.DBus.Error.InvalidArgs:Type of message, `(s)', does not match expected type `(o)'
failed to CreateProfile: org.freedesktop.ColorManager.AlreadyExists:profile id 'Canon_LBP6650-Gray..' already exists
Thanks for any suggestions.

Maybe you can trace the filter chain used by evince/libreoffice compared to the lp output. Probably whatever settings Canon chose to implement doesn't fit Debian. For example, maybe Canon only implemented something to deal with incoming PostScript input, rather than PDF?
--
Gernot Hassenpflug

0) Apologies for doublepost above & for the messy title.
1a) OK Evince GTK print: http://pastebin.ca/2316390 (see lines 270 etc for filters).
1b) BAD lp print here: http://pastebin.ca/2316390 (see 328 etc for filters).
2) converted pdf to ps and tried to print with lp. Didn't work (resulted in black page).
3) filter chain: did compare the output of the debug error_log for evince to see if I could see differences in how it was handling filters. Not sure what I'm looking for here, pasted the successful log above at 1a-1b.
4) noticed that the CUPS web interface showed 2 different printers. When using lpoptions, I noticed that the first one ("Canon_6650") did not list options properly. The second ("Canon_LBP6650") did list options when prompted by lpoptions. Deleted the Canon_6650 printer from web interface. This may be a red herring, but mentioned anyway.
5) I removed cups/ghostscript and reinstalled it, but this didn't work.

Note the filter pstoufr2cpca is being used. I think this is a Canon creature. Any suggestions as to why evince GTK method prints ok whereas lp will not? Thanks very much for any lookins here.

[Dave]

Post by Dave

CUPS output using command line (lp) produces nearly full black page output. (Solid black field). Output using evince or libreoffice is ok.
64 bit drivers provided by Canon were RPM only, so they were converted to .deb with alien. This went normally. I can print with evince and libreoffice without issue. Printing from command line (lp filename.pdf) will produce the error whereas printing from a pdf GUI app (same file) will print ok.
http://pastebin.ca/2315773
D [19/Feb/2013:14:15:13 -0800] Loading printer Canon_6650...
D [19/Feb/2013:14:15:13 -0800] load_ppd: Loading /var/cache/cups/Canon_6650.data...
D [19/Feb/2013:14:15:13 -0800] Calling DeleteDevice(cups-Canon_6650)
D [19/Feb/2013:14:15:13 -0800] failed to DeleteDevice: org.freedesktop.DBus.Error.InvalidArgs:Type of message, `(s)', does not match expected type `(o)'
failed to CreateProfile: org.freedesktop.ColorManager.AlreadyExists:profile id 'Canon_LBP6650-Gray..' already exists
Thanks for any suggestions.

Maybe you can trace the filter chain used by evince/libreoffice compared to the lp output. Probably whatever settings Canon chose to implement doesn't fit Debian. For example, maybe Canon only implemented something to deal with incoming PostScript input, rather than PDF?
--
Gernot Hassenpflug

0) Apologies for doublepost above & for the messy title.
1a) OK Evince GTK print: http://pastebin.ca/2316390 (see lines 270 etc for filters).
1b) BAD lp print here: http://pastebin.ca/2316390 (see 328 etc for filters).
2) converted pdf to ps and tried to print with lp. Didn't work (resulted in black page).
3) filter chain: did compare the output of the debug error_log for evince to see if I could see differences in how it was handling filters. Not sure what I'm looking for here, pasted the successful log above at 1a-1b.
4) noticed that the CUPS web interface showed 2 different printers. When using lpoptions, I noticed that the first one ("Canon_6650") did not list options properly. The second ("Canon_LBP6650") did list options when prompted by lpoptions. Deleted the Canon_6650 printer from web interface. This may be a red herring, but mentioned anyway.
5) I removed cups/ghostscript and reinstalled it, but this didn't work.
Note the filter pstoufr2cpca is being used. I think this is a Canon creature. Any suggestions as to why evince GTK method prints ok whereas lp will not? Thanks very much for any lookins here.

Correction 1b) BAD lp print here: http://pastebin.ca/2315773

[Gernot Hassenpflug]

Post by Dave

Post by Dave

CUPS output using command line (lp) produces nearly full black page output. (Solid black field). Output using evince or libreoffice is ok.
64 bit drivers provided by Canon were RPM only, so they were converted to .deb with alien. This went normally. I can print with evince and libreoffice without issue. Printing from command line (lp filename.pdf) will produce the error whereas printing from a pdf GUI app (same file) will print ok.
http://pastebin.ca/2315773
D [19/Feb/2013:14:15:13 -0800] Loading printer Canon_6650...
D [19/Feb/2013:14:15:13 -0800] load_ppd: Loading /var/cache/cups/Canon_6650.data...
D [19/Feb/2013:14:15:13 -0800] Calling DeleteDevice(cups-Canon_6650)
D [19/Feb/2013:14:15:13 -0800] failed to DeleteDevice: org.freedesktop.DBus.Error.InvalidArgs:Type of message, `(s)', does not match expected type `(o)'
failed to CreateProfile: org.freedesktop.ColorManager.AlreadyExists:profile id 'Canon_LBP6650-Gray..' already exists

Maybe you can trace the filter chain used by evince/libreoffice compared to the lp output. Probably whatever settings Canon chose to implement doesn't fit Debian. For example, maybe Canon only implemented something to deal with incoming PostScript input, rather than PDF?

0) Apologies for doublepost above & for the messy title.
1a) OK Evince GTK print: http://pastebin.ca/2316390 (see lines 270 etc for filters).
1b) BAD lp print here: http://pastebin.ca/2316390 (see 328 etc for filters).
2) converted pdf to ps and tried to print with lp. Didn't work (resulted in black page).
3) filter chain: did compare the output of the debug error_log for evince to see if I could see differences in how it was handling filters. Not sure what I'm looking for here, pasted the successful log above at 1a-1b.
4) noticed that the CUPS web interface showed 2 different printers. When using lpoptions, I noticed that the first one ("Canon_6650") did not list options properly. The second ("Canon_LBP6650") did list options when prompted by lpoptions. Deleted the Canon_6650 printer from web interface. This may be a red herring, but mentioned anyway.
5) I removed cups/ghostscript and reinstalled it, but this didn't work.
Note the filter pstoufr2cpca is being used. I think this is a Canon creature. Any suggestions as to why evince GTK method prints ok whereas lp will not? Thanks very much for any lookins here.

Correction 1b) BAD lp print here: http://pastebin.ca/2315773

Unfortunately pastebin appears to have some problems, so I have not seen your files.
However, I would hazard a guess that evince is using PDF as a starting point, and converting to ps using one type of library (poppler or ghostscript) while lp is using PS as a starting point and using perhaps a different library (of either poppler of ghostscript).
Maybe you can see if you can successfully print from Adobe Acrobat Reader, which uses a third pdf to ps converter library.