using executable from core snap fails sanity check

Metadata

Project: snapcraft (launchpad)
Number: #1751828
Type: issue
State: open
Author: ~ondrak
Labels: —
Created: 2018-02-26 04:01 PM UTC
Updated: 2018-02-26 04:01 PM UTC
Closed: —

Current evaluation

Snapcraft's sanity check fails when an application command references an executable provided by the core snap (e.g., ping). Workaround: install the binary on the build host. Unanswered since 2017. Old host-based check likely obsolete in modern snapcraft.

Suggested action: close stale

Reason: The issue is 3108 days old with 0 comments, no labels, and no maintainer interaction, and it describes the pre-core22 snapcraft's host-based sanity check, whose affected versions are no longer supported after the project's full rewrite. The reporter's suggested fix (checking against core + snap contents rather than the host) reflects how modern snapcraft validates, so the original problem is likely no longer reproducible. Confidence is moderate because the repo tooling failed (no pinned SHA), so I could not directly confirm the current check behavior in code.

Impact: 35 Quick Win: 21.0 Staleness: 95 Complexity: 40 Confidence: 55 Support Request: 10

Issue body

When using executable from core snap for application command, snapcraft will fail with sanity check. Example of using 'ping' is here: https://github.com/kubiko/avahi-client/blob/master/snap/snapcraft.yaml Workaround is to install desired executable on building host, then check passes. Suggesting snapcraft checks against host, which seems wrong. Surely check should be against core + content of the snap itself (ignoring confinement restriction for binaries in core)

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-01 08:21 AM UTC	qwen/qwen3.8-27b	Impact: 35 Quick Win: 21.0 Staleness: 95 Complexity: 40 Confidence: 55 Support Request: 10	close stale	Snapcraft's sanity check fails when an application command references an executable provided by the core snap (e.g., ping). Workaround: install the binary on the build host. Unanswered since 2017. Old host-based check likely obsolete in modern snapcraft.
2026-07-23 11:55 AM UTC	qwen/qwen3.6-35b-a3b	Staleness: 98 Complexity: 25 Confidence: 95 Support Request: 15	close stale	Snapcraft fails a sanity check when referencing executables from the core snap. Reported over 8 years ago with no maintainer response or updates.
2026-07-22 12:19 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 95 Complexity: 40 Confidence: 90 Support Request: 10	close stale	Snapcraft sanity check fails when using executables from core snaps. Reported over 8 years ago with zero maintainer interaction or updates.
2026-07-09 11:21 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 98 Complexity: 35 Confidence: 85 Support Request: 10	close stale	Snapcraft fails sanity checks when using executables from the core snap. Unlabelled, unresponded to, and inactive for over 8 years.
2026-06-21 01:30 PM UTC	qwen3.6-35b-moe-q4	Staleness: 95 Complexity: 55 Confidence: 85 Support Request: 20	close stale	Snapcraft sanity check fails when using executables from core snaps. Untriaged, no maintainer interaction, and over 8 years old.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.