patchelf fails on i386 vscode
Metadata
Current evaluation
i386 vscode snap build fails because patchelf 0.9 cannot patch the 32-bit ELF (virtual address space underrun); no maintainer response, unlabelled, ~7.5 years old.
Suggested action: close stale
Reason: The issue is 2873 days old with 0 comments, no labels, and no maintainer interaction. It targets the xenial (16.04) core and patchelf 0.9, both long since superseded; the error message itself points to a newer patchelf via `after: [patchelf]`/`build-snaps`, and modern snapcraft (core20/core22/core24) ships a much newer patchelf that handles 32-bit rpath patching. The affected base is no longer supported, so the specific failure is no longer reproducible in current builds.
Impact:
30
Quick Win:
13.5
Staleness:
95
Complexity:
55
Confidence:
60
Support Request:
25
Issue body
https://launchpadlibrarian.net/393792896/buildlog_snap_ubuntu_xenial_i386_8530e5f76cb0f52c411b1e115ff18a11-xenial_BUILDING.txt.gz
Seems the i386 build of vscode hasn't built for a while due to patchelf failure.
Staging electron-launch
Staging vscode
Priming electron-launch
Priming vscode
virtual address space underrun!
Failed to update '/build/vscode/prime/usr/share/code/code'. Retrying after stripping the .note.go.buildid from the elf file.
virtual address space underrun!
An attempt to patch '/build/vscode/prime/usr/share/code/code' so that it would work correctly in diverse environments was made and failed. To disable this behavior set `build-attributes: [no-patchelf]` for the part.
'/build/vscode/prime/usr/share/code/code' cannot be patched to function properly in a classic confined snap: /usr/bin/patchelf --set-interpreter /snap/core/current/lib/ld-linux.so.2 --force-rpath --set-rpath $ORIGIN/lib/:$ORIGIN/../../lib/i386-linux-gnu:$ORIGIN/../../../lib/i386-linux-gnu:$ORIGIN:/snap/core/current/usr/lib/i386-linux-gnu:/snap/core/current/lib/i386-linux-gnu /tmp/tmpk1puj0w0 failed with exit code 1.
'patchelf 0.9' may be too old. A newer version of patchelf may be required.
Try adding the `after: [patchelf]` and a `patchelf` part that would filter out files from prime `prime: [-*]` or `build-snaps: [patchelf/latest/edge]` to the failing part in your `snapcraft.yaml` to use a newer patchelf.
Build failed
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/build_snap.py", line 229, in run
self.build()
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/build_snap.py", line 218, in build
env=env)
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/build_snap.py", line 75, in run_build_command
return self.backend.run(args, env=full_env, **kwargs)
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/lxd.py", line 460, in run
subprocess.check_call(cmd, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 541, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '['lxc', 'exec', 'lp-xenial-i386', '--env', 'LANG=C.UTF-8', '--env', 'SHELL=/bin/sh', '--env', 'SNAPCRAFT_BUILD_INFO=1', '--env', 'SNAPCRAFT_IMAGE_INFO={"build_url": "https://launchpad.net/~build.snapcraft.io/+snap/8530e5f76cb0f52c411b1e115ff18a11-xenial/+build/355956"}', '--env', 'http_proxy=http://10.10.10.1:8222/', '--env', 'https_proxy=http://10.10.10.1:8222/', '--env', 'GIT_PROXY_COMMAND=/usr/local/bin/snap-git-proxy', '--', '/bin/sh', '-c', 'cd /build/vscode && linux32 snapcraft']' returned non-zero exit status 2
Revoking proxy token...
RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes --backend=lxd --series=xenial --arch=i386 SNAPBUILD-355956
Scanning for processes to kill in build SNAPBUILD-355956
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
13.5
Staleness:
95
Complexity:
55
Confidence:
60
Support Request:
25
|
close stale | i386 vscode snap build fails because patchelf 0.9 cannot patch the 32-bit ELF (virtual address space underrun); no maintainer response, unlabelled, ~7.5 years old. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Build failure on i386 due to patchelf 0.9 address space underrun during snapcraft packaging. Issue is over 7 years old with no activity. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
100
Complexity:
20
Confidence:
95
Support Request:
0
|
close stale | patchelf fails on i386 vscode build due to virtual address space underrun. Issue is 2832 days old, inactive for 2652 days, and likely obsolete due to age and architecture deprecation. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
95
Support Request:
10
|
close stale | vscode snap build fails on i386 due to patchelf 0.9 virtual address space underrun. Inactive for over 7 years with no maintainer response. Likely obsolete due to outdated toolchain and deprecated i386 support. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
25
Confidence:
90
Support Request:
10
|
close stale | Build failure on i386 Ubuntu Xenial due to patchelf virtual address space underrun. Issue is over 7 years old with no maintainer response or updates. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2045895 patchelf missing snap libdir rpath | snapcraft (launchpad) | open | patchelf inconsistent rpath for classic snaps: proposed rpath missing snap libdir that linter expects. Unlabelled, 1002 days old, no maintainer engagement. | |
| #1943963 patchelf creates unloadable non-PIE riscv64 executables | snapcraft (launchpad) | closed | Abandoned without resolution. The report details a snapcraft python3.8 execution failure on riscv64, potentially involving patchelf or seccomp, but received no comments and was closed. |