Bug 49174

Summary: fuzzy output on paper, but clear output printing after exported to PDF
Product: LibreOffice Reporter: Nelson <jusfixit>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: jmadero.dev
Priority: medium    
Version: 3.5.2 release   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: photo of printed output from Lib0 .odt file
photo of printed output from Evince .pdf created by LibO

Description Nelson 2012-04-26 08:26:57 UTC
Created attachment 60616 [details]
photo of printed output from Lib0 .odt file

When LibreOffice is used to print output onto paper. the result is fuzzy.  Normal text appears similar to bolded text, except it is disturbingly rough along the edges.  See the first attached image for an example (scale on left is mm / cm).

  I had thought this problem must arise from the printer driver, but I have observed that on the same computer, using the same printer driver, etc. that clean and sharp output can be obtained.  In LibreOffice while viewing the same text file with no change in font or any other formatting, select "File", "Export as PDF ...".  Use a PDF viewer such as Evince to open the resulting file, and render the same file onto paper using the same print driver, printer, etc.  See the second attached image for an example of the fine clear sharp output one would expect to always see.  

  The magic is not in the conversion to PDF format, for if one uses LibreOffice Draw to view and print the PDF, the result is just as crudely fuzzy as when Writer printed the original .odt file. 

  This problem was first observed on earlier releases such as: 
  LibreOffice 3.3.4
and has been reproduced with:
  LibreOffice 3.5.2.2 
  Build ID: 281b639-6baa1d3-ef66a77-d866f25-f36d45

  What can I do to assist LibO to produce respectable-quality output on paper directly, without having to detour through a file format conversion and use of another application?
Comment 1 Nelson 2012-04-26 08:30:22 UTC
Created attachment 60617 [details]
photo of printed output from Evince .pdf created by LibO
Comment 2 Joel Madero 2012-09-11 20:27:00 UTC
Can you give info on your printer? I've never had this problem using my HP Photosmart 1115. Also, just to verify is this still a bug with latest stable (3.6.1.2)? Marking as NEEDINFO. Once you provide the info please mark as UNCONFIRMED again and we'll try to track down the problem.
Comment 3 QA Administrators 2013-05-29 14:00:24 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 4 QA Administrators 2013-07-08 21:23:00 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 FDO