LO 5152 Steps : 1) open LO 2) File -> New -> Formula 3) In the editor field, insert a character with code above U+10000 (for example: '𝑛') 4) click in the middle of the character 5) press the space bar 6) text is now broken.
Repro. Arch Linux 64-bit, KDE Plasma 5 Version: 5.3.0.0.alpha0+ Build ID: ff2a399b61f34f7920e594e8cbb6c19045b24956 CPU Threads: 8; OS Version: Linux 4.7; UI Render: default; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on October 7th 2016 Arch Linux 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 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 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: 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 bug.reporter.21, 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 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: 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
On pc Debian x86-64 with master sources updated today, I got a crash. There's indeed a pb when dealing with surrogate. See part of bt when typing space after having clicking on middle of 𝑛 character: #0 SmParser::Parse(rtl::OUString const&) (this=0x3205db8, rBuffer="\xd835 \xdc5b") at starmath/source/parse.cxx:2381 #1 0x00007fffdc3981e3 in SmDocShell::Parse() (this=0x3205c20) at starmath/source/document.cxx:222 #2 0x00007fffdc397e7c in SmDocShell::SetText(rtl::OUString const&) (this=0x3205c20, rBuffer="\xd835 \xdc5b\n") at starmath/source/document.cxx:145 #3 0x00007fffdc3973c8 in SmDocShell::Execute(SfxRequest&) (this=0x3205c20, rReq=...) at starmath/source/document.cxx:1034 There shouldn't be an extra space here: "\xd835 \xdc5b" The crash is triggered by https://cgit.freedesktop.org/libreoffice/core/commit/?id=11b57129b53e1e2d71a5f969e2417226b4e2ddd9 but it just makes the bug worse, it didn't create it. I don't understand how come typing space may indeed insert a space between a pair of surrogates in rBuffer.
In SmTextForwarder::GetText, pEditEngine->GetText( rSel ) has already the pb. https://opengrok.libreoffice.org/xref/core/starmath/source/accessibility.cxx?r=9ad252b2#885
I gave a try with https://gerrit.libreoffice.org/c/core/+/93684
Julien Nabet committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/23efced60cb7e08bf17b10e3e1ea5802e68a0cc6 tdf#102625: fix Formula editor breaks surrogate pairs It will be available in 7.0.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Backport for 6.4 waiting for review here: https://gerrit.libreoffice.org/c/core/+/93544
Verified, thanks! Arch Linux 64-bit Version: 7.0.0.0.alpha1+ Build ID: bd8015b13636607805fcf6a25e353597db868696 CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: kf5; Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 8 May 2020
Julien Nabet committed a patch related to this issue. It has been pushed to "libreoffice-6-4": https://git.libreoffice.org/core/commit/f7661f9da338daedc0a215bab76f4b0b42538913 tdf#102625: fix Formula editor breaks surrogate pairs It will be available in 6.4.5. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.