-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
P4
-
Affects Version/s: 8, 21, 25, 26
-
Component/s: client-libs
-
None
-
Environment:
- CUPS running
- One printer as default is defined
-
x86_64
-
linux
When looking for a named printer with PrintServiceLookup.lookupPrintServices() using a AttributeSet containing the PrinterName attribute a phantom IPP printer is returned in Linux when CUPS is running and a default printer is defined.
Expected behavior:
It is expected that no print service will be found on the sun.print.PrintServiceLookupProvider. In our case a other PrintServiceLookup implementation is actually providing the correct PrintService implementation in this case.
Actual findings:
In my investigations I could pin down the source of the problem seems to be in the method "PrintService getServiceByName(PrinterName nameAttr)" within the sun.print.PrintServiceLookupProvider class caused by the special treatement of CUPS, not actually checking for the real existence of this given printer name... (line 456 of the Java 25 implementation)
Expected behavior:
It is expected that no print service will be found on the sun.print.PrintServiceLookupProvider. In our case a other PrintServiceLookup implementation is actually providing the correct PrintService implementation in this case.
Actual findings:
In my investigations I could pin down the source of the problem seems to be in the method "PrintService getServiceByName(PrinterName nameAttr)" within the sun.print.PrintServiceLookupProvider class caused by the special treatement of CUPS, not actually checking for the real existence of this given printer name... (line 456 of the Java 25 implementation)