APM fails to use 7za during Install

[LunatiK-ExpiX]

Issue

Fails to Install due to an error with 7za

Log

[2025-07-31 00:39:24.773] [debug] {
node: '20.18.3',
acorn: '8.14.0',
ada: '2.9.2',
ares: '1.34.4',
base64: '0.5.2',
brotli: '1.0.9',
cjs_module_lexer: '1.4.1',
cldr: '44.1',
icu: '74.2',
llhttp: '8.1.2',
modules: '132',
napi: '9',
nghttp2: '1.61.0',
openssl: '0.0.0',
simdutf: '5.6.4',
tz: '2024b',
undici: '6.21.1',
unicode: '15.1',
uv: '1.46.0',
uvwasi: '0.0.21',
v8: '13.2.152.41-electron.0',
zlib: '1.3.0.1-motley',
electron: '34.3.4',
chrome: '132.0.6834.210'
}
[2025-07-31 00:41:18.752] [error] Unhandled Error: spawn /home/luna/apm/.webpack/renderer/main_window/native_modules/linux/x64/7za EACCES
at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
at onErrorNT (node:internal/child_process:483:16)
at processTicksAndRejections (node:internal/process/task_queues:82:21)

Other info

Unfortunately, I lack any knowledge of JavaScript or Electron, so I can't provide any information on this

[hal-shu-sato]

Thanks for the report, and sorry for the long silence.

The EACCES means the bundled 7za binary lost its executable bit, so spawn could not run it. This should be fixed in v3.13.0: apm now sets the executable bit on 7za before spawning it (3d38b57).

Two things worth knowing if you retry:

• The path in your log (.webpack/renderer/main_window/native_modules/linux/x64/7za) no longer exists. apm has since moved from webpack to Vite, and 7za now resolves from node_modules/7zip-bin/linux/x64/7za (inside app.asar.unpacked for packaged builds).
• The underlying cause is environment-dependent: the executable bit can be lost when the package manager extracts 7zip-bin from its cache. We reproduced exactly that on a development machine while investigating this issue, so the fix guards against it rather than assuming it cannot happen.

Could you try v3.13.0 or later and let us know whether the install works?

One more thing that would help: your log path was /home/luna/apm/.webpack/..., which looks like you were running apm from a source checkout rather than an installed package. Could you confirm how you launched it? That tells us whether the fix covers your case, since the packaged and from-source paths differ.

---

Investigation and drafting done with Claude Code.