Bug 72008 - Printed pages partially obscured by strange white area fills
Summary: Printed pages partially obscured by strange white area fills
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
4.1.3.2 release
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-25 22:04 UTC by Helge Blischke
Modified: 2015-06-08 14:27 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
screenshot showing the bug in the print dialogue (368.06 KB, image/tiff)
2013-11-25 22:04 UTC, Helge Blischke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Helge Blischke 2013-11-25 22:04:15 UTC
Created attachment 89789 [details]
screenshot showing the bug in the print dialogue

The graphic anchored on top of the first page of the document
Word2007RTFSpec9.rtf
is turned into rectangular white area fills spread over more than half
of the document's pages.
This occurs when printing as well as when displaying the preview (even in
the print dialogue).

This issue does not show up in version 4.0.6 on Mac OS X.

The bug can easily be reproduced by opening the mentined document
(downloaded from Microsoft's web site).

See the attached screenshot.
Comment 1 Joel Madero 2013-12-20 15:40:02 UTC
Not a critical bug - updating status

Normal: Can prevent high quality work

Critical bugs are almost only for bugs that affect a huge number of users, result in massive data loss and can cause crashes.
Comment 2 Buovjaga 2014-10-26 08:39:04 UTC
Downloaded file from http://download.microsoft.com/download/2/f/5/2f599e18-07ee-4ec5-a1e7-f4e6a9423592/Word2007RTFSpec9.doc
Could not reproduce. Can you test with latest stable?

Tested on Win 7 64-bit 4.3.2.2 and dev build Version: 4.4.0.0.alpha1+
Build ID: 0a82645c360158f9cc0fdabe2a52f1ff8f981bed
TinderBox: Win-x86@39, Branch:master, Time: 2014-10-24_06:59:23
Comment 3 QA Administrators 2015-05-06 14:14:25 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 4 QA Administrators 2015-06-08 14:27:10 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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

-- The LibreOffice QA Team 

This INVALID Message was generated on: 2015-05-06

Warm Regards,
QA Team