I have a document which starts with a one column, to move into a two columns and then again back to a one column. The document opens correctly in Word, but on LibreOffice the column break after the two columns layout was not recognized and the remaining part of the document went on the second page.
Hi Andrea.. Please attach sample document (after remove confidential data). Then change status of this bug to UNCONFIRMED
Created attachment 104080 [details] this is the document (CV) I was working on
Did you try to work in OpenDocument Format and export to OOXML when the document is finished (or, better, in pdf)? Best regards. JBF
No I didn't it yet. I was trying to test the compatibility of LibreOffice versus Mac, in an attempt to establish how proficient I will be once on Ubuntu.
Hi Andrea, in your document I can confirm that there is a page break sets with the style Converted1. You can view it by editing the page break and under the text flow tab. Set as New, change plateform to all (tested on 4.3.0.4 Ubuntu 14.04) - Sophie.
Hi Sophie, when you say "style converted" you refer to a document converted in OpenOffice format?
** 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.0.5 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 If 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-09-03
Still confirmed. Doesn't go to 2nd page in 3.5.0, though. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: b216cc1b8096eb60c27f67e8c27b7cd756c75e38 TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-11-12_00:06:20 Locale: fi-FI (fi_FI) 3.5.0
Migrating Whiteboard tags to Keywords: (bibisectRequest) [NinjaEdit]
Just FYI on this bibisect - there is a separate bug that comes up during the bibisect that might be related. A different page break appears. This bibisect focuses on the page break immediately after the double column. 5b4693bb72eca5e38e3f56d036bca425c9a21b37 is the first bad commit commit 5b4693bb72eca5e38e3f56d036bca425c9a21b37 Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com> Date: Sun Dec 9 11:49:31 2012 +0000 source-hash-e3633f60b349022994e291aa3d1a0c90c3403b2e commit e3633f60b349022994e291aa3d1a0c90c3403b2e Author: Stephan Bergmann <sbergman@redhat.com> AuthorDate: Wed May 16 09:32:51 2012 +0200 Commit: Stephan Bergmann <sbergman@redhat.com> CommitDate: Wed May 16 09:36:38 2012 +0200 fdo#46074 fdo#49948 Ignore corrupted items in Recent Documents ...following up on 4ccb4bda483eb548eb6efb5e2f1952f094522320 "fdo#46074 Ignore corrupted items in Recent Documents" with another problematic scenario found with fdo#49948. Change-Id: I3e7c803813f09c1f031defc2c18cfab6732b1621 :100644 100644 5aa1dfc68ecb9ac57316a995424b2d3683cb4774 aa42f04f09d97d387333244ba505d2fd3c3086c2 M autogen.log :100644 100644 72da0ea5e9ec1223cb456558a2e0254561faa98c 1829a020e51322ed60e655809575a93edd3b9032 M ccache.log :100644 100644 5ef3324ce1c257155c9e095fdeb7d912b2681ae1 795d8ec3e2d59c5f0a85099dac7224954a57c4f2 M commitmsg :100644 100644 8b14489bddefe04fcfaecb0be901837505c64b67 5e870f27775bef1e12288b413b09a4052c414870 M dev-install.log :100644 100644 68ac6a90c73f1f7c8776a70772a40ae1ce41e13d 78b57ac998248d89343563f89455faeeea3f57a1 M make.log :040000 040000 8b906c6863615fd1253b393b35b18a883201b310 e793bfa8b661936460e69be1537f15a7e99d3289 M opt # bad: [423a84c4f7068853974887d98442bc2a2d0cc91b] source-hash-c15927f20d4727c3b8de68497b6949e72f9e6e9e # good: [65fd30f5cb4cdd37995a33420ed8273c0a29bf00] source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932 git bisect start 'latest' 'oldest' # bad: [e02439a3d6297a1f5334fa558ddec5ef4212c574] source-hash-6b8393474974d2af7a2cb3c47b3d5c081b550bdb git bisect bad e02439a3d6297a1f5334fa558ddec5ef4212c574 # bad: [8f4aeaad2f65d656328a451154142bb82efa4327] source-hash-1885266f274575327cdeee9852945a3e91f32f15 git bisect bad 8f4aeaad2f65d656328a451154142bb82efa4327 # good: [369369915d3582924b3d01c9b01167268ed38f3b] source-hash-45295f3cdceb4c289553791071b5d7f4962d2ec4 git bisect good 369369915d3582924b3d01c9b01167268ed38f3b # bad: [6fce03a944bf50e90cd31e2d559fe8705ccc993e] source-hash-47e4a33a6405eb1b5186027f55bd9cb99b0c1fe7 git bisect bad 6fce03a944bf50e90cd31e2d559fe8705ccc993e # good: [8a39227e344637eb7154a10ac825d211e64d584c] source-hash-f5080ebb7022c9f5d7d7fdca4fe9d19f9bb8cabf git bisect good 8a39227e344637eb7154a10ac825d211e64d584c # bad: [e4c742a9e244bd7ebeabc50c90182df28ac3daaf] source-hash-c52ba433491afbca70aa1977a624c795bdd5b9ef git bisect bad e4c742a9e244bd7ebeabc50c90182df28ac3daaf # good: [96a055e15ee7171a28888973a3c3a7307dd9867f] source-hash-9ca02a663c3eee2698eb360dd5dc7afb1951e743 git bisect good 96a055e15ee7171a28888973a3c3a7307dd9867f # bad: [e87a0055deae2c9e25ae1d1a365cec8418b785ce] source-hash-67ff63988f3b8eef2cc2b5bdf917918b93c3f070 git bisect bad e87a0055deae2c9e25ae1d1a365cec8418b785ce # bad: [5b4693bb72eca5e38e3f56d036bca425c9a21b37] source-hash-e3633f60b349022994e291aa3d1a0c90c3403b2e git bisect bad 5b4693bb72eca5e38e3f56d036bca425c9a21b37 # good: [d101b9946a6a04e65e3923038503436c790b7e12] source-hash-18e6e7d929c2be209407ed2e56b8ec4d5e6c4900 git bisect good d101b9946a6a04e65e3923038503436c790b7e12 # first bad commit: [5b4693bb72eca5e38e3f56d036bca425c9a21b37] source-hash-e3633f60b349022994e291aa3d1a0c90c3403b2e
*** This bug has been marked as a duplicate of bug 64372 ***