Comment 3 for bug 164945

I do not know if it is exactly the same problem as yours. If I start up the computer with the printer off, apparently cups automatically flags the printer as not enabled. Even if I turn the printer on afterwards, the printer still appears in the computer as stopped and any job sent keeps sleeping in the queue. If I check the "enable" box, the printer start printing whatever is in the queue. An user without lpadmin privileges cannot reenable the printer an so, cannot print at all.
Before the last upgrade to Gusty, the printer was flag as "not enabled" and should be manually enabled only when I forgot to turn it on before sending a job. After the upgrade it is flagged as "not enabled" if it is off at computer startup. This may be logically justified only if there were some sort of deamon checking very frequently whether the printer has been turned on to re-enable it automatically but it does not seem to be the case. I would rather prefer that the printer is never automatically disabled. Does anyone know if this kind of behaviour is configurable somehow?
I think this is some sort of new cups feature intended as an improvement but which turns out to be a annoyance for many users.