On Tue, Sep 6, 2011 at 11:45 AM, Michael Mol <mike...@gmail.com> wrote: > On Tue, Sep 6, 2011 at 12:28 PM, Paul Hartman > <paul.hartman+gen...@gmail.com> wrote: >> On Tue, Sep 6, 2011 at 11:16 AM, Dale <rdalek1...@gmail.com> wrote: >>> This is rather odd. For the longest, every time I had a cups update, I had >>> to delete my printers then add them back again. It would not print until I >>> did so. >> >> I have to do that every time I plug my printer in... >> >> I print so infrequently, every time I want to print I turn the printer >> on and plug it into my PC, and then spend 25 minutes trying to make it >> work with CUPS again. > > Paul, I suspect you've got a udev configuration problem. Your printer > *should* get some kind of persistent symlink pointing to its device > node, probably derived from its serial number. If that isn't working > properly, fixing it should fix your recurring CUPS issues. If udev is > behaving properly, then perhaps CUPS is latching on to something more > transient.
IIRC the issue in my particular case is related to loading and unloading the usblp module. I have an HP LaserJet 1020 and use foo2zjs. Attaching the printer must be done in this order: modprobe usblp plug in printer rmmod usblp If I plug in then printer without usblp (if I have blacklisted the module), it won't work. If I plug in the printer and leave usblp loaded, it won't work. I must load usblp, plug in the printer and then rmmod usblp. If I add the printer in CUPS when it's in the wrong state, it won't work either. Usually I screw around with deleting/adding the printer until I remember what the solution was in the first place. :)
