I'm not sure if this is an OS issue or a Rust issue, but I'm having trouble getting Rust installed. I just get a Segmentation Fault.

My first install attempt was using the command from the website:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

It seems to have run fine, but rustc fails:

rustc -vV
Segmentation fault (core dumped)

It doesn't matter what options I try with rustc, but it fails.

rustc --version
fish: Job 1, 'rustc --version' terminated by signal SIGSEGV (Address boundary error)

rustup seems to work fine:

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 `(error reading rustc version)`

I also tried installing with rustup. I tried both the stable and the nightly.

I'm running on Garuda linux, so I tried using octopi to install the rust package and then the rustup package.

I thought I saw somewhere that starfish might be interfering so I tried to run it in a new bash terminal with the same results.

I just tried checking my path. It looks correct, and both versions fail. Then, I noticed that both are linked to rustup. Is it supposed to be like that?

>which rustc
/home/skp/.cargo/bin/rustc

>rustc -vV
fish: Job 1, 'rustc -vV' terminated by signal SIGSEGV (Address boundary error)

>/usr/bin/rustc -vV
fish: Job 1, '/usr/bin/rustc -vV' terminated by signal SIGSEGV (Address boundary error)

>ls -l /usr/bin/rustc
lrwxrwxrwx - root  2 Jun 04:45  /usr/bin/rustc -> /usr/bin/rustup

>ls -l /home/skp/.cargo/bin/rustc
lrwxrwxrwx - skp 15 Jun 22:24  /home/skp/.cargo/bin/rustc -> rustup

Almost all the search results for this error turns up people struggling with their programs causing memory errors. Since I can't even get a version number from rustc, I'm way before that point. I have a feeling it's a dependency that I'm missing, but I'm not sure where to go from here. Should I take this to a Garuda Linux forum, or is this an issue with rustc? Or, am I just missing something obvious.

4 posts - 2 participants

Read full topic