Bug 502236

Summary: Specifying pages when printing sends the specified pages to the printer but also sends the original range to the printer
Product: [Applications] okular Reporter: Roman Karwacik <roman.karwacik>
Component: printingAssignee: Okular developers <okular-devel>
Status: RESOLVED DUPLICATE    
Severity: normal CC: john.kizer
Priority: NOR    
Version First Reported In: 24.12.3   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Roman Karwacik 2025-03-31 12:13:59 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. Open A PDF with at least 2 pages (my PDF has 4 pages)
2. File -> Print
3. Expand the Options
4. Select the "Pages" Checkbox
5. Put in "2"

OBSERVED RESULT
No document is printed

EXPECTED RESULT
Page 2 is printed

SOFTWARE/OS VERSIONS
Linux: Fedora 4

ADDITIONAL INFORMATION
I inspected the IPP traffic using Wireshark, and the document which is sent to the server when doing the steps above is identical to using the "current page" checkbox, but the "current page" checkbox IS working. In the IPP Create-Job Request the page-ranges job-attribute-tag is specified only for the explicit specification of the pages, this attribute seems to be the only difference to the two methods on a protocol level. It seems like with the okular is cropping the pages according to the specification on the Pages checkbox, and is additionally sending the page ranges, when it does not have to do this.
Comment 1 Roman Karwacik 2025-03-31 12:15:16 UTC
Sorry, I forgot to remove the header. I am using Fedora 41 with Okular okular-24.12.3-1.fc41.x86_64
Comment 2 John Kizer 2025-04-10 18:08:24 UTC
Hi - merging this in with an existing bug report for what appears to be the same issue. Thanks!

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