Hm, unfortunately nothing obvious. And your last boot ended with a crash?
Nevertheless you could try running a Memtest (this can take a while) - it will check whether any of your RAM modules are faulty: https://www.memtest.org/
Hm, unfortunately nothing obvious. And your last boot ended with a crash?
Nevertheless you could try running a Memtest (this can take a while) - it will check whether any of your RAM modules are faulty: https://www.memtest.org/
That’s unfortunately a bit cut off. Could you run this again with the following command? sudo journalctl -xeb -1 --no-pager
Sure, though the immutable design makes it very safe to touch these things.
OP, do this - it’s the best way to figure out what’s happening. It could be any number of issues, e.g. faulty RAM. With the output of the command above people can tell you what to test for.
As such we had to install openrgb the usual system-wide way, with rpm-ostree in terminal - something I was hoping he would never had to do.
There is nothing wrong with doing that if there’s no better option. You’re not losing out on anything.
What? No I’m not. Using a memory-safe implementation of sudo doesn’t take any power away from the user, how does that make sense?
sudo-rs doesn’t have anything to do with run0. Please take your pills grandpa, we’re worried about you.
Edit: in case you’re actually an older person, the latter part wasn’t meant as a swipe (just saw your pfp). In that case, sorry!
Oh, you should have mentioned that - or do you think that fsck is Memtest? It is not.