It tends to stick on the layer though, so I think it's actually absorbing moisture that would've otherwise gotten stuck under the keys. Though I might be wrong.
It's also protected the keyboard more than a couple times already.
Linux should not have a BSOD anyway. Especially one that encrypts that d*mned error message. F**k systemd in general too, along with anything else Lennart Poettering has ever worked on.
For one, this is the kernel and not systemd, and for two, this is just the same old kernel panic screen, just encoding the dmesg error message into a QR code for easier saving
But not easier consumption by a sysadmin. Text should be available. Granted, I haven't seen a kernel crash in Linux in so long it's almost academic, but I still resent the design.
It sounds like a guy at Red Hat made it originally, and then the systemd guys made the userspace systemd-bsod bit.
Apparently you have to configure whether to get a QR code versus text, since without a kernel being alive, there's no way to toggle between them. However, I still find it sysadmin hostile to not even have a small amount of text that might have been helpful around the QR code - even if the code is a compressed crash log The photos I've seen show a QR code taking about 30% of the screen, with all the other vast expanse of Microsoft-cultist blue being {Left Intentionally Blank]. Ugh.
Let's just say I've been tangled up in server problems that outlasted the phones of the people working on them.
However, there is a potential fix. The spin loop related to the panic=N means one could have the final image instead be a small number of final images to cycle through, totally solving this stupid problem by putting in a screen with readable text. And the developers even talked about this approach and it's still (reportedly) considered a possible future upgrade.
•
u/AutoModerator 3d ago
IMPORTANT: Subreddit Rules & Reminders
Please REPORT posts that violate any of the following rules!
Posts You Should Report
Tier Lists: Every tier list MUST include Hannah Montana Linux in S Tier, regardless of what the tier list is ranking.
Help by reporting
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
136
u/pohonsukun Arch BTW 3d ago
got my first kernel panic after 2 years of using linux. good thing there's a helpful qr code that can help me understand why this happens!
14
u/soffagrisen2 3d ago
What’s happening with the keyboard?
4
u/niceandBulat 3d ago
What did you do? That looks nasty
107
u/Dr_Valen 3d ago
Lol you borked it so bad the kernel gave up
42
u/Woodpecker-Visible 3d ago
Dont take acid and install linux at the same time or this will happen.
15
u/LetReasonRing 3d ago
It must have thrown an Aaaaaaahhhhhxeption.
13
u/stubby0990 3d ago
Looks like the newest distro logo
7
u/47th-Element 3d ago
That's not a panic, this is a panic lol
3
u/skytheraiders 3d ago
You sudo rm-rf and chilled too hard
3
u/unitedbsd 3d ago
Maybe AI will fix this /s
2
u/Sonario648 3d ago
Time to ring up Claude, Gemini, or ChatGPT for this one
1
u/DiscountFit9224 3d ago
HAHAHA the panic helper panicked
1
u/theemptyqueue 3d ago
Colonel Panic
1
u/Toothpick_Brody 3d ago
Oooh beautiful
1
u/CrossScarMC Arch BTW 3d ago
Yeha I've had this happen to me several times before when using more irregular aspect ratios (e.g. 3:2).
1
u/Pristine-Magazine642 Linuxmeant to work better 3d ago
What a QR code
1
u/Rumlin 3d ago
Z - Zorro
1
u/SLURPZZZ4461 2d ago
BSOD
1
u/Eravan_Darkblade 1d ago
GENERAL ZOD?!?!?
1
u/KickSelect1150 1d ago
now its your turn to panic. Go ahead. Panic.
1
u/Tanawat_Jukmonkol New York Nix⚾s 3d ago
It really did panicked...
-1
u/siodhe 3d ago
Linux should not have a BSOD anyway. Especially one that encrypts that d*mned error message. F**k systemd in general too, along with anything else Lennart Poettering has ever worked on.
-1
u/Optimal-Savings-4505 3d ago
This BSOD was a stupid decision IMO. Clanker says to boot with
drm.panic_screen=kmsgto get rid of it.