Can't sign ubuntu core model assertion
Metadata
Current evaluation
`snap sign` of a Ubuntu Core model assertion fails with "gpg: signing failed: No such file or directory"; ~ogra identified a stuck gpg-agent/pinentry lock in the user's environment and linked a forum workaround. Untriaged further.
Suggested action: keep open
Reason: The report is a real, reproducible failure of an official UC image-building step ("error: cannot sign assertion: ... --detach-sign failed"), and it already has triage: labels assertion/sign/snap plus a maintainer reply from ~ogra stating "there is a known issue with gpg-agent not freeing the lock" and pointing at the snapcraft forum thread (https://forum.snapcraft.io/t/snap-sign-unable-to-invoke-gpg-agent-pinentry/10938). However, nothing in this repo can fix it — snapcraft only shells out to `snap` for key/assertion work (snapcraft/commands/keys.py:162 calls `subprocess.create-key`), and there is no signing or gpg-agent handling here, no resolving commit/PR, and no evidence of deprecation, so closing is not justified. Low actionability because the root cause sits in snapd/the user's local gpg-agent state, making the concrete fix target (docs note, better error message, or snapd-side handling) ambiguous and requiring investigation.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
5
Complexity:
55
Confidence:
70
Actionability:
30
|
keep open | `snap sign` of a Ubuntu Core model assertion fails with "gpg: signing failed: No such file or directory"; ~ogra identified a stuck gpg-agent/pinentry lock in the user's environment and linked a forum workaround. Untriaged further. | |
| stealth/space-bunny-alpha |
Impact:
28
Quick Win:
10
Complexity:
22
Confidence:
72
Actionability:
45
|
close not a bug | `snap sign` fails with "gpg: signing failed: No such file or directory" when signing a UC model assertion; cause is a stuck gpg-agent/pinentry in the user's environment, not snapcraft. Maintainer pointed to a known-issue thread with workaround. | |
| stealth/space-bunny-alpha |
Impact:
50
Quick Win:
11
Complexity:
55
Confidence:
70
Actionability:
48
|
needs triage | Ubuntu Core model signing via `snap sign` fails with a GPG exit-status-2 error; `snapcraft create-key` reportedly allows only one successful signature before the same failure recurs. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
12
Staleness:
95
Complexity:
40
Confidence:
65
Support Request:
50
|
close stale | 2019 report that snap sign fails with a GPG error when signing an Ubuntu Core model assertion; after snapcraft create-key it signs once, then fails again. No labels, no maintainer response, no activity for ~6.5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
40
Confidence:
85
Support Request:
60
|
close stale | User reports GPG signing failures when creating Ubuntu Core model assertions following official tutorials. Issue has been completely inactive for over six years with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
35
Confidence:
90
Support Request:
65
|
close stale | GPG signing fails when creating Ubuntu Core model assertions per tutorial. Issue inactive for 6+ years with no maintainer response or follow-up. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
90
|
close not a bug | User reports GPG signing error when creating Ubuntu Core images following a tutorial. Inactive for over six years with no maintainer response. Appears to be a local GPG configuration issue rather than a tool defect. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.