Bug 63424 - PRINTING: Bad print of a document correctly displayed both in editing and in print preview
Summary: PRINTING: Bad print of a document correctly displayed both in editing and in ...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.6.2 release
Hardware: x86-64 (AMD64) Windows (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard: BSA NoRepro:4.2.0.1:OSX
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-11 13:24 UTC by dduck
Modified: 2014-08-06 08:44 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
7zip file containing DOC1.odt, DOCPRINTED.pdf and DOCPRINTEDOK.pdf (191.48 KB, application/x-7z-compressed)
2013-04-11 13:24 UTC, dduck
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dduck 2013-04-11 13:24:04 UTC
Created attachment 77809 [details]
7zip file containing DOC1.odt, DOCPRINTED.pdf and DOCPRINTEDOK.pdf

Problem description: 
The attached document DOC1 is correctly seen while edited and in print preview. But if printed the result is wrong, as you can see in the attached DOC1PRINTED. However the DOC1 is correctly exportable in pdf format and consequentely printable.

Steps to reproduce:
1. Open DOC1.odt
2. Look at the print preview: it seems to be ok

Current behavior:
Print DOC1: the result is in DOC1PRINTED.pdf. The result is the same on HP LJ1160 with HPLJ II driver, OKI B411 with its driver and HP LJ P3005 with its own driver PCL6

Expected behavior:
Look at DOC1PRINTEDOK.pdf. This file was created with LO4.0.2.2

              
Operating System: Windows XP
Version: 4.0.2.2 release
Comment 1 dduck 2013-04-11 13:33:55 UTC
This bug seems to be independent from the platform: I have the same described behavior on both a VmWare WinXP Pro and a Win7 64bit PRO. I've also tried the same document with LO 3.5.7.2 on Ubuntu 12.04 but, there, the behavior is correct.

Regards
Comment 2 kieran 2013-04-11 16:53:07 UTC
I have the same issue with my .doc files, the results look the same, even with the heavy border shifted down to the lower right.  
docx print fine however.
Comment 3 Javier 2013-04-29 08:42:52 UTC
The same with version 4.0.2.2 with oki (I think that the problem is in hp pcl drivers).
Comment 4 dduck 2013-04-29 09:54:37 UTC
@Javier.
Why you think the problem is in the HP PCL drivers? I tested right now the involved document on a Kyocera Task Alfa 250 with its own KX Driver, noting the same buggy result.
Regards
Comment 5 Joel Madero 2013-12-16 21:07:02 UTC
Comment on attachment 77809 [details]
7zip file containing DOC1.odt, DOCPRINTED.pdf and DOCPRINTEDOK.pdf

Update to mime type
Comment 6 retired 2014-01-03 13:09:05 UTC
NoRepro:4.2.0.1:OSX

Is this bug still valid / reproducible with the latest pre-release 4.2.0.1: http://www.libreoffice.org/download/pre-releases/

Should this be still reproducible for you with the latest LO release please set this bug back to UNCONFIRMED. Should this issue be solved set it to WORKSFORME.

Setting to NEEDINFO until more detail is provided.
Comment 7 QA Administrators 2014-08-04 16:17:42 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/FDO/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 8 dduck 2014-08-06 08:44:29 UTC
I just tried with:
- LO 4.2.4.2 on UBUNTU 14.04
- LO 4.2.1.1 on UBUNTU 12.04
- LO 4.2.0.4 on WinXP SP3

The bug is fixed

Regards