Bug 459995

Summary: printing page range selection problem with 2-up
Product: [Applications] okular Reporter: Richard PALO <richard.palo>
Component: printingAssignee: Okular developers <okular-devel>
Status: RESOLVED DUPLICATE    
Severity: normal CC: john.kizer, null
Priority: NOR    
Version First Reported In: 22.08.1   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Richard PALO 2022-10-05 06:45:13 UTC 
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
When selecting a printing range while viewing a pdf file with okular and having selected 2-up pages per sheet,
the pages printed are not the pages indicated, but the resulting 'sheet' number...

STEPS TO REPRODUCE
1.  in a 61 page pdf, select printer
2. in properties, select 2-up
3. in options, select pages 18-19

OBSERVED RESULT
pages 35-38 are output, 2 pages per sheet side

EXPECTED RESULT
pages 18-19 on one sheet side

SOFTWARE/OS VERSIONS

Operating System: EndeavourOS
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.19.13-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 3 5300U with Radeon Graphics
Memory: 15.0 Gio of RAM
Graphics Processor: AMD RENOIR
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: MINIPC PN51-E1
System Version: 0302

ADDITIONAL INFORMATION
upon request
Comment 1 Unknown 2024-06-19 13:15:21 UTC 
Confirmed in "okular" 22.12.3 with QT 5.15.8, Plasma 5.27.9, KDE-Frameworks 5.103.0
on OpenSUSE LEAP 15.5

Especially nerving, as there is no option to preview what actually will be printed – as "kprinter" once provided.
The error is only visible on paper – if one is wise enough to check the result before using the print-out …
Error-checking is not feasible for voluminous print-outs!
Comment 2 John Kizer 2025-06-19 04:07:52 UTC 
Merging together reports for the same underlying issue - thanks!

*** This bug has been marked as a duplicate of bug 432258 ***