^ You may change the driver on system-config-printer by double clicking on the installed printer (to open it's properties), close the "Option 'printer-resolution' has value '(unknown IPP tag)' and cannot be edited." message and on the printer properties where says "Make and Model" click "Change" and then "Choose Driver" -> "Provide PPD file" and browse /usr/share/ppd/HP for the model series of your printer, select the ppd file without "-hpijs" and finish it.
Anyway, I must correct my previous report, where I said that «Using the "hpcups" eliminated any error and I now can use both printers normally!» I should have said that although the red (!) exclamation mark disappeared and it prints normally, the error message "Option 'printer-resolution' has value '(unknown IPP tag)' and cannot be edited." is still displayed when opening the printer properties.
This error is related to python-cups 1.9.48-1+b1 bug, you may either install and updated version or wait that debian provides an updated version. See more information here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656640
^ You may change the driver on system- config- printer by double clicking on the installed printer (to open it's properties), close the "Option 'printer- resolution' has value '(unknown IPP tag)' and cannot be edited." message and on the printer properties where says "Make and Model" click "Change" and then "Choose Driver" -> "Provide PPD file" and browse /usr/share/ppd/HP for the model series of your printer, select the ppd file without "-hpijs" and finish it.
Anyway, I must correct my previous report, where I said that «Using the "hpcups" eliminated any error and I now can use both printers normally!» I should have said that although the red (!) exclamation mark disappeared and it prints normally, the error message "Option 'printer- resolution' has value '(unknown IPP tag)' and cannot be edited." is still displayed when opening the printer properties.
This error is related to python-cups 1.9.48-1+b1 bug, you may either install and updated version or wait that debian provides an updated version. See more information here: http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 656640