On Sunday 17 July 2005 04:41 am, Karsten M. Self wrote:
> I've got a problem with the canon backend (which I don't use) hanging in
> CUPs.  My load average is currently 13+, and there's nothing I can kill
> to bring down the processes.
>
>     $ ps aux | grep ' [D] '
>     root     19562  0.0  0.0   3388   576 ?        D    Jul12   0:00
> /usr/lib/cups/backend/canon root     19505  0.0  0.0   3388   576 ?       
> D    Jul13   0:00 /usr/lib/cups/backend/canon root      1960  0.0  0.0  
> 3388   592 ?        D    Jul14   0:00 /usr/lib/cups/backend/canon root    
> 21916  0.0  0.0   3388   592 ?        D    Jul15   0:00
> /usr/lib/cups/backend/canon root      5799  0.0  0.0   3388   592 ?       
> D    Jul15   0:00 /usr/lib/cups/backend/canon root      6417  0.0  0.0  
> 3388   592 ?        D    Jul15   0:00 /usr/lib/cups/backend/canon root     
> 7555  0.0  0.0   3388   592 ?        D    Jul15   0:00
> /usr/lib/cups/backend/canon root      6884  0.0  0.0   3388   764 ?       
> D    Jul16   0:00 /usr/lib/cups/backend/canon root     18238  0.0  0.0  
> 3388   764 ?        D    01:35   0:00 /usr/lib/cups/backend/canon
>
>
> Any suggestions for fixing this or (since I don't have a canon printer)
> keeping the backend from running in the first place?
>
>
> Peace.
Hi, Karsten!
I had the same problem recently & was only able to rid myself of 2 different 
printer backends by completely  removing every vestige of any cups cache 
files. I suspect that this is a bug at lest with kde and maybe with the 
debian installer. I figure that the trick is in /var/log/cups  
and /var/run/cups and /etc/cups being completely removed and using dpkg to 
force a reinstall of the cups system from a downloaded .deb file. If you try 
to remove cups the dependencies will totally screw up your system.
I was able to get rid of my old printer back ends using this process. However 
I have been unable to get my new Samsung ML-2250 to actually print correctly. 
If you have any tips there please advise.
-- 
John Foster


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to