Download it now!
Bug 116753 - When saving a Writer file as RTF, page break is lost
Summary: When saving a Writer file as RTF, page break is lost
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.5.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, regression
: 116754 (view as bug list)
Depends on:
Blocks: RTF Writer-Page-Break
  Show dependency treegraph
 
Reported: 2018-04-02 14:01 UTC by Bernard Moreton
Modified: 2019-07-12 10:05 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample RTF file (5.08 KB, application/rtf)
2018-04-02 14:03 UTC, Bernard Moreton
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernard Moreton 2018-04-02 14:01:26 UTC
Description:
The sample uploaded is an RTF file, whch opens correctly.  If saved As RTF (I used a new filename) and then re-opened, the page break is seen to be lost.

Steps to Reproduce:
1. Open sample RTF document
2. Save As RTF
3. Open the saved document

Actual Results:  
Page break lost (and header text on p.2 mistreated as a footnote, se separate issue)

Expected Results:
Page break should be retained


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:


User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/538.1 (KHTML, like Gecko) QupZilla/1.8.9 Safari/538.1
Comment 1 Bernard Moreton 2018-04-02 14:03:35 UTC
Created attachment 141028 [details]
Sample RTF file
Comment 2 Timur 2018-04-02 14:49:40 UTC
Repro in 6.1+ and 3.6.5. Looks like regression from LO 3.6.
Comment 3 Bernard Moreton 2018-04-02 15:32:20 UTC
This report came from an observation against bug 92013
Comment 4 Dieter Praas 2018-04-13 11:20:40 UTC Comment hidden (obsolete)
Comment 5 Buovjaga 2018-04-13 11:23:42 UTC
Yes, not yet seen in LibreOffice 3.5.0rc3 so should be bibisectable.
Comment 6 Buovjaga 2018-04-13 11:29:13 UTC
(In reply to Dieter Praas from comment #4)
> (In reply to Timur from comment #2)
> > Repro in 6.1+ and 3.6.5. Looks like regression from LO 3.6.
> 
> Similar or same bug was fixed in 4.3 (see bug 80167). So perhaps a later
> regression.

But that regression date is from Thu Feb 6 13:58:03 2014 +0530

3.6.5 was in 2013: https://wiki.documentfoundation.org/ReleasePlan/3.6#3.6.5_release
Comment 7 Aron Budea 2018-04-13 17:34:25 UTC
Bibisected to the following range using bibisect-43all:
https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=3d4288c1c0b593421c7f6619c88584bdb7c53337..4026e1824de8ff9b5d006ae6eba491f91bc4e599

The following commit seems to be related at first sight:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=b836bf389d1150c9cafbb0aefa641af2316e536c
author		Miklos Vajna <vmiklos@suse.cz>	2012-11-30 15:33:52 +0100
committer	Miklos Vajna <vmiklos@suse.cz>	2012-11-30 17:25:15 +0100

fdo#57708 fix fake page break problem during RTF import
The core of this change is: so far the continous section break at the
end of the document was sent as a normal section break. This was
introduced in commit 892d33c8d5033b4f8f7889bf91d257f55adf0e1f, probably
as a workaround (sadly it's not documented and I no longer remember).
Don't do this, since it causes additional page breaks during import.
Instead, fix properly whatever was broken after getting rid of this
workaround.
Comment 8 QA Administrators 2019-07-12 02:52:21 UTC Comment hidden (obsolete)
Comment 9 Bernard Moreton 2019-07-12 09:30:26 UTC
This is probably in essence the same problem as in
[Bug 116754] When saving a Writer document As RTF header text from  p.2 appears in a footnote on p.1"

I reported that as still a problem a few days ago, and the test then showed that this bug (116753) is also still a problem.

Version: 6.2.4.2
Build ID: 1:6.2.4-0ubuntu0.18.04.1~lo1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
Calc: threaded
Comment 10 Dieter Praas 2019-07-12 10:05:17 UTC
*** Bug 116754 has been marked as a duplicate of this bug. ***