[cups.general] Canon 6650 CUPS debug: failed to DeleteDevice: org.freedesktop.DBus.Error.InvalidArgs:Type of message, `(s)', does not match expected type `(o)'

Gernot Hassenpflug ha4h-grnt at asahi-net.or.jp
Tue Feb 19 17:41:13 PST 2013


Dave <djh999gc at gmail.com> writes:

> 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.
> 
> I've turned on CUPS debugging and output the debug log here:
> http://pastebin.ca/2315773
> 
> The suspicious section, to me, is:
> 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)'
> 
> Also, prior to setting debug, the error was:
> 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





More information about the cups mailing list