FULL PRODUCT VERSION :
Java 1.6.0_12-b04 with Sun Microsystems Inc. Java HotSpot(TM) Client VM mixed mode

ADDITIONAL OS VERSION INFORMATION :
  Customer is using glnx86, Linux - Fedora Core 5.

EXTRA RELEVANT SYSTEM CONFIGURATION :
Here is their printer configuration:

chesley@arjuna ~]$ /usr/sbin/lpc status
am:
printer is on device 'socket' speed -1
queuing is enabled
printing is enabled
no entries
daemon present
drudge:
printer is on device 'socket' speed -1
queuing is enabled
printing is enabled
no entries
daemon present
hp-laserjet:
printer is on device 'usb' speed -1
queuing is enabled
printing is enabled
no entries
daemon present

          * Please ask the user to send us the contents of the file /etc/printcap.

[root@arjuna cups]# cat ../printcap
# This file was automatically generated by cupsd(8) from the # /etc/cups/printers.conf file. All changes to this file # will be lost.
hp-laserjet|Created by redhat-config-printer 0.6.x:rm=arjuna:rp=hp-laserjet:
am|Created by redhat-config-printer 0.6.x:rm=arjuna:rp=am:
drudge|Created by redhat-config-printer 0.6.x:rm=arjuna:rp=drudge:


A DESCRIPTION OF THE PROBLEM :
When using Java 1.6.0_12-b04, the customer does not see 2 of his 3 printers in the Java printing dialog. These 2 network printers are:

Aquamarine is a HP color laserjet 4650dtn
Druge is a HP laserjet 4250tn

The printers DO appear with all the following JRE's:

Java 1.5.0-b64 with Sun Microsystems Inc. Java HotSpot(TM) Client VM mixed mode
Java 1.5.0_09-b03 with Sun Microsystems Inc. Java HotSpot(TM) Client VM mixed mode, sharing
ava 1.6.0_04-b12 with Sun Microsystems Inc. Java HotSpot(TM) Client VM mixed mode

It appears that with version Java 1.6.0_12-b04, the 2 printers return false for whether or not they support "printable" documents. With older JVMs, they return true. Since we only display printers that can support DocFlavor.SERVICE_FORMATTED.PRINTABLE, the printers are not being displayed.

Note that the one printer that does appear is a local printer.


REPRODUCIBILITY :
This bug can be reproduced always.

Release Regression From : 6u10
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.