Bug 1404386

Summary: Export to PDF creates a blank PDF
Product: [Fedora] Fedora Reporter: Andrig Miller <andrig.t.miller>
Component: freecadAssignee: Richard Shaw <hobbes1069>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 26CC: cz172638, hobbes1069, john
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:52:36 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:

Description Andrig Miller 2016-12-13 17:22:19 UTC
Description of problem:

When using the Export to PDF menu item, a PDF is created, but its blank.

Version-Release number of selected component (if applicable):

OS: "Fedora release 25 (Twenty Five)"
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.16.Unknown
Build type: Unknown
Python version: 2.7.11
Qt version: 4.8.7
Coin version: 3.1.3
OCC version: 6.8.0.oce-0.17


How reproducible:

Every time.


Steps to Reproduce:
1. Open a CAD file
2. Select File->Export to PDF
3. Enter the file name and save

Actual results:

A blank PDF is created

Expected results:

A PDF with a 2D representation of the 3D image should be created.


Additional info:

This seems to work on this same version on other platforms, so may be a Fedora specific issue, as someone in the FreeCAD forums tried to reproduce the issue, but didn't.  There were on Windows with the same version.

At one time this worked fine, as I have PDF's from models in the past, and this is a necessary function to have working, as when you have parts CNC machined from a 3D CAD model, almost all machine shops want a PDF or SVG with directions for threading (thread dimensions and depth).

Comment 1 Fedora End Of Life 2017-11-16 19:50:15 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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.

Comment 2 Fedora End Of Life 2017-12-12 10:40:56 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.

Comment 3 Andrig Miller 2017-12-12 16:57:19 UTC
Yet, another bug I opened that no one ever looked at, and now its being closed.

It would be nice if someone actually looked at the bug, after all its been open for a year.

Comment 4 Richard Shaw 2017-12-12 19:53:23 UTC
When originally reported I did a search but didn't find much. Checking now here's a forum post for a possible work around.

https://forum.freecadweb.org/viewtopic.php?f=3&t=16814&hilit=pdf+export+blank&start=10

When you run into these types of problems it's usually best to search upstream first to see if it's a packaging error or not. If not, it's been to report upstream.

Comment 5 Fedora End Of Life 2018-05-03 08:09:44 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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.

Comment 6 Fedora End Of Life 2018-05-29 11:52:36 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.