Public Key decryption failed: Not enough space

GnuPG Help
1

I keep coming across an intermittent issue when decrypting files and am met with the following outputs

Public key decryption failed: Not enough space

decrpytion failed: Not enough space

I’ve seen a similar issue reported here: gpg: signing/decryption failed: Not enough space
However, we only use the simple GnuPG installer, so configuring Kleopatra doesn’t appear to be the solution. Is there a similar registry edit available?

2

Just to check the obvious: Is your disk not full?

If not, what is the command you execute (with personal data removed)? Could you retry with gpg --verbose ...

3

I can confirm there’s plenty of space on the disk.

Will take a while to get the verbose output, as it’s only occurring intermittently on one system that requires all changes to be approved.

The command as stands is:

gpg --quiet --batch --no-tty --no-mangle-dos-filenames --yes --passphrase-fd 0  --multifile --decrypt <FILES>

Just to confirm this is using the latest version 2.4.8

4

are these files particularly large? maybe the problem isn’t missing space on the disk you want to write to in the end, but a different partition where temporary files are written?

5

The files aren’t particularly large, probably 10-15mb at most. However, there is potential for multiple concurrent decryption actions to be performed which may give the same result.

My internal change request has been approved so hopefully should have the output of –verbose by tomorrow morning.

6

Have finally got the –verbose output and it doesn’t offer much more information unfortunately:

stderr>gpg: enabled compatibility flags:
Waiting for command gpg --verbose --quiet --batch --no-tty --no-mangle-dos-filenames --yes --passphrase-fd 0 --max-output 33554432 --decrypt-files FILE.xml.gpg to finish
stderr>gpg: public key is REMOVED
stderr>gpg: public key decryption failed: Not enough space
stderr>gpg: decryption failed: Not enough space
Command failed: gpg --verbose --quiet --batch --no-tty --no-mangle-dos-filenames --yes --passphrase-fd 0 --max-output 33554432 --decrypt-files FILE.xml.gpg with non-zero return code: 2

For further context, there’s at least 100GB free space on the drive for this a 4kb file.
GPG_HOME is on another drive that has at least 20GB free

I wonder if there might be a regression somewhere, I’ve only noticed this error when upgrading to to 2.4.X from a 2.2 version. Failing that is there anyway to look at the conditions that would flag this error?