Bug 451128 - "Print to file (PDF)" always defaults to A4 paper size
Summary: "Print to file (PDF)" always defaults to A4 paper size
Status: RESOLVED DUPLICATE of bug 420928
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-04 12:45 UTC by billgee
Modified: 2022-03-22 02:28 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description billgee 2022-03-04 12:45:01 UTC
SUMMARY
In any KDE application - When printing to the "Print To File (PDF)" device, the paper size defaults to A4.  It can be changed to another size, but this must be done for every print job.

This device does not appear under System Settings - Printers.  Other printers that do show up there have been set to default to US Letter paper size.


STEPS TO REPRODUCE
1. Open any KDE application.  Gwenview, for example, though it happens in all KDE apps.
2. Open a document.
3. Pull down File and choose Print.
4. Choose the "Print To file (PDF)" device from the list of printers.
5. Click the Properties button.  Observe that the paper size is A4.  Change the paper size to something else.
6. Run the print job.
7. Repeat and notice that the paper size is once again A4.

OBSERVED RESULT
The default paper size for the "Print To File (PDF)" device is always A4.  The default cannot be changed.

EXPECTED RESULT
Some way should be provided to change the default paper size for the "Print To File (PDF)" device.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.9-200.fc35.x86_64 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5 CPU 760 @ 2.80GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GT 710/PCIe/SSE2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-03-22 02:28:37 UTC

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