← Back to issue list

Classic confined snap started segfaulting after 2.40 upgrade

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1760897
Type
issue
State
open
Author
~kos.tsakalozos
Labels
—
Created
Updated
Closed
—

Current evaluation

2018 report that a classic confined snap (kubernetes-test) segfaults when built with snapcraft 2.40 due to patchelf/ELF buildid stripping; reporter found a no-patchelf workaround. No maintainer response in 8+ years; affected version long superseded.

Suggested action: close stale

Reason: The issue is 8+ years old with zero comments, no labels, and no maintainer interaction, and the reporter already has a working workaround (no-patchelf). The affected snapcraft 2.40 is long superseded and the ELF/patchelf code has since been rewritten (snapcraft/elf/), so the original problem is no longer reproducible in current versions; the related 2.37 regression (LP #1736861) was resolved in a later release.

Impact: 15 Quick Win: 8.25 Staleness: 95 Complexity: 45 Confidence: 80 Support Request: 40

Issue body

Our kuberentes-test snap is crashing when built with 2.40 snapcraft. The snap's yaml looks like this now: https://raw.githubusercontent.com/juju-solutions/release/rye/snaps/snap/kubernetes-test.yaml We had to add "build-attributes: [no-patchelf]" to get it working again. Here are two runs with different builds of the same snap where we have a working version and a failing one: https://pastebin.ubuntu.com/p/f4552kVxVK/ Here is also the build process with debug enabled: https://pastebin.ubuntu.com/p/jTm7TBJH4B/ There is this error message during build: "cannot find section Failed to update '/home/jackal/workspace/charms/release/snap/build/kubernetes-test/prime/ginkgo'. Retrying after stripping the .note.go.buildid from the elf file." Is this an expected behaviour? Is it something we should change in our snap? Or is it an indication of a bug? Thanks.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 15
Quick Win: 8.25
Staleness: 95
Complexity: 45
Confidence: 80
Support Request: 40
close stale 2018 report that a classic confined snap (kubernetes-test) segfaults when built with snapcraft 2.40 due to patchelf/ELF buildid stripping; reporter found a no-patchelf workaround. No maintainer response in 8+ years; affected version long superseded.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 55
Confidence: 92
Support Request: 40
close stale Classic confined snap segfaults after snapcraft 2.40 upgrade due to ELF stripping. Reporter applied a workaround. No maintainer interaction in over 8 years.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 65
Confidence: 90
Support Request: 20
close stale Classic confined snap segfaults after snapcraft 2.40 upgrade; workaround involves no-patchelf. Issue is 8+ years old with no maintainer interaction or updates.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 35
Confidence: 75
Support Request: 20
close stale Classic snap built with snapcraft 2.40 segfaults due to ELF stripping. No maintainer response in over 8 years. Workaround exists.
qwen3.6-35b-a3b-mtp-q6
Staleness: 100
Complexity: 45
Confidence: 95
Support Request: 20
close stale Classic snap segfaults after snapcraft 2.40 upgrade. Reporter suggests no-patchelf workaround. No maintainer response, completely inactive for over eight years.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft#1736861 (confidence 65%)

    Same 'cannot find section' patchelf failure class in classic snaps (2.37 regression); closed as resolved in a subsequent release.

  • Related To: snapcraft#1753995 (confidence 60%)

    Same 'cannot find section' warning plus segfault on a Go binary (telegraf) with snapcraft 2.39.2; open with no maintainer response, version superseded.

Related issues

Issue Project State Summary Similarity
#1736861 classic snap fails to build with "cannot find section" snapcraft (launchpad) closed Closed without comments or resolution. The snapcraft 2.37 regression causing patchelf failures in classic snaps was abandoned or resolved in a subsequent release.
77%
#1753995 patchelf warning / binary segfaults snapcraft (launchpad) open 2018 report: snapcraft 2.39.2 patchelf step warns 'cannot find section' on a Go binary (telegraf) and the resulting snap segfaults (core-dump). No maintainer response. Referenced LP bug lp:1736861 is closed as resolved. Affected version long superseded.
75%
#1752957 Building classic snap without core snap installed succeeds, but creates snap that doesn't run snapcraft (launchpad) open Snapcraft 2.39.x crashes with TypeError building a classic snap without the core snap installed, as get_core_dynamic_linker() returns None during patchelf. No comments or labels; 2.x series is EOL and the code path no longer exists in the current codebase.
72%