Bug 480085 - PDF generation hangs in openoffice.org
PDF generation hangs in openoffice.org
Status: CLOSED DUPLICATE of bug 477174
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Caolan McNamara
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-01-14 18:18 EST by Jonathan Corbet
Modified: 2009-01-14 18:28 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-14 18:28:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File I can't export to PDF (7.86 KB, application/vnd.oasis.opendocument.text)
2009-01-14 18:18 EST, Jonathan Corbet
no flags Details

  None (edit)
Description Jonathan Corbet 2009-01-14 18:18:30 EST
Created attachment 329051 [details]
File I can't export to PDF

Description of problem:

Attempts to export a document to PDF result in a hung openoffice.org

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

How reproducible:

Steps to Reproduce:
1. Run openoffice on a standard LWN invoice template
2. Try to export as PDF
3. Wait for the heat death of the universe
Actual results:

OpenOffice.org hangs.  Invoices do not get sent.  LWN doesn't get paid and goes out of business.  The entire Linux community mourns.

Expected results:

A shiny new PDF file.

Additional info:

The hang happens after the first click on the "export" button, before confirming the file name.  I can't reproduce it with a blank page, but I *can* reproduce it if I delete everything from the invoice file.  An example file is attached.
Comment 1 Caolan McNamara 2009-01-14 18:28:05 EST
I'm going to blame bug 477174 for now as its hopeless to attempt to use the gtk dialogs at the moment.

*** This bug has been marked as a duplicate of bug 477174 ***

Note You need to log in before you can comment on or make changes to this bug.