Description: In file, dragging the second and third lines before the first results in the Redo assert Steps to Reproduce: 1. Open attached file 2. Drag 2. and 3. lines to first place Actual Results: It makes redo assert Expected Results: It should not make redo assert Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 5c138ac6a8334825ef171ac6291b66b277eb4288 CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: Skia/Vulkan; VCL: win Locale: hu-HU (hu_HU); UI: hu-HU Calc: CL
Created attachment 178052 [details] Example file from Writer
Please can you attach video? Do you mean 2. and 3. lines in first cell (A3 sd Lorem ipsum dolor sit amet...)?
(In reply to raal from comment #2) > Please can you attach video? Do you mean 2. and 3. lines in first cell (A3 > sd Lorem ipsum dolor sit amet...)? => NEEDINFO
Created attachment 178450 [details] Screencast about the assert crash during Redo
Sorry, missing steps to reproduce the assert crash during Redo: 2 ... by selecting the 2nd and 3rd table rows by clicking on the left border of the first row and dragging the selection to the 3d row. After that, it's possible to move the selected table rows before the first row by drag & drop them into the first cell of the first row. 3. Click on Undo 4. Click on Redo This likely a regression, but I'm not sure in it.
Created attachment 178528 [details] Screencast: different drag result (not a reproducer) I don't understand, if I try performing the same steps, the result of dragging is different for me, see the screencast. Note that an assertion failure requires a debug build to trigger it, and isn't bibisectable. And btw, I can reproduce an assert after the undo step, but it behaves slightly differently before that.
Dear NISZ LibreOffice Team, 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