SUMMARY Can't print 4 pages per sheet and then odd/even for double-sided printing for printers that not allowed to print double-sided by itself STEPS TO REPRODUCE 1. Options page set -> odd/even 2. Select printer options and pages by sheet 3. Error message: pages by sheet and pages set cant selected at the same time EXPECTED RESULT Print 1 2 3 4 in the first page print 9 10 11 12 int the second page ... and then print 5 6 7 8 in the first page by the other side changing the paper... ACTUAL RESULT Error message: pages by sheet and pages set cant selected at the same time SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION
Already submitted as Bug 399030. Let's track the issue there.
(In reply to Nate Graham from comment #1) > Already submitted as Bug 399030. Let's track the issue there. Right, so it's a duplicate. *** This bug has been marked as a duplicate of bug 399030 ***
At one point I was told not to mark duplicates when a single reporter opened two bugs, because it could artificially inflate the apparent severity of the bug, because the number of duplicates is useful information. If that's no longer the case, I'll happily mark these kinds of bugs as duplicates from now on.
(In reply to Nate Graham from comment #3) > At one point I was told not to mark duplicates when a single reporter opened > two bugs, because it could artificially inflate the apparent severity of the > bug, because the number of duplicates is useful information. It may be project specific - I don't remember such rule. Do you have any pointer or was it discussed in person/through messaging systems?
It was in the bug itself, but it was so long ago I can't remember which one it was, sorry. We don't have any guidelines one way or the other on https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging or https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging/Identifying_duplicates
Nate is right. Someone looking at bug 399030 might check the duplicates to gather more information, and we want to spare developers from reading the exact same information again. We used to have the INVALID resolution, but NOT A BUG is the best we have now.
I disagree with this guideline. The volume of exact duplicate bugs due to user error is not so high to make developers waste their time. On the other side, the connection between the two bugs is lost. Maybe a new sub-state EXACT_DUPLICATE could solve the issue, but notwithstanding, I think that DUPLICATE is the correct solution.
The connection is not lost if we continue to say "Already reported as bug #" and link to the first bug reported in the series of multiple exact duplicates.