Details
-
Bug
-
Resolution: Fixed
-
P4
-
7
-
b14
-
generic
-
generic
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8019035 | 7u45 | Neil Richards | P4 | Closed | Fixed | b01 |
JDK-8002063 | 7u40 | Unassigned | P4 | Closed | Fixed | b02 |
Description
An OpenJDK developer reported that :
---
Whilst trying to debug a printing problem, I noticed that the (Unix and
PostScript) printer spoolers in Java do not check what the result is of
trying to launch the OS print spooler command (often 'lpr' or 'lp').
As a result, if that exec'd command fails for any reason, that result
(and that reason) is lost, and the user left without any clue that
something is amiss.
---
---
Whilst trying to debug a printing problem, I noticed that the (Unix and
PostScript) printer spoolers in Java do not check what the result is of
trying to launch the OS print spooler command (often 'lpr' or 'lp').
As a result, if that exec'd command fails for any reason, that result
(and that reason) is lost, and the user left without any clue that
something is amiss.
---
Attachments
Issue Links
- backported by
-
JDK-8002063 Unix printing does not check the result of exec'd lpr/lp command
- Closed
-
JDK-8019035 Unix printing does not check the result of exec'd lpr/lp command
- Closed
- relates to
-
JDK-8044694 Fix finally lint warnings in sun.print
- Resolved