Steps to reproduce:
1. Open attachment 160662 [details] from bug 132944
2. Select all
-> LibreOffice hangs
Build ID: 94eb4f9b19b13f3548a232ec0a1f4b50bcb55d94
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
but not with x11
Regression introduced by:
author László Németh <firstname.lastname@example.org> 2019-07-25 17:52:20 +0200
committer László Németh <email@example.com> 2019-08-01 09:43:51 +0200
commit fa5eb82b398e29ae033f7b7c8c8195dfc10cf5b0 (patch)
parent 1aac73a1fb260e4c76a483a68f003913fdd2c4bb (diff)
tdf#118699 change tracking: don't number empty lines
Bisected with: bibisect-linux64-6.4
Adding Cc: to László Németh
Hi Caolán, I believe you should be able you reproduce this one on your end
@Xisco: I'll check it, I was able to reproduce it. Thanks, László
@Michael: it seems, this is special case of the regressions caused my incomplete fix for https://bugs.documentfoundation.org/show_bug.cgi?id=118699, which has been completed by you.
It seems, the problem is the document ending table. The first failing assert:
libreoffice/sw/source/core/text/redlnitr.cxx:94: std::unique_ptr<sw::MergedPara> sw::CheckParaRedlineMerge(SwTextFrame&, SwTextNode&, sw::FrameMode): Assertion `pNode != &rTextNode || &pStart->nNode.GetNode() == &rTextNode failed.
Dear Xisco Faulí,
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!
Issue fixed by
Closing as duplicated of bug 135061
*** This bug has been marked as a duplicate of bug 135061 ***