• Avid Amoeba
    link
    fedilink
    401 month ago
    • Preparations for a kernel panic screen as sort of like a Windows Blue Screen of Death (BSoD).

    This is my favorite part.

    • @kautau@lemmy.world
      link
      fedilink
      27
      edit-2
      1 month 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

      See the comments in response to mine on how this might look

      • @9point6@lemmy.world
        link
        fedilink
        31
        edit-2
        1 month 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…?”

      • @SteveTech@programming.dev
        link
        fedilink
        English
        18
        edit-2
        1 month 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.

        • Butt Pirate
          link
          fedilink
          01 month ago

          Man I really hope they kill that. Its extremely user unfriendly, especially in Microsoft’s configuration where they show the bsod for 0.2 seconds for rebooting.

          • @SteveTech@programming.dev
            link
            fedilink
            English
            11 month ago

            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.

      • @AnUnusualRelic@lemmy.world
        link
        fedilink
        6
        edit-2
        1 month 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
          91 month 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