Bug 1111216

Summary: [fix available] LibreOffice Calc: PDF export of an empty document fails with Write Error
Product: Red Hat Enterprise Linux 7 Reporter: Milan Barta <mbarta>
Component: libreofficeAssignee: David Tardon <dtardon>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.0CC: caolanm, dtardon, jkoten, lkolacek, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 08:50:19 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: 1119709    
Bug Blocks:    

Description Milan Barta 2014-06-19 13:34:13 UTC 
Description of problem:
When exporting an empty LO Calc document to PDF, the export fails with Write Error. Any other (Writer, Impress, Draw) empty document can be exported to PDF without an error.

The Error message: Error saving the document Unittled1: Write Error. The file could not be written.

If the possibility of exporting an empty Calc document isn't fixed, the error message should at least explain why the export failed and not only state that the file couldn't be written.

Version-Release number of selected component (if applicable):
libreoffice-core-4.1.4.2-3.el7.x86_64
libreoffice-calc-4.1.4.2-3.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open LibreOffice Calc with new empty document
2. Without editing the document click File -> Export as PDF... menu and save the file

Actual results:
Write Error message appears and the PDF file is not saved.

Expected results:
An empty PDF file is saved (as it is possible to do in Writer, Impress and Draw)

Additional info:
Comment 2 Jiri Koten 2014-11-19 13:32:33 UTC 
Not fixed, still getting the same error

libreoffice-4.2.6.3-3.el7
Comment 3 David Tardon 2014-11-21 12:31:39 UTC 
The patch got lost during the rebase...
Comment 7 errata-xmlrpc 2015-03-05 08:50:19 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0377.html