https://bugzilla.redhat.com/show_bug.cgi?id=1276653
Bug ID: 1276653 Summary: fop fails to include some images Product: Fedora Version: 23 Component: fop Severity: high Assignee: r.landmann@redhat.com Reporter: wboessen@redhat.com QA Contact: extras-qa@fedoraproject.org CC: c.david86@gmail.com, java-sig-commits@lists.fedoraproject.org, mizdebsk@redhat.com, msimacek@redhat.com, msrb@redhat.com, rhbugs@n-dimensional.de, r.landmann@redhat.com
Created attachment 1087917 --> https://bugzilla.redhat.com/attachment.cgi?id=1087917&action=edit Complete output from fop on a failed run.
Description of problem:
When building a PDF from a .fo file on F23, some, but not all, external-graphic elements with a relative path to a file will generate a "SEVERE: File not found" image.
Version-Release number of selected component (if applicable): fop-2.0-2
How reproducible:
Always
Steps to Reproduce: 1. Have a directory tree like this: test.fo Common_Content/images/note.svg 2. include a tag like this in test.fo <fo:external-graphic width="auto" height="auto" content-width="24pt" src="url(Common_Content/images/note.svg)"/> 3. run fop
Actual results: Lots of tracebacks about missing images
Expected results: PDF renders with images, like fop-1.1 did.
Additional info: The errors for missing images can be interesting, as the path they refer to has the leading part doubled. The actual PDF does have empty gaps of the correct size for the missing image.
https://bugzilla.redhat.com/show_bug.cgi?id=1276653
Steve Bonneville sbonnevi@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sbonnevi@redhat.com
--- Comment #1 from Steve Bonneville sbonnevi@redhat.com --- Suspect this is related to upstream's https://issues.apache.org/jira/browse/FOP-2550 issue. Testing suggests there may be some sort of race in fop or batik going on here, because we're seeing different results when the .fo file is rendered with fop on the command line when compared to calling the render through Publican. (Direct render seems to result in fewer files having duplicated directory names in the fo).
https://bugzilla.redhat.com/show_bug.cgi?id=1276653
--- Comment #2 from Fedora End Of Life jkurik@fedoraproject.org --- This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
https://bugzilla.redhat.com/show_bug.cgi?id=1276653
Steve Bonneville sbonnevi@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|23 |24
--- Comment #3 from Steve Bonneville sbonnevi@redhat.com --- Known to also be an issue in Fedora 24, bumping version to keep this alive. Haven't yet tested on Fedora 25, will update when I have.
https://bugzilla.redhat.com/show_bug.cgi?id=1276653
--- Comment #4 from Fedora End Of Life jkurik@fedoraproject.org --- This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
https://bugzilla.redhat.com/show_bug.cgi?id=1276653
Fedora End Of Life jkurik@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |EOL Last Closed| |2017-08-08 08:20:33
--- Comment #5 from Fedora End Of Life jkurik@fedoraproject.org --- Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
java-sig-commits@lists.fedoraproject.org
-
bugzilla＠redhat.com -
Red Hat Bugzilla