Describe the bug
In ZenNotes-2.57.0-linux-x64.tar.gz, resources/terminal/ is drwx------ root:root; the files inside (zn, manifest.json, LICENSE) are world-readable. The AUR PKGBUILD copies it with cp -a, so the app, running as a normal user, cannot read manifest.json. zn keeps using the legacy Node CLI instead of Go zn 0.4.1.
To reproduce
- Install
zennotes-bin 2.57.0-1 from the AUR.
- Open Settings → CLI.
Expected
zn is Go 0.4.1.
Actual
Settings → CLI shows "The bundled terminal manifest is invalid. Your existing CLI remains available." and zn --version prints zn v2.57.0. The message is misleading: prepare() returns null only for ENOENT, so the EACCES is reported as an invalid manifest.
Workaround
sudo chmod 755 /opt/zennotes-bin/resources/terminal, then restart the app. Settings → CLI then reports 0.4.1.
Environment
ZenNotes 2.57.0 (desktop)
OS: Omarchy (kernel 7.2.5-4-omarchy), x64
Engine: Electron 41.10.7 (Chromium 146.0.7680.216, Node 24.18.0)
Install: package manager or tarball (updates are reported, not installed)
Describe the bug
In
ZenNotes-2.57.0-linux-x64.tar.gz,resources/terminal/isdrwx------ root:root; the files inside (zn,manifest.json,LICENSE) are world-readable. The AUR PKGBUILD copies it withcp -a, so the app, running as a normal user, cannot readmanifest.json.znkeeps using the legacy Node CLI instead of Gozn0.4.1.To reproduce
zennotes-bin 2.57.0-1from the AUR.Expected
znis Go 0.4.1.Actual
Settings → CLI shows "The bundled terminal manifest is invalid. Your existing CLI remains available." and
zn --versionprintszn v2.57.0. The message is misleading:prepare()returns null only forENOENT, so theEACCESis reported as an invalid manifest.Workaround
sudo chmod 755 /opt/zennotes-bin/resources/terminal, then restart the app. Settings → CLI then reports 0.4.1.Environment