Created attachment 181003 [details] GDB trace of assertion Running a debug build: 1. Open Writer and make sure Tools - AutoCorrect - AutoCorrect Options - Options - Apply border is activated 2. In the first paragraph, type an autocorrect string for separator line, for example --- or ___ and hit Enter soffice.bin: /home/user/libreoffice/sw/source/core/edit/autofmt.cxx:1274: void SwAutoFormat::DelEmptyLine(bool): Assertion `!m_aDelPam.HasMark()' failed. Note: this only happens when done in the first paragraph.
Confirmed with a debug build of LO 7.5.0.0.alpha0+ (415dc3bb1c03dbdbc3cbca274bc435ac7557ba2d) / Ubuntu.
Reproduced with the latest LO 7.5 dev master: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1f9b2a7057a519e0ea750875ac439129f1d3df87 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Just for info: Assertion added with 9b34dc20b6946698ae6ce2d5d859885bfb444633 tdf#137245 sw: fix AutoFormat SetBorder deleting flys
Dear Buovjaga, 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