My guess is it means this sort of recent windows feature of showing a QR code on how to search for the issue you’re experiencing
Having a QR code with a link to the error code or at least a way to search it is an excellent UX thing, especially for those who are less accustomed to dealing with Linux kernel panics
See the comments in response to mine on how this might look
Well the QR code part hasn’t even been submitted to the maintainers yet AFAIK, so there’s still time to change, and I’m sure it’ll be configurable so you either get a stack trace or a QR code.
I like it when my crashes come with a plain text explanation of what caused the crash. It just seems simpler to me than having to deal with some barcode fuckery.
One doesn’t exclude the other. And if you really hate QR codes that much I’m sure there will be a flag or you can recompile the kernel without this, it’s Linux after all
This is my favorite part.
My guess is it means this sort of recent windows feature of showing a QR code on how to search for the issue you’re experiencing
Having a QR code with a link to the error code or at least a way to search it is an excellent UX thing, especially for those who are less accustomed to dealing with Linux kernel panics
See the comments in response to mine on how this might look
I love your specific example screenshot
“Hey is this Microsoft support? Yeah, err, so I’ve got this MANUALLY_INITIATED_CRASH error, can you help?”
“Have you tried… Not initiating…a crash…?”
Lol just what I found first with a quick google, but it is funny
It doesn’t have a QR code in it’s current state AFAIK, but I believe the guy wants to add one eventually. Here’s what it might look like:
Also from the commits it looks like the colours are configurable at compile time (white on black default), and that exclamation Tux is already there.
Nah, that only handles boot errors, not kernel panics.
Ah thanks for the clarification, that’s pretty neat, I’ll update my comment
For the curious, it’s one big long url that encodes some OS data and the end of the kernel ring buffer.
Pretty neat, but I’d rather have it on screen too.
deleted by creator
Well the QR code part hasn’t even been submitted to the maintainers yet AFAIK, so there’s still time to change, and I’m sure it’ll be configurable so you either get a stack trace or a QR code.
I like it when my crashes come with a plain text explanation of what caused the crash. It just seems simpler to me than having to deal with some barcode fuckery.
One doesn’t exclude the other. And if you really hate QR codes that much I’m sure there will be a flag or you can recompile the kernel without this, it’s Linux after all