snapcraft configure hook fails: segmentation fault
Metadata
Current evaluation
Snapcraft snap's configure hook segfaults on AWS arm64 GitHub runners during install. Maintainer requested diagnostic logs in Dec 2023; reporter never responded. Unlabelled, inactive ~18 months, snap since reworked to core24.
Suggested action: close stale
Reason: Maintainer @mr-cal explicitly requested `snap tasks --last=configure` logs on 2023-12-04 and the reporter never provided them, leaving the issue unactionable for ~18 months (last activity 536 days ago). The snapcraft snap has since been substantially reworked (core22 → core24 migration, new configure-hook shebang handling in fc985d4c5), so the specific 2023 arm64 segfault is very likely no longer reproducible on current releases.
Impact:
40
Quick Win:
18.0
Staleness:
80
Complexity:
55
Confidence:
68
Support Request:
10
Issue body
### Bug Description
When installing the `snapcraft` snap on an AWS arm64 GitHub runner, the "configure" hook fails
```
error: cannot perform the following tasks:
- Run configure hook of "snapcraft" snap if present (run hook "configure": signal: segmentation fault)
```
### To Reproduce
Run the following GitHub workflow:
```yaml
jobs:
snap:
name: linux-arm64
runs-on: [self-hosted, linux, arm64, aws, large]
steps:
- name: Install Dependencies
shell: bash
run: |
set -euxo pipefail
sudo snap install snapcraft --classic
```
### Environment
Distribution: Ubuntu 22.04.3 LTS
Architecture: aarch64
on AWS
### snapcraft.yaml
```shell
N/A
```
### Relevant log output
```shell
+ sudo snap install snapcraft --classic
error: cannot perform the following tasks:
- Run configure hook of "snapcraft" snap if present (run hook "configure": signal: segmentation fault)
```
### Additional context
Run here: https://github.com/juju/juju/actions/runs/6783177627/job/18436880350?pr=16548
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
18.0
Staleness:
80
Complexity:
55
Confidence:
68
Support Request:
10
|
close stale | Snapcraft snap's configure hook segfaults on AWS arm64 GitHub runners during install. Maintainer requested diagnostic logs in Dec 2023; reporter never responded. Unlabelled, inactive ~18 months, snap since reworked to core24. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
60
Confidence:
85
Support Request:
20
|
close stale | Segfault during snapcraft configure hook on AWS arm64 runners. Unlabelled, inactive for over a year, and reporter did not provide requested debug logs. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
92
Complexity:
45
Confidence:
85
Support Request:
10
|
close stale | Segfault in snapcraft configure hook on AWS arm64 Ubuntu 22.04. Maintainer requested debug logs via snap tasks --last=configure, but no response provided. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
45
Confidence:
85
Support Request:
10
|
close stale | snapcraft snap installation fails with a segmentation fault in the configure hook on AWS arm64 Ubuntu 22.04. Issue remains open, awaiting requested diagnostic logs. Inactive for over a year. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1746403 snapcraft fails to find hooks if ran from snap directory. | snapcraft (launchpad) | open | 2017 report: running snapcraft from the snap/ directory builds without error but omits hooks, causing confusing install failures; proposes enforcing project-root CWD. No maintainer activity in 8+ years; likely obsolete after the core22 rewrite. | |
| #1999321 Snapcraft is stuck on "launching instance..." indefinitely | snapcraft (launchpad) | open | Snapcraft hangs indefinitely on 'launching instance...' on arm64 architectures (M1 Mac, Fedora 37 arm64, Asahi Linux). No maintainer response or labels after 1362 days. | |
| #2099923 Snapcraft builds are failing: install of snap "snapcraft" failed | snapcraft (launchpad) | open | Snapcraft builds failing due to outdated snapd (2.61) on build infrastructure unable to install core20 base. Issue is 556 days old with no maintainer response. |