Summary: | Okular is unable to print to fit page | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | gregorystarr00 |
Component: | printing | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | m.weghorn, nate |
Priority: | NOR | ||
Version First Reported In: | 1.10.1 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
This highlights the broken print.
Settings |
Description
gregorystarr00
2020-06-07 23:00:56 UTC
> with print set to fit
Can you clarify what this means? How did you set it exactly? Did you happen to check the "Force Rasterization" checkbox?
Created attachment 129331 [details]
Settings
No, I didn't enable force rasterization. Everythnig was stock, except for printer properties.
Works fine for me in a quick test with Okular 1.10.2 on Debian testing using the CUPS-PDF printer using A4 as page size. Does it work for you when "printing" using CUPS-PDF instead of the actual printer as well? If so, you please attach: * your printer's PPD file, located at /etc/cups/<PRINTERNAME>.ppd * CUPS log (or relevant part of that for the print job): /var/log/cups/error_log, with 'LogLevel debug' set in /etc/cups/cupsd.conf (might have to set 'ErrorLog /var/log/cups/error_log' in '/etc/cups/cups-files.conf' or otherwise search in journal, depending on how your distro configures this) And does it work if you explicitly enable rasterization? This might help to avoid issues with the CUPS filter chain, s.a. bug 422690. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |