Where lp0 on fire?
the famous “This incident will be reported” error was briefly removed last year before being replaced with a less ominous version.
I noticed this, got so sad. It was one of the funniest ones for me. First time I got it I kinda laughed.
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
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
I’ll never forget this one lmao
I love Linux but this is a huge pain point for me with Linux. Just tell me actual errors like a professional OS would.
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”
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.
Unfortunately, the SEO hellscape means every single windows error just yield a “Try to install our patcher tool” article.
How about both?
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
ssh!
Just tell me actual errors like a professional OS would.
Professional OS:
Ah, my Windows (dual booted and hardly ever used) desktop wallpaper. 😅
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.
score 10 or sacrifice childis actually just a MtG card, how did that get in thereI can’t imagine Linux users and mtg players being mutually exclusive lol
We’re not
Gah and I spent all that money on a garage foundation.
php has a log message about killing children, i think i saw once
BEST os ever, proof is right here.
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. 😅
LI
That’s some bare metal system breakage I can get behind
What was that? I couldn’t hear you over my triggered anxiety.
Be back later, gonna go generate more recovery media.
linux susadmin can’t even find the print screen button smdh head /s
You don’t see most of these errors in situations where screenshots are possible
I’ve been messing around with Linux VMs and have gotten kernel panic a lot lately. Always gives me a chuckle
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.
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
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.
They need to noobify that prompt further, something like “Yes, break my system!”. Even Linus wouldn’t fall for that (I hope)!
Or have them answer a few linux related questions
*They will claim it was Linus fault
Which one?
sex tips
deleted by creator
By “people” you mean Linus Sex Tips
Linux tech slips
For legal reasons I cannot confirm nor deny such allegations at this time.
Linux Tech Tips channel when?
With Emily as the main Host (Comment section goes BRRRRRRR! Don’t want to be a mod there xD)
For anyone confused with this comment thread https://youtu.be/0506yDSgU7M?t=597
Your system ate a SPARC! Gah
What does this mean? Does it has something to do with… I don’t know, the Sun SPARC CPUs?
deleted by creator
Okay, but what is sparc and pa-risc?
OMG I feel old.
Also regret the money I spent buying Sun stock in the late 90s.
As someone who was Sun Certified 5.7.1 to version 10, I feel this way too hard as well.
nice
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.
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.
