Bug 490435

Summary:	printing from the selected range of pages does not work correctly
Product:	[Applications] okular	Reporter:	Nazar <nazar2692>
Component:	printing	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED DUPLICATE
Severity:	grave	CC:	bugs.kde.org, erentar2002, jnerin, john.kizer
Priority:	NOR
Version First Reported In:	23.08.1
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Other
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Nazar 2024-07-18 07:21:26 UTC

SUMMARY
printing from the selected range of pages does not work correctly

STEPS TO REPRODUCE
1. File
2. Printing
3. Pages: page range 1,3,5
4. Button - Print

OBSERVED RESULT
prints only the currently displayed page, rather than the selected page range

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: Windows 11 Home
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION

Comment 1 erentar2002 2024-08-01 13:48:43 UTC

I can reproduce this, in my case the pdf has some pages indexed in roman numerals at the start, and after the tenth page it starts roman numerals.
i want to print pages 5,6 (v,vi) however printing `5,6` or `v,vi` does not produce any print output.

Comment 2 Erik Quaeghebeur 2024-12-04 16:03:20 UTC

I also found that printing selected pages does not work. (I'm on Linux, so it seems to be OS-independent.) In my case, it is a pdf with frontmatter in roman numerals and mainmatter in arabic ones (I do not know if that matters). I select 6 non-consecutive pages to print and if I print to a printer, it prints 4 pages (apparently mostly unrelated to the selected ones); if I print to a pdf, it prints everything between the first and last selected page.

I guess this code is seriously broken. Given that the functionality is effectively unusable, I marking this as grave.

Comment 3 John Kizer 2025-05-11 06:21:45 UTC

Hi - merging this together with what I believe is the same underlying issue. This means it's likely based on the upstream Qt printing code, but I'll have to defer to developers to confirm that suspicion. Thanks!

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