The Blue Screen of Death is Coming to Linux..

44 thoughts on “The Blue Screen of Death is Coming to Linux..”

• Are you ready to experience the BSOD? =)

• Damnit it's more Poettering disease.

• "More KDE plug-ins and themes coming soon!"

• When does Linux ever crash? The only time I've had that issue was with hardware failure

• Can't we have a Guru Meditation screen instead?

• Systemd 255 was already around since Christmas of the last year (2023).

• "Guru Meditation" would have been a far more fitting name for a system like Linux, imho. 😂

• I'm always excited when someone thinks of a way to make Linux more user friendly and contributes that to the project, however, from my perspective, Linux already technically has these type of Kernel panic error messages, only problem with them is they are viewable via CLI only, meaning NO GUI SPLASH SCREEN, the fact that they're going to add this is great news, if they customized it per main branch distro would be even better (a unique one for Debian, Ubuntu, Arch, Fedora, RHEL, Manjaro, OpenSUSE, Slackware, etc.)

• I still prefer the Amiga's Guru Meditation Numbers…

• DRM coming to Linux! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!! NO!!

• kernel panic bsod lmfao

• Ofc it is from SystemD

• i love systemd(eez-nuts)

• I really like the idea of a BSOD. I had some errors in the past where I wasnt sure about linux errors and alike. I often didn't know which logs to look at or what to do and just reinstalled the whole system (not now anymore though). But this, hopefully, will help alot fir new users to get help much faster and more precisely. Thank you for the video about that and the very clean and good explanation of it. Really much appreciated ❤

• Cowsay bluescreen or bust

• i find the idea interesting, although i have never really encountered any kernel problems (yet) and i'm using a different init system
  it could/will help alot of linux newbies to find solutions easily, since they most likely do not know/use jornalctl log

• Does it really have to be a Microsoft color? Why can’t we just get a black screen, with Tux in the upper corner?

• I like the idea and literaly the one change which I would've proposed is actually to add ASCII Symbol of Distro Icon with exclamation mark to differentiate system stack error and hardware one (which might have a Tux with exclamation mark) and add of course then field «Type: » and put there something like «System-caused» or «Hardware-caused»

• Linux is slowly becomming Systemd/Linux

• Sure it’ll be added to Linux, but you’ll never actually see it.

• I am all for more error messages so long as they are useful. I want to know what I did or didn't do to screw up and cause issues. The error message on linux mint cinnamon when I ran out of disk space gave me no indication of what was wrong, and wouldn't always bring up an error when I was trying to save a game, it would simply delete my entire save folder for that game. It happened to multiple games before I realized it was a storage issue.

• Given the Linux Kernel is getting re-implemented in the Rust programming language, they will need it.

• I rather not include a bsod. I dont want my Linux system to remind me of what I left. I am cool with the logs.

• only on linux will you find people who have arguments against a screen providing useful information about why your entire device just crashed.
  i will never understand how people can even have a discussion or arguments against it if objectively you want to get as many useful information as you can and if you cant boot the PC up anymore having a secure environment with a screen that tells you exactly what problem you need to fix is something everyone should be looking forward to instead of arguing against.

• didn't; ubuntu had something like this? I swear I have seen a computer with dead eyes with a message under it

• My answer is, why do we need one? I might get it as a like an ultimate fail safe, literally everything is crashed that the operation needs to function. But isn't that like the entire point of linux its stable and only typically partially crashes? Allowing is to be more resilient in data retention.

  As long as it's not being triggered during these partial crash cases I think it would be perfectly fine.

• Having BSOD on Systemd would be the reason why I stick with OpenRC permanently. All I need is a few init systems running and have control of them.

• This seems to be a bad joke. We don't need and we don't want to mimic Windows in this anoying behavoir…

• 2:27 "Restart your computer" is the exact reason why people hate the Windows BSOD. I would rather have a stack dump where I can map the address back to the System.map file and addr2line to locate and troubleshoot the source code.

• SystemD != Linux
  It was made by Microsoft Engineers working at Fedora.

• The modern BSOD is actually Azure and isn't a true blue like it used to be.

• should be red imo

• I hope any BSOD on linux is more useful to the user than just System Error or There was a problem. at least tell us what part of system had the issue or what program caused the crash.

• WTF

• I hope they make it at least useful, the main problem with Windows' BSOD is that if you got a fast PC, that message is going to be on screen for maybe two seconds and then just automatically reboot leaving you guessing WTF just happened.
  You barely have enough time to react to it, let alone scan a QR code (not that the message or QR code are any helpful anyway)

• What I like: It simplifies the error and troubleshooting for less technical people.

  What I don't like: It's blue. Black background is good and I also like the green text.

  What I don't care: Do we really read what's on the screen? Linux survived this long without it which is a testament to how unimportant it is. However its one of the little things I can appreciate.

• I dunno…. It's been about 20+ years since I've actually encountered a kernel panic on a Linux kernel.

• fuck systemd now, Stop doing too much just be init system.

• Haven't seen a blue screen since 1998. They are usually low level hardware issues. If the system components are carefully selected you can live a lifetime without seeing one.

• I had 3 times in my live having bsod on linux.
  The first was about power failure. (Grub error)
  The second was about driver compatibility (via c3)
  The third was about a wrong comand (I used USB stick to repair the disk)
  Overall, linux is easy to repair.

• Windows: welcome to the club bro! 😁

• Been using Linux for years and I defiantly would appropriate a feature like this. As it stands, when Linux stops working, it just stops and your entire system will sit there frozen forever until you hold down the power button down. I know Linux on servers is rock solid but Linux on the desktop might as well be an entirely different animal.

• video on how to rice you BSOD in arch coming soon…

• it would be awesome if they externalize a visual editing api only for the screen visual we could like put the "You died" of dark souls or the "busted" of GTA screen kkkkk

Comments are closed.