Bug 1174051
Summary: | error building PDF: ASSERT failure in QList<T>::operator[]: "index out of range" | ||
---|---|---|---|
Product: | [Community] Publican | Reporter: | Greg Sheremeta <gshereme> |
Component: | publican | Assignee: | Lee Newson <lnewson> |
Status: | CLOSED WONTFIX | QA Contact: | Ruediger Landmann <rlandman> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2 | CC: | cbredesen, lnewson, rlandman, ykatabam |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-29 17:08:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1172043 |
Description
Greg Sheremeta
2014-12-15 02:07:00 UTC
There are a couple workarounds to this: The first is to change the font via the publican.cfg "pdf_body_font" and "pdf_mono_font" properties. Normally it requires doing a bit of mixing and matching to find something that works. This approach has worked for all but 2 cases I've seen. The second is to revert to FOP as the pdf renderer, via the "--pdftool=fop" argument. However this has varying results and also tends to output a differently styled PDF. As such this isn't really an alternative internally. The last, which is really only an option for writers and is very much so a last ditch effort, is to add some some additional revision history entries or to rework some of the content. This then adjusts the number of pages ever so slightly, which then offsets the issue. Closing, we've worked around. |