Jesus, that rustup folder is HUGE

My 2 cents. I started with Bazzite and switched to Fedora after some things broke. Fedora works for my use case and I don’t see any reason to switch further. Even upgrading from 40 to 41 worked without hickups.

Looks like a sad and overworked old guy

It only doesn’t seem fair because those two aren’t hiding it.

Is there any write-up for the recent events around the kernel and Rust? Glancing over recent posts, it seems like new devs want to push Rust, but older maintainers don’t want to deal with it. Why do people love Rust so much? Is it just a loud minority or does it in fact offer substancial gains and safety over existing C code? Lqstly, can they simply fork the kernel and try their own thing? E.g. do a branch as a proof of concept and therefore convince them to migrate?

After seeing the priginal I was hoping someone would make this kind of shitpost!

Yesterday I came back to my issue and decided to try LazyVim just to see what would happen since it comes with Mason. It worked, first try. Both on Linux and Windows. I seriously have no damn clue why it wasn’t working standalone… It has to be something with Plug

No, it works just fine. It finds Mason and does the check ehich returns OK results except the add-ons for specific languages (e.g. it deteckts python3, complains about misisng rails etc.)

No, no conflict whatsoever. Just an error mesaage that the command is not recognized/present. Telescope works just fine. The colorscheme as well.

If you still have Windows i.e. you dual boot, then Windows might have taken control over the HDD. A similar thing happened to me. If that is your case, you need to go back into Winodws, open the command prompt and type in shutdown /s /f /t 0. This is caused by having fastboot enabled which makes Windows never fully shutdown when powered off.

That was the problem. Stupid me…

You are right. I messed it up adn didn’t put $ infront of PATH… Luckily I found an stackoverflow post with a similar issue and it suggested setting PATH to the default PATH=/usr/bin:/usr/sbin that would alowe using commands again and it worked.

We might as well bring some pitchforks and torches.

Fastboot was never enabled to begin with :-/

Ok, I foxed it! I looked around in the log of which I mostly understood nothing, but then I came acress the section where the kernel/shstemd mounts the drives and the error it spits out. Googling it gave me an arch forum post with the identical problem. Windows didn’t shutdown correvtly the last time I used it and did something to the partition table. I’ll update my post wiy the solution.

Tnx. I will report back tonight when I get around checking.

I’ll check the BIOS stuff tonight.

As for the sata port, the new drive was connected to a different one so it can’t be it. I did a drive health check and all seemed well and good.

I touhgt the same, but connecting a new drive and getting the same “read-only file system” error is really strange. I used the other drive for qbittorrent and it worked flawlessly before the update. I haven’t come around to try any of the suggestions yet. I’ll report back tonight.

I checked fstab and it’s the same from day one. I tired adding stuff to it and shuffeling parameters around (like phtting rw,exec last), but it did nothing.

I’ll give ut a shot first before the other suggestions. Tnx