Bug 81393 - Formulas get corrupted after exporting as PDF
Summary: Formulas get corrupted after exporting as PDF
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.4.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-15 17:32 UTC by Gayan Weerakutti
Modified: 2015-09-04 03:01 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Test File (69.25 KB, application/vnd.oasis.opendocument.text)
2014-07-16 08:07 UTC, Gayan Weerakutti
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gayan Weerakutti 2014-07-15 17:32:53 UTC
Steps to reproduce:
1. Create .odt Document
2. Insert -> Object -> Formula
3. Update formula content
4. File -> Export as PDF ..
5. Save document (.odt)
6. Reopen Document
4. Double click on formula.

Screenshot: 
http://cdn.imghack.se/images/a5f500f87099c5089356510d5f88d24d.png
Comment 1 tommy27 2014-07-16 03:58:35 UTC
would you please upload a test file as well?
did the formula corruption happen only after PDF export?
what if you save as .odt (step 5) and then export to .pdf (step 4) ?
Comment 2 Gayan Weerakutti 2014-07-16 08:07:44 UTC
Created attachment 102904 [details]
Test File
Comment 3 Gayan Weerakutti 2014-07-16 08:09:52 UTC
(In reply to comment #1)
> would you please upload a test file as well?
> did the formula corruption happen only after PDF export?
> what if you save as .odt (step 5) and then export to .pdf (step 4) ?

Please see the attached content. BTW this only happens with my old .odt files.
Comment 4 Gayan Weerakutti 2014-07-16 08:14:38 UTC
May be this is because some of my files are initially created as .rtf in Windows Wordpad and then open and saved in LibreWriter as .odt
Comment 5 tommy27 2014-07-16 18:22:57 UTC
reproducible with LibO 4.2.5.2 under Win7x64
status NEW. platform ALL
Comment 6 Matthew Francis 2015-01-17 01:56:19 UTC
I can't access the image linked to in comment 0.

If this issue still occurs in 4.3 or later, please attach a screenshot of the issue you are seeing directly to this bug.

It would also be useful to know the precise formula text used in the reproduction steps (step 2) and how exactly it is updated (step 3)

Setting -> NEEDINFO
Comment 7 QA Administrators 2015-07-18 17:36:11 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-07-18
Comment 8 QA Administrators 2015-09-04 03:01:30 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-09-03