• kautau@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    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

    • SteveTech@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      5 months ago

      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:

      DRM panic handler panic screenshot https://gitlab.com/kdj0c/panic_report/-/issues/1

      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.

      Looks like this is already a thing though with [systemd-bsod]

      Nah, that only handles boot errors, not kernel panics.

    • AnUnusualRelic@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      5 months ago

      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.

      • kautau@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        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

    • 9point6@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      5 months ago

      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…?”