Created attachment 130309 [details]
example to demonstrate the bug
This document has a first section in portrait (with PARA 1 and PARA 2), followed by a section break, then a one-page section in landscape (with some content in a frame FRAME 1), then another section break followed by section in portrait orientation (with PARA 3-PARA 5. There is a frame FRAME 2 linked to PARA 3. This document is attached as 'test1.odt'.
To show the bug, load test1.odt and attempt to cut PARA 3 and PARA 4 together from the last page and paste them immediately below PARA 2
When doing this, note that 'FRAME 1' disappears completely from view. And note that frame 'FRAME 1' is now duplicated, even though we previously cut it from the last page. ALSO note that there are now THREE section breaks in the document where the were previously only two. The document is now corrupted and cannot be restored with the use of the undo option.
If only PARA 4 is cut/pasted to the first page, there is no problem.
If FRAME 2 is re-anchored to PARA 4 and PARA 4 is cut/pasted to the first page, there is also no problem.
Hence the problem appears to arise as a result of cut/pasting from part-way through PARA 3, deliberately excluding the first few characters. So it is not a question of selecting/deselecting the first character after the section break.
This is a major bug causing corruption of documents.
Additionally, please not that PAGE 3 and the second section break are both rendered in the wrong place on the screen when zooming the view to show all three pages at once (zoom= 60% on my 1920x1200 monitor)
Build ID: 9a30cb2161506e003f14592d83075ab9d30516c1
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2;
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Please could the importance of this bug be increased? Bug leads to corruption of documents during normal use of LibreOffice.
Please update to CONFIRMED (as noted above by Xisco).
Also, I can confirm that the bug is also present in 18.104.22.168 on Ubuntu 15.04 64-bit.
I can confirm that this bug is still presented in 22.214.171.124.
Please update this bug to CONFIRMED??
I confirm this bug is still present in version 126.96.36.199.
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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
There is still a bug here in LO 188.8.131.52 on Ubuntu 18.04. However the behaviour does seem to have changed somewhat. But it's still completely not correct, all over the place. The implementation of frames and sections in Writer documents definitely needs some more careful testing.
Build ID: 1:6.2.6-0ubuntu0.18.04.1~lo1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: en-AU (en_AU.UTF-8); UI-Language: en-US
CTRL+V produces also improper result