To reproduce this bug, run the regression test
test/java/awt/PrintJob/PrintComponentTest/PrintComponentTest.java.

From the "Print" menu, select "Print to Printer". Select a device and click OK.
The following exception appears:

Exception occurred during event dispatching:
java.lang.NullPointerException:
        at sun.awt.windows.WGraphics.getDeviceColorModel(WGraphics.java:137)
        at sun.awt.windows.WGraphics.lock(WGraphics.java:772)
        at sun.java2d.loops.LockableRaster.<init>(LockableRaster.java:97)
        at sun.java2d.loops.RasterOutputManager.drawString(RasterOutputManager.j
ava:2483)
        at sun.java2d.loops.RasterOutputManager.drawString(RasterOutputManager.j
ava:2394)
        at sun.java2d.SunGraphics2D.drawString(SunGraphics2D.java:2224)
        at MainFrame$LWButton.paint(PrintComponentTest.java:225)
        at java.awt.Container.paint(Container.java:762)
        at MainFrame$LWContainer.paint(PrintComponentTest.java:246)
        at java.awt.Container.paint(Container.java:762)
        at java.awt.Component.print(Component.java:1797)
        at java.awt.Container.print(Container.java:802)
        at sun.awt.windows.WComponentPeer.print(WComponentPeer.java:93)
        at sun.awt.windows.WCanvasPeer.print(WCanvasPeer.java:47)
        at sun.awt.windows.WPanelPeer.print(WPanelPeer.java:24)
        at java.awt.Component.printAll(Component.java:1822)
        at MainFrame$ActionPrint.actionPerformed(PrintComponentTest.java:162)
        at java.awt.MenuItem.processActionEvent(MenuItem.java:443)
        at java.awt.MenuItem.processEvent(MenuItem.java:407)
        at java.awt.MenuComponent.dispatchEventImpl(MenuComponent.java:211)
        at java.awt.MenuComponent.dispatchEvent(MenuComponent.java:203)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:229)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:63)

It looks like WGraphics is trying to access the ComponentPeer's ColorModel, but
no ComponentPeer is associated with a WGraphics which is created from a
PrintJob.

This bug is a regression from beta4.