[pdfarranger]

Yeneros · January 16, 2026, 8:14am

[ After a recent update i can’t Save using pdfarranger.

Two computers confirmed working before upgrade now fail to save pdf files.

Roll-back to previous version(s) fails to produce a working application… 1.11, 1.10, 1.9…

To reproduce try opening a pdf and saving it as a new name before and after upgrade.

Currently I’m using a third computer to save pdf using old versions without updating.

May be pikepdf or libqpdf issue?]

Bink · January 16, 2026, 8:19am

Try running:

sudo downgrade pdfarranger

Select the previous version.

Looks like it may be a known issue too:

github.com/pdfarranger/pdfarranger

Attempting to save merged PDFs fails with Python error

opened 08:43AM - 15 Jan 26 UTC

JBNorwich

Describe the bug ---------------- Trying to merge two PDFs into one and save as… a different file name. However PDFArranger silently fails to save the file. When running in a terminal, a Python error appears saying "No such file or directory" on os.getcwd: ``` Traceback (most recent call last): File "/usr/lib/python3.14/site-packages/pdfarranger/pdfarranger.py", line 1450, in on_action_save_as self.choose_export_pdf_name('ALL_TO_SINGLE') ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/pdfarranger/pdfarranger.py", line 1372, in choose_export_pdf_name self.save(exportmode, files_out) ~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/pdfarranger/pdfarranger.py", line 1481, in save self.export_process.start() ~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/lib/python3.14/multiprocessing/process.py", line 121, in start self._popen = self._Popen(self) ~~~~~~~~~~~^^^^^^ File "/usr/lib/python3.14/multiprocessing/context.py", line 224, in _Popen return _default_context.get_context().Process._Popen(process_obj) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib/python3.14/multiprocessing/context.py", line 288, in _Popen return Popen(process_obj) File "/usr/lib/python3.14/multiprocessing/popen_spawn_posix.py", line 32, in __init__ super().__init__(process_obj) ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib/python3.14/multiprocessing/popen_fork.py", line 20, in __init__ self._launch(process_obj) ~~~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib/python3.14/multiprocessing/popen_spawn_posix.py", line 42, in _launch prep_data = spawn.get_preparation_data(process_obj._name) File "/usr/lib/python3.14/multiprocessing/spawn.py", line 186, in get_preparation_data dir=os.getcwd(), ~~~~~~~~~^^ FileNotFoundError: [Errno 2] No such file or directory ``` This happens when saving **any** file, including when not trying to merge at all, or when trying to save over any other file. To Reproduce ------------ Steps to reproduce the behavior: 1. Open PDFarranger. 2. Open a PDF 3. Save the file. Expected behavior ----------------- The PDF saves. Input files ----------- I cannot attach any specific files as they are confidential but I have tested on multiple other files and the same behaviour repeats. System and Versions ------------------- - Arch Linux - all packages from distro archives - python-pikepdf 10.2.0-1 - python-multiprocess 0.70.18-2 (tried downgrading to previous version, no change) - pdfarranger 1.12.1-2 - Running under latest KDE Plasma on Wayland (not sure matters)

Yeneros · January 16, 2026, 8:45am

[ Thanks.

That does seem to be this bug.

Unfortunately Roll-back doesn’t work. ]

Bink · January 16, 2026, 8:47am

Hmm… was it an update to Python causing the issue then?

Python can get a bit messy with issues like that. You could try rolling back again (select an even older version of pdfarranger, or wait for the bug to be fixed?

Bink · January 16, 2026, 8:50am

Hmm… was it an update to Python causing the issue then?

Python can get a bit messy with issues like that. You could try rolling back again (select an even older version of pdfarranger, or wait for the bug to be fixed?

The latest update’s note is:

upgpkg: 1.12.1-2: Rebuild for Python 3.14
Source

So perhaps it is a Python issue.

Yeneros · January 23, 2026, 7:39am

[ Culprit is qpdf.

Solution is downgrading package qpdf (12.3.1-2 => 12.2.0-1)

downgrade qpdf

]

fog · January 23, 2026, 8:06am

A week ago, I was also dealing with this issue.
Yesterday, I discovered that the problem had been solved without me having to downgrade.

Is your os fully updated?

Edit: Add screenshot: