Building a classic snap on trusty doesn't work
Metadata
Current evaluation
Trusty classic-snap build segfaults traced to core paths in LD_LIBRARY_PATH. Proposed fix PR canonical/snapcraft#2128 was closed unmerged as unnecessary, leaving the bug unfixed.
Resolution: closed stale
Reason: No fix landed: the only proposed resolution, PR canonical/snapcraft#2128 ('project_loader: stop setting LD_LIBRARY_PATH'), was closed unmerged after the last known Trusty classic-snap user moved to Xenial, and the Launchpad bug was closed with no further work.
Evaluated by: mr-cal-bot
No scores available.
Issue body
If one tries to build a classic snap on trusty, whenever Snapcraft tries to execute anything (e.g. cmake, or a scriptlet) the executed thing segfaults. For example:
Preparing to pull my-part
Pulling my-part
Preparing to build my-part
Building my-part
cmake /snapcraft/tests/smoke/classic/parts/my-part/src -DCMAKE_INSTALL_PREFIX=
Failed to run 'cmake /snapcraft/tests/smoke/classic/parts/my-part/src -DCMAKE_INSTALL_PREFIX=' for 'my-part': Exited with code -11.
Verify that the part is using the correct parameters and try again.
This should either work, or fail in a nicer way.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Trusty classic-snap build segfaults traced to core paths in LD_LIBRARY_PATH. Proposed fix PR canonical/snapcraft#2128 was closed unmerged as unnecessary, leaving the bug unfixed. | |
| stealth/space-bunny-alpha | — | closed stale | Trusty classic-snap build segfaults were traced to core library paths in LD_LIBRARY_PATH. Proposed fix PR #2128 was closed unmerged after affected users moved to Xenial. | |
| stealth/space-bunny-alpha | — | closed stale | Closed unresolved after becoming inactive. Trusty classic-snap builds segfaulted when executing tools (LP #1765482); no resolving PR or commit was recorded. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The Trusty classic snap build segfault was likely abandoned or superseded by newer OS versions, as no fix or discussion was recorded. | |
| qwen/qwen3.6-35b-a3b | — | — | Segfaults during classic snap builds on Ubuntu Trusty were reported but the ticket closed without resolution. Likely abandoned or superseded by discontinued OS support. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution, likely abandoned or superseded by dropped Ubuntu Trusty support. The report detailed segfaults during classic snap builds on Trusty. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned without resolution. Classic snap builds on Ubuntu Trusty caused segfaults during command execution. Zero comments and significant age indicate the issue was closed following Trusty's end-of-life. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
canonical/snapcraft#2128
(confidence 95%)
Fix PR cited in the issue comments (kyrofa, 2018-05-10); closed unmerged with no code changes.
-
Related To:
canonical/snapcraft#4216
(confidence 35%)
Later commit 9b6e58337 omits LD_LIBRARY_PATH/PATH for classic confinement, related area but not the Trusty build crash.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1723208 Snapcraft snap doesn't work natively on trusty | snapcraft (launchpad) | closed | Fixed Trusty classic-snap builds by preventing bundled-library LD_LIBRARY_PATH values from leaking into build commands; merged in snapcore/snapcraft#1635 as da9181487. | |
| #1635 snap: remove leaking LD_LIBRARY_PATH | snapcraft | merged | Merged as da9181487: PR #1635 removed LD_LIBRARY_PATH leakage from snapcraft-classic, fixing LP #1723208 and preventing breakage on hosts such as Trusty. | |
| #2128 project_loader: stop setting LD_LIBRARY_PATH | snapcraft | closed | Closed unmerged in #2128 as unnecessary after the last known Trusty classic-snap user moved to Xenial; no code was changed. | |
| #1665165 classic snaps fail to build in launchpad in archs other than amd64 | snapcraft (launchpad) | closed | Classic non-amd64 Launchpad builds were fixed by snapcraft PR #1170 (commit b19e9cf68), correcting relative core dynamic-linker symlink resolution. | |
| #1665081 building a classic snap does'nt remove /snap/core/current | snapcraft (launchpad) | closed | Closed without a code fix; the maintainer clarified that SNAPCRAFT_SETUP_CLASSIC=1 is only intended for CI use. | |
| #1752964 Snapcraft snap broken on trusty | snapcraft (launchpad) | closed | Snapcraft 2.39.2 snap failed on Trusty: mksquashfs couldn't find liblz4.so.1 because ELF rpaths weren't set. Fixed by snapcore/snapcraft#1988 (commit 17f1f8c2f), which only sets rpaths to libs of the same arch; verified via edge/1752964-fix-trusty channel. | |
| #1752957 Building classic snap without core snap installed succeeds, but creates snap that doesn't run | snapcraft (launchpad) | open | Legacy Snapcraft 2.x classic builds could emit a non-running snap when core was absent; the affected base and implementation are now obsolete. | |
| #1992557 snapcraft remote-build snapcraft.yaml validation too strict | snapcraft (launchpad) | closed | Strict validation in snapcraft remote-build rejected empty LD_LIBRARY_PATH for core22 snaps. Resolved by the new remote builder, which fixes the legacy core18/20 implementation bug. | |
| #1668424 binutils-related issues with classic snap installed on 14.04 | snapcraft (launchpad) | open | Classic snap built on xenial exposed a static lib whose objects use R_X86_64_REX_GOTPCRELX relocations that trusty's ld can't parse; reporter flagged it as probably not snapcraft-fixable, no action since 2017. |