Bug 129002 - Printing with the newest version of LIBRE Version: (x64) now takes a long wait times to process file after print command.
Summary: Printing with the newest version of LIBRE Version: (x64) now takes a ...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
(earliest affected) release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
Keywords: possibleRegression
Depends on:
Blocks: Print
  Show dependency treegraph
Reported: 2019-11-25 01:53 UTC by Ronald Novak
Modified: 2020-06-26 03:41 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Ronald Novak 2019-11-25 01:53:09 UTC
The new version now takes me to a LIBRE preview screen whereas before it took me directly to the printer's own preview options. When selecting print, the printer dialog appears with "creating print file" which takes a very long time to process LIBRE information. Prior to the upgrade, the print command went directly to the print spool and would start printing almost immediately. This is when using wireless printing through the router which works just fine with my other computer still using the 6.2 version.

Steps to Reproduce:
1.Select PRINT
3.select OK to print

Actual Results:
The Cannon Print Dialog Box will appear on-screen with the phrase CREATING PRINT FILE for which takes up to 2-3 minutes to complete. Sometimes it will state PRINTER PORT IN USE and then switch back to CREATING PRINT FILE. Once it completes printing is normal.

Expected Results:
Create the file for printing immediately instead of going to the new PRINT PREVIEW  page LIBRE created. It will then go to the CANON print preview as it would have initially prior to the upgrade to Version: (x64).

Reproducible: Always

User Profile Reset: Yes

OpenGL enabled: Yes

Additional Info:
Prior to printing and between each page, the printer will do a print head cleaning which uses the ink very fast. If I take it to the printer and use the USB direct connection, printing is completed as normal, quickly, without issue. THE PRINTER USED IS A CANON PIXMA MX922, without fail prior to the upgrade to Version: (x64). The hardware is a TOSHIBA SATELITE LAPTOP without fail prior to the Version: (x64) upgrade.
Comment 1 Xisco Faulí 2019-11-27 14:54:08 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Comment 2 QA Administrators 2020-05-26 03:35:38 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2020-06-26 03:41:28 UTC
Dear Ronald Novak,

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