Bug 66047 - Making a formula element in parentheses bold makes the formula object huge and invisible
Summary: Making a formula element in parentheses bold makes the formula object huge an...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Formula Editor (show other bugs)
Version:
(earliest affected)
4.0.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-22 14:43 UTC by Shimi Chen
Modified: 2015-05-02 20:06 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Example of the bug(odt) (10.15 KB, application/vnd.oasis.opendocument.text)
2013-06-22 14:43 UTC, Shimi Chen
Details
how it looks like when importing attached odt (160.10 KB, image/png)
2013-06-24 13:28 UTC, Jorendc
Details
ODTs with formula created under v3304, v3462, v3572, v3672, v4062, and v4132. (49.15 KB, application/zip)
2013-12-09 01:32 UTC, Owen Genat (retired)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Shimi Chen 2013-06-22 14:43:49 UTC
Created attachment 81217 [details]
Example of the bug(odt)

To reproduce make a formula object in Writer with the following content:
bold{(1)}
This will result in an empty and seemingly infinite box.
Workaround: remove the parentheses or the bold statement.
Tested on Ubuntu 13.04(MATE desktop) using LibreOffice 4.0.4.2 installed from:
https://launchpad.net/~libreoffice/+archive/ppa

A simple example .odt is attached.
Comment 1 Regina Henschel 2013-06-22 21:40:29 UTC
I cannot reproduce the problem. I use 4.1.0.0.beta2 on Windows 7. I have tried it with "experimental features" enabled and without, and with "Math baseline alignment" and without.
Comment 2 Jorendc 2013-06-24 13:28:30 UTC
I can confirm this behavior using Mac OSX 10.8.3 with LibreOffice 4.1.0.1 RC when importing your attached ODT file.
When I double click and unselect it again, the formula box is shown normally.

I can NOT confirm this behavior from scratch.
I think this bug needs some more investigation.

Kind regards,
Joren
Comment 3 Jorendc 2013-06-24 13:28:59 UTC
Created attachment 81338 [details]
how it looks like when importing attached odt
Comment 4 ⁨خالد حسني⁩ 2013-06-25 12:04:57 UTC
Same here as Jorendc, put with master on Linux.
Comment 5 José Guilherme Vanz 2013-11-02 21:18:01 UTC
I can reproduce the bug on master build.
Comment 6 Owen Genat (retired) 2013-12-09 01:32:19 UTC
Created attachment 90483 [details]
ODTs with formula created under v3304, v3462, v3572, v3672, v4062, and v4132.

There appears to have been a problem with the ViewAreaWidth name value for the config-item element in Object\ 1/styles.xml. I created new ODTs (refer attached) containing a formula with "bold{(1)}" under Ubuntu 10.04 x86_64 using:

- v3.3.0.4 OOO330m19 Build: 6
- v3.4.6.2 OOO340m1 Build: 602
- v3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b
- v3.6.7.2 Build ID: e183d5b
- v4.0.6.2 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24
- v4.1.3.2 Build ID: 70feb7d99726f064edab4605a8ab840c50ec57a

Some of these versions do not appear to write out the name value:

v3.3.0.4: <config:config-item config:name="ViewAreaWidth" config:type="long">787</config:config-item>
v3.4.6.2: <config:config-item config:name="ViewAreaWidth" config:type="long">786</config:config-item>
v3.5.7.2: <config:config-item config:name="ViewAreaWidth" config:type="long">786</config:config-item>
v3.6.7.2: <config:config-item config:name="" config:type="long">786</config:config-item>
v4.0.6.2: <config:config-item config:name="" config:type="long">786</config:config-item>
v4.1.3.2: <config:config-item config:name="ViewAreaWidth" config:type="long">786</config:config-item>

All the attached test ODTs are rendered correctly when re-opened by the same creating version or v4.1.3.2. By comparison, attachment 81217 [details] (created in v4.0.2.2) contains:

<config:config-item config:name="" config:type="long">29593752</config:config-item>

Perhaps there was a regression in handling this value in the v3.6/4.0 series?
Comment 7 Owen Genat (retired) 2013-12-09 07:36:57 UTC
(In reply to comment #6)
> Object\ 1/styles.xml. 

Should read "Object\ 1/settings.xml."
Comment 8 Jean-Baptiste Faure 2014-03-01 14:45:18 UTC
Seems to be linked to bug 75408 and bug 48846. Indeed if I open the bugdoc with the master in which I reverted the fix for bug 48846, theh I can see the formula with the correct size.
So it seems that there is some incompatibility in the ability to make formula resizable in Writer.
Comment 9 Joel Madero 2014-03-02 17:05:14 UTC
After reading comments I'm a bit confused as to what state this bug is in - UNCONFIRMED because it needs additional research, NEW because it's now been confirmed several times or a dupe of the other bug?
Comment 10 Regina Henschel 2014-03-02 17:53:08 UTC
Here LO4.3 even crashes on the provides documents. So yes there is a problem with this documents. When I newly write the formula in LO4.3, then there is no problem in LO4.3.

Version: 4.3.0.0.alpha0+
Build ID: f839b5dd16c05c0eda21345ec36ec0cb024eb732
TinderBox: Win-x86@47-TDF, Branch:MASTER, Time: 2014-02-23_09:54:38
Comment 11 Shimi Chen 2014-03-02 18:03:26 UTC
I also cannot reproduce this issue with a new document.
Currently running 4.1.5.3 Arch Linux build-1
There are three options as I see it:
-This bug was fixed in one of the versions between 4.0.4.2 and 4.1.5.3.
-It was caused by a bug in the ubuntu ppa packaging.
-Something unknowingly changed in my LO configuration that resolved the issue.
Comment 12 Regina Henschel 2014-03-02 18:32:01 UTC
For me the LO4.3 from 2014-03-01 still crashes on the attached documents. I work on Windows7.
Comment 13 Joel Madero 2014-03-02 21:15:34 UTC
Was the original report about a crash though? that seems like a separate issue
Comment 14 Regina Henschel 2014-03-02 21:44:12 UTC
@Joel: You might be right. I have created bug 75686 for the crash now. But I think, that it is very likely, that all the formula problems have the same reason.
Comment 15 Owen Genat (retired) 2014-03-09 00:50:58 UTC
(In reply to comment #6)
> Some of these versions do not appear to write out the name value:
> ...
> v3.6.7.2: <config:config-item config:name=""
> config:type="long">786</config:config-item>
> v4.0.6.2: <config:config-item config:name=""
> config:type="long">786</config:config-item>
> ...
> By comparison, attachment 81217 [details] (created in v4.0.2.2) contains:
> 
> <config:config-item config:name=""
> config:type="long">29593752</config:config-item>
> 
> Perhaps there was a regression in handling this value in the v3.6/4.0 series?

Just for info, this was caused by commit: 90a91ed3e9ca1684655268dc52754ca569febc36 (08-Mar-2012)
... and fixed in commit: a44bff569bcef931e1ca6a7b2b8d0bcd279725bc (26-Apr-2013)
Comment 16 Joel Madero 2015-05-02 15:44:32 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

   Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.2 or later)
   https://www.libreoffice.org/download/

   If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 
 If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

   Update the version field
   Reply via email (please reply directly on the bug tracker)
   Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Comment 17 Shimi Chen 2015-05-02 20:06:12 UTC
Changed to WORKSFORSOME as per comments 10-11.