Re: Konica-Minolta 4750en crashed using CUPS 1.52 but not 1.50

Mark Blades wrote:

>> Mark Blades wrote:
>>
>> >> Mark Blades wrote:
>> >>
>> >> ....
>> >>
>> >> I forgot to mention that you probably need to copy the file
>> >> /usr/bin/pdftops
>> >> over to the new system if it does not already exist there.
>> >>
>> >> Helge
>> >>
>> > pdftops exists in /usr/bin  I think cups is using the version in
>> > /etc/cups/filters as pdftops was failing until I changed file
>> > permissions
>> > on the copied file to match the rest of the directory (755 I think). 
>> > Do I still need to replace the copy in /usr/bin?
>>
>> No, I don't think so. The filter  /usr/lib/cups/filter/pdftops is in fact
>> a wrapper program which calls either /usr/bin/pdftops or Ghostscript
>> depending on how cups gets configured on build time (which has been done
>> at Ubuntu's when building the rpm stuff).
>> And the 1.5.0 file you provided has been created by the /usr/bin/pdftops
>> utility, whereas the 1.5.2 file has been created by Ghostscript (version
>> 9.05).
>>
>> Helge
>>
> OK, copied the fiel from /usr/bin on the old machine to the same location
> on the new machine.  Same problem with the printer hanging  but I also had
> to cancel the job from cups as well. This was only successful after
> powercycling the printer which shows in the log as an unable to cancel
> print job.
> 
> E [03/May/2012:00:23:44 +0100] [Job 25] Unable to cancel print job.
> W [03/May/2012:00:23:48 +0100] failed to CreateProfile:
> org.freedesktop.ColorManager.AlreadyExists:profile id
> 'KONICA-MINOLTA-magicolor-4750-Gray..' already exists W
> [03/May/2012:00:23:48 +0100] failed to CreateProfile:
> org.freedesktop.ColorManager.AlreadyExists:profile id
> 'KONICA-MINOLTA-magicolor-4750-CMYK..' already exists W
> [03/May/2012:00:23:48 +0100] failed to CreateDevice:
> org.freedesktop.ColorManager.AlreadyExists:device id
> 'cups-KONICA-MINOLTA-magicolor-4750' already exists
> 
> any ideas?

Well, from the error message
"[Job 25] Unable to cancel print job."
I see that the printer is configured to use the IPP protocol. Could you try 
to reconfigure the printer to use a different protocol, e.g. socket?
As the printer has a web interface for setup and maintenance, you should log 
in there as an administrator and revise the protocol settings.

Helge