Description: Page orientation lost on redo Steps to Reproduce: 1. Open attachment 164872 [details] (bug 145374 and bug 136284) 2. Place cursor above Table 3.1a on page 2 3. Select content until bottom (say shift page down) 4. CTRL+N 5. CTRL+V and scroll to top (page orientation OK) 6. CTRL+Z 7. CTRL+Y Page orientation lost Actual Results: Page orientation not restored by redo Expected Results: Should be the case Reproducible: Always User Profile Reset: No Additional Info: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 25276df12abd9d002f7f899900434617b256f745 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded
Repro Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ef6083200a4f28e43198c7a0878da6f4b880725f CPU threads: 8; OS: Linux 6.7; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded
By the way, for me the orientation is already lost with undo. And between step 3 and 4 should be Ctrl+C. With a debug build it crashes at undo with soffice.bin: /home/user/libreoffice/sw/source/core/txtnode/ndtxt.cxx:5494: void SwTextNode::TriggerNodeUpdate(const sw::LegacyModifyHint &): Assertion `dynamic_cast<SwTextFormatColl const*>(static_cast<const SwFormatChg*>(pOldValue)->pChangedFormat)' failed.
(In reply to Buovjaga from comment #2) > By the way, for me the orientation is already lost with undo. And between > step 3 and 4 should be Ctrl+C. > > With a debug build it crashes at undo with > > soffice.bin: /home/user/libreoffice/sw/source/core/txtnode/ndtxt.cxx:5494: > void SwTextNode::TriggerNodeUpdate(const sw::LegacyModifyHint &): Assertion > `dynamic_cast<SwTextFormatColl const*>(static_cast<const > SwFormatChg*>(pOldValue)->pChangedFormat)' failed. Reported as bug 159503
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