OK, I am not necessarily looking for someone to fix my issue here, but wanted to report this to PCLOS devs and maybe this might help someone else?............
Since 2009, I seem to have a problem with printerdrake (PcLinuxOs Control Center-Hardware-Printers) or associated packages(Synaptic) like HPLIP not getting along with my scanner or PCC.
In 2009, I had to remove all non-needed printer files and HPLIP-related......library directories, etc that were installed all at the same time and eventually printerdrake and scannerdrake (PCC-Hardware-Scanner) behaved and wouldn't lock or kick me out.
In 2010, similar issue, but more specific on the fix.............this time, I got disgusted with printerdrake locking up my PCCenter and the scanner doing its install fits. I removed printerdrake and it also took the following packages with it........printerdrake-common, postscript-ppds, hplip-model-data and gutenprint-foomatic, AND reinstalled hp-foomatic-db..........................................................now, I went into my CUPS web browser interface(
http://127.0.0.1:631/printers/myprinter) and it would not find nor install the printer. Taking a break from that, scannerdrake in PCC immediately did its thing ok and with my firmware from 2009 I had no install issues. So, back to the printer, I copied over my .ppd for my p-2250 from the old 2009 install and manually browsed for it as my printer driver in CUPS (
http://127.0.0.1:631/printers/myprinter) and it installed like a gem. So, as not to be off on updates in PCC and be properly up-to-date, I went to reinstall printerdrake in Synaptic to see what happened........it undid the package removal/additions mentioned above. Printed a test page from PCC printerdrake (which shot out all kinds of garbage the one time I did get my printer driver installed) and it was now printing awesome. So, I guess one result of this post is.......having probs with printerdrake? use CUPS web interface after uninstalling printerdrake, then reinstall it......NOT A FIX.........just another user suggestion.....
It would seem that printerdrake and HPLIP either have a cow about the older parallel printers to the point it causes issues like mine....(as mine as never worked in HPLIP despite 100% compatibility reported by HP, and I have installed it from source with parallel enabled just to see if that would help).........wonder what is up with it? Hope it might help someone find the gremlin........
