Bug 121564 - Selecting a different printer in the dialog box of Windows 10 elevates the number of copies
Summary: Selecting a different printer in the dialog box of Windows 10 elevates the nu...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
6.0.6.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: corruptProfile
Depends on:
Blocks: Print-Dialog
  Show dependency tree / graph
 
Reported: 2018-11-20 19:40 UTC by NameknowntotheNSA
Modified: 2018-11-28 17:29 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description NameknowntotheNSA 2018-11-20 19:40:15 UTC 
Description:
Working with several printers under Windows 10, I have run into the above issue.
The default printer has "1" as the number of copies in the "print" dialogue, as it should. If you then try to select another printer, the number of copies will be automatically elevated to another number (3, 5..) - this number seems to follow the alphabetically sorted position of the selected printer (like Canon=2, Epson=3, HP=5 etc.). My current version of LO is 6.0.6.2 (x64), Windows ver. 1803 (build 17134.407) - the previous version already had this bug, but it took some time to trace. The workaround is easy: reset the number to 1 before printing.

Steps to Reproduce:
1. Call Printer dialog (ctrl+p)
2. Select a different printer 
3. Check the number of copies

Actual Results:
see description

Expected Results:
incorrect number of copies printed if you overlook the changed number in the dialog box


Reproducible: Always


User Profile Reset: No



Additional Info:
The number should have remained at the default "1"
Comment 1 NameknowntotheNSA 2018-11-20 19:41:22 UTC 
at two other machines (same OS and LO version) the bug doesn't occur, but different printers (may be driver-specific?
Comment 2 raal 2018-11-23 21:02:10 UTC 
I can not confirm with Version: 6.2.0.0.beta1+
Build ID: 268364e35100b559f42d8c02b930c5cca1c84be7
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Comment 3 NameknowntotheNSA 2018-11-23 21:13:03 UTC 
(In reply to raal from comment #2)
> I can not confirm with Version: 6.2.0.0.beta1+
> Build ID: 268364e35100b559f42d8c02b930c5cca1c84be7
> CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;

The bug does occur in Windows 10 (see orig. report), may be config specific
Comment 4 Roman Kuznetsov 2018-11-27 08:44:37 UTC 
don't repro in

Version: 6.2.0.0.beta1
Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded

and in

Version: 6.1.2.1
Build ID: 65905a128db06ba48db947242809d14d3f9a93fe
CPU threads: 4; OS: Windows 6.1; UI render: default; 
Locale: ru-RU (ru_RU); Calc: group threaded

only Windows 10 problem?
Comment 5 NameknowntotheNSA 2018-11-27 23:31:26 UTC 
Probably so, and not on every machine, will try completely uninstalling and installing LO again and reassess this as soon as I have spare time (next weekend?)
Comment 6 Timur 2018-11-28 15:51:17 UTC 
Please see Bug 119250 and reset profile as a solution, no need to reinstall.
Comment 7 NameknowntotheNSA 2018-11-28 16:52:08 UTC 
(In reply to Timur from comment #6)
> Please see Bug 119250 and reset profile as a solution, no need to reinstall.

Thank you very much - this was indeed the solution.
Comment 8 raal 2018-11-28 17:29:19 UTC 
I think we can close the bug.