Bug 139378 - Wrong page announcement when PRINTING to printer driver
Summary: Wrong page announcement when PRINTING to printer driver
Status: RESOLVED DUPLICATE of bug 127932
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.6.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-03 00:14 UTC by Michael
Modified: 2021-01-03 17:25 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
picture of pop-up (225.68 KB, image/jpeg)
2021-01-03 00:17 UTC, Michael
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael 2021-01-03 00:14:25 UTC
Description:

When printing to a printer driver, a pop-up announces the number of pages that will be printed. In writer, this number is too high by a factor of 10. One page actually to be printed, 10 are announced. 2 pages actually to be printed, 20 are announced. etc.

This is annoying and will startle a user not expecting it immensely. In particular when printing to paper a document with a high page-count to start with.


Steps to Reproduce:
1. <CTRL>-p
2. select printer
3. [OK]


Actual Results:
Pop-Up announces the number of pages that will be printed, but multiplied by a factor of 10.


Expected Results:
Pop-Up announces the number of pages that will be printed.


Reproducible: Always


User Profile Reset: No


Additional Info: 
This happens when printing to Brother HL-2250DN, PDF-Writer, PDF24.
This does not happen with PDF-Export.
Comment 1 Michael 2021-01-03 00:17:42 UTC
Created attachment 168637 [details]
picture of pop-up
Comment 2 Julien Nabet 2021-01-03 10:13:28 UTC
Could you give a try to 6.4.7 or rather 7.0.4?
Indeed, even if you reproduce this in 6.4.7, it won't be fixed since it's EOL.
Comment 3 Timur 2021-01-03 14:00:48 UTC
Let's assume duplicate. 
As already advised, if repro with newer LO set Unconfirmed.

*** This bug has been marked as a duplicate of bug 127932 ***
Comment 4 Michael 2021-01-03 17:25:03 UTC
I confirm it has been fixed in 7.0.3 or previous.