`stage-snaps: mir-kiosk-x11` segfaults on `base: core18`
Metadata
Current evaluation
Closed as stale after the core18/core20 stage-snaps switch could not be reproduced; no reproducer or fixing PR or commit was supplied.
Resolution: closed stale
Reason: Maintainer cmatsuoka could not reproduce the segfault with current Snapcraft, and reporter ~saviq said no easy reproducer was available without a mixed-core test snap. No merged fix or explanatory closing comment is shown, so the inactive report is best classified as stale.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Given this yaml:
```
name: try-kiosk-x11
adopt-info: mir-kiosk
summary: Segfault on stage-snaps
description: |
This shows snapcraft segfaulting on stage-snaps
confinement: strict
base: core18
architectures:
- build-on: amd64
parts:
mir-kiosk:
plugin: nil
stage-snaps:
- mir-kiosk-x11/latest/beta
```
Snapcraft segfaults in `snapcraftcl pull`. The snap in `stable` channel is a `base: core20` one, which was suspect, but the `beta` channel is `core18`. Both cause a segfault.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed as stale after the core18/core20 stage-snaps switch could not be reproduced; no reproducer or fixing PR or commit was supplied. | |
| stealth/space-bunny-alpha | — | closed stale | Abandoned: no code fix. Maintainer cmatsuoka (2021-11-22) could not reproduce the segfault; reporter had no reproducer, so the bug was closed with no resolving PR or commit. | |
| stealth/space-bunny-alpha | — | closed stale | Snapcraft’s core18 stage-snaps segfault was reported as abandoned and closed without a fixing PR or commit. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The snapcraft segfault when staging mir-kiosk-x11 on core18 was closed without a fix or developer follow-up. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. The snapcraft segfault triggered by staging mir-kiosk-x11 on core18 was resolved. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Snapcraft segfaults during pull when staging mir-kiosk-x11 on core18. No fix provided. Tracked as craft-416. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without discussion. The snapcraft segfault when staging mir-kiosk-x11 on core18 was not addressed, indicating abandonment or internal resolution. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1849707
(confidence 80%)
Describes the related mixed-core stage-snaps failure and remains open.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1849707 stage-snap causes issues when mixing cores | snapcraft (launchpad) | open | Staging a core16 snap into core18 reportedly overwrote build tools and caused file collisions; the proposed mismatch warning is untriaged, and core18 support has since been removed. | |
| #1926355 Snap applications segfault with new core20 (rev: 1015+) | snapcraft (launchpad) | closed | Resolved by Snapcraft 4.6.1 (commit 0bf7a2e), which stopped erroneously staging libc; glibc 2.31-0ubuntu9.4 also reverted the incompatible 9.3 change. Affected snaps require rebuilding. |