Bug 117450 - Repagination on FileOpen in Writer makes drawings disappear.
Summary: Repagination on FileOpen in Writer makes drawings disappear.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.3.2 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-06 01:42 UTC by Darv Dombach
Modified: 2018-12-03 13:20 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Darv Dombach 2018-05-06 01:42:14 UTC
Description:
Drawings that are anchored to a page near the end of a chapter, in a file where chapters are set to begin on a right-hand page, will disappear immediately after the file is opened, as if the image was deleted.

Steps to Reproduce:
1. Create a book-length file with drawings near the chapter ends. (Mine is about 160 pages.)
2. Set the chapters to start on a right hand page. (This automatically generates blank pages between chapters if necessary.)
3. Anchor the drawings to "Page." (In my case, I have a couple drawings that take up the whole page, so that alternative types of anchors do not work.)

Actual Results:  
When I open the file, the drawings every so briefly display on the file, and disappear while the file is being paginated.

Expected Results:
The drawings should remain the the place where they were positioned.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
As a work-around, I have attempted to select and cut the drawing while it is still visible before the pagination is complete. This tends to crash LibreOffice, but it worked well in the NeoOffice derivative, which seems to have a more pedantic repagination process. Unfortunately, that work-around can only be used for one drawing.

Version: 6.0.3.2
Build ID: 8f48d515416608e3a835360314dac7e47fd0b821
CPU threads: 4; OS: Mac OS X 10.13.4; UI render: default; 
Locale: en-US (en_US.UTF-8); Calc: group


User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:59.0) Gecko/20100101 Firefox/59.0
Comment 1 Alex Thurgood 2018-05-07 07:02:28 UTC
Without a test file, this is going to be difficult to reproduce.

Creating a 160 page book including images in the general manner you describe in point 1 is too vague and time consuming. Additionally, we have no way of knowing:

- what, if any other style elements or formatting you have assigned that might impact pagination;
- what size and file type of images you are using, how many images per page, etc, etc - there are simply too many variables.

You mention that you have 2 images that take up a whole page, does changing the size/properties of these images, or removing them completely change the behaviour?



Setting to NEEDINFO pending test file, and/or detailed steps/files to be able to attempt to reproduce.
Comment 2 QA Administrators 2018-11-05 16:07:45 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2018-12-03 13:20:14 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20181203