Helmut Leininger has found this bug. Here are the steps: 1. Create empty document 2. Make page orientation album with 2 columns and margins 1.0, 1.0, 1.0, 1.0 cm (up, down, left, right) 3. Create table 2*2 and move it to the bottom of the column using enters. 4. Copy first column with ctrl+c 5. Paste to the second column. 6. Save as doc (test.doc) 7. Open the file. 8. Mark first collumn on the page and copy it with Ctrl+C 9. Mark the second column on the page and press ctrl+v 10. Save document and close it (test2.doc) 11. Open it.
Created attachment 41054 [details] Document after first "Save as..."
Created attachment 41055 [details] Document after second "Save as..."
After first column in page 1 there is a wrong section break. Because of that the original column 2 in page 1 is empty
Hello, druido77, thanks for reporting. I am not sure if I understand the steps quite clear. (In reply to comment #0) > Helmut Leininger has found this bug. Here are the steps: > > 1. Create empty document > 2. Make page orientation album with 2 columns and margins 1.0, 1.0, 1.0, 1.0 > cm (up, down, left, right) > 3. Create table 2*2 and move it to the bottom of the column using enters. > 4. Copy first column with ctrl+c How did you select the first column. i.e, something like put the cursor on the top the column, and Shift+click the end of the column? > 5. Paste to the second column. > 6. Save as doc (test.doc) > 7. Open the file. > 8. Mark first collumn on the page and copy it with Ctrl+C > 9. Mark the second column on the page and press ctrl+v > 10. Save document and close it (test2.doc) > 11. Open it. I tried to do these steps in 3.3 rc1 and the result is a bit different (no data missing here): left column in the 1st page: has table right column in the 1st page: empty left column in the 2nd page: has table right column in the 2nd page: has table Please see my attachment test3.doc :)
Created attachment 41056 [details] test3.doc
(In reply to comment #5) > Created an attachment (id=41056) [details] > test3.doc And if I understand it correctly, the expected result should be: left column in the 1st page: has table right column in the 1st page: has table left column in the 2nd page: has table right column in the 2nd page: empty Is that what you concerned?
I select the column with mouse movements and do copy/paste operation by pressing ctrl+c and ctrl+v. You can see a demo video at http://www.stefanofraccaro.org/video_32344.zip I have followed all steps... I save and reopen ever the same file, but before and after the second "save as..." the document is different.
(In reply to comment #6) > > Created an attachment (id=41056) [details] [details] > > test3.doc > The expected result is a bit different but, also in your case, there is a section break in column 1 of page 1. Why? You have never inserted a page break in this document... but the page break exists
Thanks for clarification, confirmed with 3.3 rc1. The topic and C#4 is actually the same issue.
I can reproduce it too... Lubos, maybe one for you?
Is there any chance that this bug can be fixed? Actualy there is the same issue, when drag and dropping portion of text from one collumn to another.
reproducible with LO 4.0.2.2 (Win7 Home, 64bit)
This bug has not been touched by its Assignee for a long time. To make it clearer which bugs should be fixed by someone else please take following action: - If you are the Assignee, and you are actively working on the bug, please give it an update. - If you are the Assignee, and you do not plan to work on it in the near future, please reassign it to the default assignee.
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
I tested again this bug with LibreOffice 5.0.4 x64 on Windows 7. The bug still persist.
Please test again with master https://dev-builds.libreoffice.org/daily/master/. And attach ODT document saved after step 5.
I tested it in: Version: 6.1.0.3 Build ID: 6.1.0-2 CPU threads: 12; OS: Linux 4.18; UI render: default; VCL: gtk2; Locale: de-DE (en_US.UTF-8); Calc: group threaded After saving the document, things are still normal (Column 1 and 2 the same on the first page). After closing and reopening, a page break appears pushing the content of column 2 on page one to column 1 on page 2.
Created attachment 145440 [details] test 2 in LO 6.1
Dear Stefano Fraccaro, 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! Warm Regards, QA Team MassPing-UntouchedBug
Because you are copying the very first paragraph from a .doc* format and pasting it and getting a page break, that sounds like another version of bug 118711 *** This bug has been marked as a duplicate of bug 118711 ***