error: failed to install component: 'cargo-x86_64-unknown-linux-gnu', detected conflict: 'bin/cargo'

[Sfinx]

Verification

• I searched for recent similar issues at https://github.com/rust-lang/rustup/issues?q=is%3Aissue+is%3Aopen%2Cclosed and found no duplicates.
• I am on the latest version of Rustup according to https://github.com/rust-lang/rustup/tags and am still able to reproduce my issue.

Problem

rustup upgrade
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
info: latest update on 2025-08-30, rust version 1.91.0-nightly (fe5536432 2025-08-29)
info: downloading component 'cargo'
info: downloading component 'clippy'
info: downloading component 'rust-docs'
info: downloading component 'rust-src'
info: downloading component 'rust-std'
 28.0 MiB /  28.0 MiB (100 %)  27.3 MiB/s in  1s         
info: downloading component 'rustc'
 79.4 MiB /  79.4 MiB (100 %)  16.1 MiB/s in  4s         
info: downloading component 'rustfmt'
info: removing previous version of component 'cargo'
warn: during uninstall component cargo was not found
info: removing previous version of component 'clippy'
info: removing previous version of component 'rust-docs'
info: removing previous version of component 'rust-src'
info: removing previous version of component 'rust-std'
info: removing previous version of component 'rustc'
info: removing previous version of component 'rustfmt'
info: installing component 'cargo'
info: rolling back changes
error: failed to install component: 'cargo-x86_64-unknown-linux-gnu', detected conflict: 'bin/cargo'
info: checking for self-update

       stable-x86_64-unknown-linux-gnu unchanged - rustc 1.89.0 (29483883e 2025-08-04)
  nightly-x86_64-unknown-linux-gnu update failed - rustc 1.91.0-nightly (6ba0ce409 2025-08-21)

info: cleaning up downloads & tmp directories

removing/adding/uninstalling/installing cargo package do not help

Steps

1. try to 'rustup update' from rustc 1.91.0-nightly (6ba0ce409 2025-08-21)

Possible Solution(s)

No response

Notes

No response

Rustup version

rustup 1.28.2 (e4f3ad6f8 2025-04-28)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.89.0 (29483883e 2025-08-04)`

Installed toolchains

Default host: x86_64-unknown-linux-gnu
rustup home:  /opt/rust

installed toolchains
--------------------
stable-x86_64-unknown-linux-gnu (active, default)
nightly-x86_64-unknown-linux-gnu

active toolchain
----------------
name: stable-x86_64-unknown-linux-gnu
active because: it's the default toolchain
installed targets:
  x86_64-unknown-linux-gnu

OS version

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04.3 LTS"
PRETTY_NAME="Ubuntu 24.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.3 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

[rami3l]

Thanks for the report!

This is quite unfortunate, but I believe you are hitting #988.

If that is the case, I suggest that this issue be closed in favor of it.

PS: I have always wanted to close that issue as much as everyone else does, but it will take some non-trivial effort to land the fix, so thanks for your comprehension as we find a way through it 🙏
#4464 (comment)

You seem to be running multiple rustup instances at the same time, and rustup is not designed for such scenarios, although we wish to support this case in the future.

As a workaround, please try to uninstall and reinstall the toolchain in question.

Please feel free to let me know if you have any remaining concerns 🙏

[Sfinx]

First, the rustup process is running as only one - I do not see any concurrency here, except the bad internal design. Second, it is still unknown for me how to fix this.

[Sfinx]

As I see - closing the real issue from your side - is the real problem solution. No issue - no problem