Comment 17 for bug 692568

We're still experiencing the same bug on multiple computers running 10.04 with HPLIP versions from 3.13.10 up to 3.14.10. Affected printers have been: M1536dnf, HP M125nw and the M1212nf.
The only workaround I've found so far that's susceptible for our end users who don't have admin rights is to run "cupsenable $PRINTERNAME" every few minutes via crontab. A real solution would be very useful.
(beh does not help us as we need the scanning capability of the hplip drivers).
I can provide more information if required.