Installer refuses an older Linux Home whose files are group-writable or owned by root #516

Problem

On a Linux or Jetson computer that already has an older ElastOS install, the 2.0.0 installer can stop before it changes anything:

Error: installation file is unsafe: /home/<user>/.local/bin/elastos is accessible to other users; fix with: chmod go-w '/home/<user>/.local/bin/elastos'
Error: This installation was not changed

After that file is fixed it names the next one (for example ~/.local/share/elastos/components.json). If chmod answers Operation not permitted, some ElastOS files belong to root, usually from an earlier install run with sudo.

Seen 2 Nov 2026 on a Jetson whose Home was created by a March 2026 release. New installs are not affected: the installer now creates its files owner-only, and fresh installs on default Ubuntu settings pass.

Workaround

Run as the user who owns the Home, not as root:

sudo chown -R "$(id -un)": ~/.local/share/elastos ~/.local/bin/elastos
chmod -R go-w ~/.local/share/elastos ~/.local/bin/elastos
curl -fsSL https://elastos.elacitylabs.com/install.sh | bash

sudo is only for giving the files back to you. Do not delete ~/.local/share/elastos: it holds this Home's identity and keys.

Fix (2.0.1)

The installer should repair group/other write on files and folders that are its own and owned by the user, and name root-owned ones with the one chown command, instead of refusing file by file. Check: install_transaction.rs check_file / check_directory_mode.