gzip exec format error under WSL1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gzip |
New
|
Unknown
|
|||
gzip (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
Unassigned | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* Optimization features included in jammy cause atypical alignment of LOAD ELF sections. This in turn causes failure to execute binaries on WSL1. Upstream have since integrated the optimization features included in jammy, but also reverted alignment to a previously used one. This also results in working binary under WSL1.
* Cherry-pick upstream applied revert to alignment to resolve running gzip under WSL1.
[Test Plan]
* Use powershell to set default WSL version to 1
* Deploy WSL1, unpack and use updated gzip package
* gzip --version should execute correctly under WSL 1
[Where problems could occur]
* I cannot tell why performance improvement patches introduced alignment change, and if revert of the alignment change affects the performance. Note that this change aligns the codebase closer to what kinetic & upstream now are.
[Other Info]
* This bug fix is upstream commit https:/
---
gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable.
bash: /usr/bin/gzip: cannot execute binary file: Exec format error
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gzip 1.10-4ubuntu3
ProcVersionSign
Uname: Linux 4.4.0-19041-
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckR
Date: Tue Mar 29 06:40:33 2022
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
LANG=pl_PL.UTF-8
SHELL=
SourcePackage: gzip
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in gzip: | |
status: | Unknown → New |
description: | updated |
Changed in gzip (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in gzip (Ubuntu Kinetic): | |
status: | Confirmed → Fix Released |
Changed in gzip (Ubuntu Jammy): | |
importance: | Undecided → High |
Status changed to 'Confirmed' because the bug affects multiple users.