People would read the second message, type the yes prompt, break their system. But still claim that it was linux's fault, and that the OS doesn't work.
Message two can also be caused by packages (or rather, package creators) with delusions of grandeur that only think that the system will stop working without them, so they rig things to threaten to uninstall the system.
Or else someone has created too heavy a dependency on something that ought to be removable, but isn't thanks to malice or incompetence (or both).
We still mock Microsoft for putting too heavy a dependency (or at least removal FUD) on whatever web browser they bundle with their OSes (first IE, now Edge), and here we might have a package creator trying the same damn thing.
Honestly I once did this to my desktop environment because I saw a huge list of packages and ignored it because I thought they were packages that could be upgraded, not that it was going to uninstall my fucking desktop lol
My local deluser checks if the user has any active process. I tried deleting all of the data by hand, but the process is still assigned to a user name and id.
I'm not sure if this one can error still can be replicated.
At least it answers the question whom it will be reported to. In all likelihood the administrator is me anyway, at least on my personal devices. People won't worry anymore that it will be reported to the police or, heaven forbid, to Santa Claus.
I actually got that one around 2010 on Ubuntu. The printer wasn't actually on fire. If I recall it was caused by the network attached printer losing connection during a job
EFL is an absolute crime against programmer-kind, even if the errors are, admittedly, hilarious. can assert that they are not so funny when you find them deeeeep in some god-forsaken legacy codebase that's seen more null *s than git commits lol
I got so hung up on the misspelling of "separate" that I didn't even see the "Congratulations" on first read-through. Which says more about me than about the error message, alas. 😅
If you setup your system with Chocolatey (is a package manager for Windows), removing Chocolatey will break your setup (removing all installed packages).
"It's possible I did something wrong." 🤣
Like not read the warning that said that he was about to uninstall the desktop? Or to continue only if he knew what he was doing? He also earlier liked to talk about "red flags", but somehow needing to type in "Yes, do as I say!" wasn't one to him. I'm supposed to be getting Linux tips from this guy?
I'm supposed to be getting Linux tips from this guy?
No. You're supposed to see what kind of experience someone who didn't use Linux before would have.
How could someone who has never used Linux know that he was about to nuke his system, after typing in the command that the internet told him to type in to install Steam?
What makes you think your average Windows user that is trying out Linux for the first time wouldn't have faced the same problem? I never understood why people criticized Linus for this video. After all, the video was supposed to see whether Linux is a viable alternative for Windows users (specifically gamers).
When a (typical) Linux system boots up, it first goes through an "early boot" environment that just has some basic drivers and things. The entire purpose of this environment is to find where your actual root file system is (which could theoretically be on something quite complicated, like RAID or a network file system), mount that, and then transition to the "real" system.
That error appears when something goes wrong with mounting the real file system.
I had this happen to me recently too, with an EndeavourOS live USB. In my case, it turned out to be due to a faulty flash, reflashing with Rufus fixed it.
failed to mount root filesystem on unknown-block(0,0) means the kernel started, loaded builtin drivers and drivers from the initrd, looked for the system partition to continue starting up and couldn't find it.
Maybe you removed a disk and /dev/sdb became /dev/sda or maybe you forgot to add nvme SSD support and the kernel can't read /dev/nvme0n1p1.
Or your disk let out the magic smoke and isn't detected any more.
It does tell you the actual error, though. Following it up with "Good luck" isn't particularly professional but removing it would just make the message more boring, not any clearer.
One smart thing I think Microsoft did was try to give every error message a code.
Googling for "gpoopapp E0013" is often easier and gets more precise results than having to type in "gpoopapp The file /home/bitchslayer69420/.config/share/whatever.yaml could not be opened: File not found"