- Login as a user.
- Delete the user while still logged in
- Run command
You should get a message “you don’t exist, go away”
Not sure if that one is still around but I know one person who ran a script with “deluser $USER” and it ate root resulting in fun messages like that
I think I’ll just take your word for it.
Easy to try in a virtual machine with snapshot. Or use a filesystem snapshot
the famous “This incident will be reported” error was briefly removed last year before being replaced with a less ominous version.
While it was funny, it probably is for the best. Especially if a kid uses the system it might legitimately scare the shit out of them lol
I wouldn’t be surprised if a kid thought the police was gonna break in now
I noticed this, got so sad. It was one of the funniest ones for me. First time I got it I kinda laughed.
IMHO, that doesn’t sound any less ominous
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.
deleted by creator
How could you not include the classic printer lp0 on fire!
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
That was a fun read, thank you.
Good chance that could be fire
I love that the Wikipedia article has a section on Printer flammability :D
There’s also the naughty programmer getting spanked by EFL
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
The third one is new to me. “Congratulations” - that’s fucking hilarious.
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. 😅
Top one has to be my favorite. I’ve gotten it once. I did manage to get it to boot and fixed it but at the time I was just like: “oh…well shit”
do you remember what causes it? and what was the fix?
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.
BEST os ever, proof is right here.
Where lp0 on fire?
That’s some bare metal system breakage I can get behind
deleted by creator
Just tell me actual errors like a professional OS would.
Professional OS:
Ah, my Windows (dual booted and hardly ever used) desktop wallpaper. 😅
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.
IIRC the person who added that didn’t add it as a joke but as a genuine thing.
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”
Unfortunately, the SEO hellscape means every single windows error just yield a “Try to install our patcher tool” article.
How about both?
But in the latter case you don’t have to google. You already know what the problem is. The file it’s looking for is missing. So I’d rather have that kind of message than just an error code.
You definitely have to
go to the Arch wikiGoogle in some cases. Knowing what the problem is and knowing how to fix it are sometimes seemingly unrelated. E.g., “Could not open foo.yaml: File not found” could actually mean “Some non-obvious file in the tarball was not set executable, which screwed up this one script that ran another script but couldn’t run some other script which didn’t give an error message, which made another script think the file had already been copied”. If you can find someone out there who ran into exactly the same problem, you can find a solution to it, but if none of the words in your error message are completely unique, it can be very hard to find someone with the same problem.
Personally, I do find these add additional information:
- That this really is a rather serious problem.
- Entropy, to make it easier to find others with the same problem.
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
ssh!
LI
The first one sent shivers fown my spine.
Second one just reminded me of Linus’ challenge.
The third one gave me quite a laugh.
I let out a chuckle on the last one
