Skip to content

Linux install fails when $HOME is a root-owned symlink under /home (activation transaction I/O failed) #2306

Open

Description

@BumaldaOverTheWater94

Summary

install fails on Linux when $HOME is a root-owned symlink under /home (for example /home/alice -> /local/home/alice, common on corporate/managed dev hosts):

error: failed to stage install candidate: activation transaction I/O failed

Cause

activation_posix_walk_path() only resolves trusted aliases when /tmp, /var or /home is itself a symlink (the #2175 fix). When /home is a real directory and the per-user entry /home/<user> is the root-owned symlink, the O_NOFOLLOW walk in activation_directory_secure() rejects it and reports the generic I/O error.

Repro

  • /home is a real root-owned dir, /home/alice is a root-owned symlink to /local/home/alice
  • HOME=/home/alice, v0.11.0
  • curl -fsSL .../install.sh | bash

Workaround

bash -s -- --dir "$(realpath ~/.local/bin)"

Suggested fix

On Linux, also resolve a root-owned symlink at /home/<name> when its target is a root- or user-owned directory. Arbitrary user-owned symlinks stay rejected.

Activity

  1. added 2 commits that reference this issue on Sep 28, 2026
    7aeb023
    42971f2
  2. DeusData commented on Oct 19, 2026

    @DeusData
    Owner

    Thank you for the managed-home symlink layout and exact activation error. I have classified this as an installer integration bug report. Any expansion of trusted path handling needs review; I cannot confirm the proposed trust rule or workaround from this triage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingeditor/integrationEditor compatibility and CLI integration

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions