Thanks Tomas. Your screenshot narrows this down: GPG successfully finds your key and creates the signature. The failure happens afterwards, when appimagetool tries to embed the public key into the AppImage:
cannot embed key in AppImage: size exceeds reserved ELF section size
The AppImage runtime reserves a fixed amount of space for that public key, currently 8,192 bytes upstream. The error means the exported public-key data exceeds the available space. It is separate from the size of your application.
I haven’t established why this started happening now. Studio’s signing invocation hasn’t changed between 26.11.3 and 26.11.4, but your log shows appimagetool downloading its runtime from upstream’s continuous release. I need to compare the key size and runtime section size before drawing a conclusion.
Could you run the following commands under the same Linux account you use for Studio and paste the output?
First, the tool locations and versions:
command -v appimagetool
appimagetool --version
command -v gpg
gpg --version
Next, the size of the exported public key. I’ve used the fingerprint shown in your screenshot:
signing_key='61A2979309565F8A668689C67582A2F3DCD63CC9'
# Normal public-key export size, in bytes
gpg --armor --output - --export "$signing_key" | wc -c
# Minimal public-key export size, in bytes
gpg --armor --export-options export-minimal --output - --export "$signing_key" | wc -c
These print byte counts, not the key itself. The minimal export is only a diagnostic comparison; it does not modify your stored key.
If the failed publish left an .AppImage file behind, please inspect its reserved sections too. Replace the example path with that file’s actual path:
readelf --wide --section-headers "/full/path/to/failed.AppImage" |
grep -E 'Name|\.sig_key|\.sha256_sig'
If you still have an older, successfully signed AppImage, please run the same command against that file as well. If readelf is unavailable, just let me know.
Please also tell me which Studio version last signed successfully, and whether appimagetool, GnuPG or the signing key changed since then.
I’m treating the missing signing setting separately. Were you updating from 26.11.3, and are you using a single .objo file or a folder-based .objosln solution? After re-entering the signing identity, does it remain there when you save, close and reopen the solution?
The green readiness checks currently confirm that the tools and key are available, but they don’t catch this size limit. I’ll need to improve that diagnostic too.