Description: !!br0ken!! error appears for fields Steps to Reproduce: 1. open the attached file 2. CTRL+A 3. CTRL+C 4. Place cursor next to the current field 5. CTRL+V 3x 6. CTRL+Z 3x 7. Paste -> !!br0ken!! Actual Results: !!br0ken!! Expected Results: No !!br0ken!! Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: <buildversion> CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: ru-RU (nl_NL); UI: en-US Calc: CL No clue where this exactly started, undo didn't work properly for a long long time
no attached file
1. Open attachment 163909 [details] 2. CTRL+A 3. CTRL+C 4. Place cursor next to the current field 5. CTRL+V 3x 6. CTRL+Z 3x 7. Paste -> !!br0ken!!
Reproduced in Version: 7.1.0.0.alpha0+ Build ID: 58937aa4a50ecd681382f03331340da4c843b01e CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Not reproducible in Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Created attachment 167070 [details] gdbtrace.log There seems to be a crash. Console output: soffice.bin: /home/suokunlong/build/lo/master/sw/source/core/txtnode/atrfld.cxx:682：void SwTextInputField::UpdateTextNodeContent(const rtl::OUString&): Asset ‘IsFieldInDoc() && "<SwTextInputField::UpdateTextNodeContent(..)> - misusage as Input Field is not in document content."’ failed. gdb backtrace attached.
The bug already exist at least in: 2019-11-13 16:51:24 +0100 9bc848cf0d301aa57eabcffa101a1cf87bad6470 Have not tested older versions. If bibisect is really needed, then need to use some old bibisect repos.
Dear Telesto, 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
Reproducable in LO 7.6 Dev under Windows 10(x64). Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1c638b7ac46d8077994c8483e6becc4a33efd12b CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: threaded