It's possible to get formulas created in Math component (Formula Editor), being corrupted right at the start: you get corrupted formula at the moment it is inserted into document. Such corrupted formula shows as an 'Object Number ...' and does not expose correct object methods (https://bugs.freedesktop.org/attachment.cgi?id=81029 is what happens when script trying for those methods finds such formula). Here's a 100% reproducible recip: Start from blank, put one "over-64K-codepoint" glyph into it, make formula from it (I did this with 'Neo Euler-like bold B' glyph U+10FE88 from Asana Math in my sample). In formula preview the glyph comes out as a 'have no such glyph' square (the default font in formulas here is Charter). Now you may save it 'as is', or you may correct the formula source (put something 100% acceptabel, like ASCII letter), then save. Either way you get a document with corrupted formula (showing as 'Object #something'). I'm attaching two sample docs, one saved as is (https://bugs.freedesktop.org/attachment.cgi?id=81582), another corrected (changed source to 'latin B'), then saved (https://bugs.freedesktop.org/attachment.cgi?id=81583).
Yury, You should not mark your own bug reports as "NEW"; instead, it must be created as UNCONFIRMED, and someone should confirm it to mark so. Even the developers themselves here don't mark bugs they create and take this way; see Bug 66279 for such example. One drawback of your wrong setting is that when triagers will look at the title of your bug, they may suspect that someone had already triaged this bug, confirmed it and informed developers. Thus it may take longer until it actually gets attention. To clarify: I'm not a trianger; I just came across it when looked for a duplicates of a bug I submit myself.
Well, settings of such high importance and of such unobvious usage at that, should be auto-initialised on ticket creation. Thank you, and I'll keep your advice, but the requirement to set new ticket as 'UNCONFIRMED' definitely isn't obvious.
Yury: thanks for your report. I haven't tried to reproduce your bug but while I was reading the code, I noticed that the Math parser seems to handle only BMP characters. So I suspect issues with non-BMP characters are likely to happen.
** 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.1 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-04-01
Not fixed. In 4.4.2.2, using that same one glyph U+10FE88 from Asana Math (insert-special character, copy glyph, paste into formula source), I get TWO squares in immediate formula render (formula source still open). After save-close-reopen, I get "General OLE Error" trying to open that formula in formula editor. Going to attach that proofdoc.
Created attachment 114528 [details] doc exposing the issue on 4.4.2.2 (needs open-source Asana Math font installed)
(In reply to Yury from comment #5) > Not fixed. In 4.4.2.2, using that same one glyph U+10FE88 from Asana Math > (insert-special character, copy glyph, paste into formula source), I get TWO > squares in immediate formula render (formula source still open). > > After save-close-reopen, I get "General OLE Error" trying to open that > formula in formula editor. > > Going to attach that proofdoc. Reproducing from scratch with the Asana Math font on Windows, I do get the general ole error after reloading and trying to open the formula. I don't see two squares, however (inserted one B (U+10FE88) and nothing else). Instead, the formula object is widened to the right, beyond the page margins and it contains nothing. On Linux 3.3.0 I got one square + general error. Win 7 Pro 64-bit, Version: 4.4.2.2 Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6 Locale: fi_FI Ubuntu 14.10 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
** 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 (5.1.6 or 5.2.3 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
still repro in 6.1.0.1 on Windows 7
Dear Yury, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Yury, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug