Description: Sometimes my text goes all wonky; for example, I just found a page where there's no text in the left column, at all. This mostly happens with a longer document that has a two-column setup and images, and especially when there's a page break. Link to an example of the bug in the doc: https://ask.libreoffice.org/upfiles/15675415108757155.odt Steps to Reproduce: 1. Create a section with two (maybe more? Haven't tested) columns. 2. Write text. 3. Create a page break. 4. Keep writing text. 5. Save and come back. Actual Results: The text after the page break does not appear in the leftmost of the two columns, at all. Expected Results: The text should appear from left to right in the leftmost column. Reproducible: Sometimes User Profile Reset: Yes OpenGL enabled: Yes Additional Info: It is possible to temporarily fix the problem by removing the page break. NOTE: I tested whether the bug functioned with OpenGL off, but it still bugged. I've also tested with OpenGL off AND in Safe Mode, and it remains. NOTE: Graphics card is an AMD 15DD, and I didn't see it specifically in "Hardware," so I chose "Other" as a precaution.
Repro Inherited from OOo (4.1.1 has it) Version: 6.4.0.0.alpha0+ (x64) Build ID: 01837a85004a6f891a09c0a63ed7eff75d634827 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-09-01_00:07:05 Locale: es-ES (es_ES); UI-Language: en-US Calc: CL
@rpgcraftsman: you wrote steps to reproduce but I didn't repro with them. Did you? Please attach ODT if you did. As for ODT from the link, please write down the source ASK topic. If that ODT came from some MSO document or was converted, than this is another bug, probably a duplicate.
Thread: https://ask.libreoffice.org/en/question/207244/my-text-is-shifting-around-in-undesired-ways/
Created attachment 153897 [details] Sample 2-page 2-column before NOK.odt Mike wrote there: "Removing then re-applying the break initially keeps the "DODGE [COMBAT]" where it was without the break (i.e., at right column of p.3), then removing the last empty paragraph before it moves it to where it should be (left column of p.4)... erratic behavior." Page break comes from the paragraph style. I attach a somewhat minimized sample with 2-pages that still has wrong behavior of "DODGE [COMBAT]" starting on the 2nd page in right instead of left column.
Created attachment 153898 [details] Sample 2-page 1-column before OK.odt We should try to further minimize the sample in order to see when it gets OK. Here I changed previous section 2 columns to normal 1 column text. And it's OK.
I mean, I understand that, but I want to keep the layout I had...it's what I've been using, and I'm trying to remain at least somewhat consistent, so that people can actually read my document when I PDF it. I'm not trying to be a dick, but I think it'd be more useful to people to fix the bug, rather than to just say "deal with it."
@rpgcraftsman@protonmail.com: thanks for reporting this! Please note that the bug tracker is for helping developers to handle issues. As such, the first stage of handling an issue is, naturally, reporting - thank you again. Then, other people jump in and do lots of other work: they try to confirm (and your bug is *confirmed* (comment 1) - which means that it's *already agreed to show a defect*, and thus it is not about "deal with it"); they try to minimize the sample to find a specific minimal set of elements showing the problem (comment 4 and comment 5); sometimes a decision is needed if this is a bug or an intended behavior (not in this case), etc. The team does brilliant job; and sometimes, when all that hard work is done, the result is that a developer would see the problem immediately when looking into the results (instead of spending weeks). Sometimes you may also read some advises how to workaround (because, well, everyone here understands that, besides reporting something, OP needs their work done, so suggesting a workaround for now, before the bug gets an interested developer's attention, is better than nothing). Please don't read here what wasn't written ;-) and thank you again for reporting.
Dear rpgcraftsman, 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://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
I reproduce with attachment 153897 [details] but I cannot create from scratch, steps needed.