• Sekoia@lemmy.blahaj.zone
      13·
      5 months ago

      I’d suggest some kind of “press this key to view debug information” text (or make it documented but not visible, to avoid people just pressing whatever button is written on the screen)

      • Possibly linuxEnglish
        72·
        5 months ago

        Why? People aren’t idiots. If they don’t know what it means they can look it up or ask for help.

        • kitnaht@lemmy.world
          182·
          5 months ago

          People aren’t idiots. If they don’t know what it means they can look it up or ask for help.

          Flip that. People are idiots. If they don’t know what something means, they won’t look it up. Not Desktop Linux users today but, definitely normies if Linux ever comes on a system they buy in the future.

        • bastion@feddit.nl
          2·
          5 months ago

          Because for the bulk of users, unless they are power users, all they need to know is that things didn’t work.

          Things actually useful to have on the BSOD:

          • distro-specific instructions for submitting a bug report
          • option to reboot
          • option to show debug info
          • option to show a qr code that submits a bug report
          • and, if configured by the distro or system admin, debug info
          • Possibly linuxEnglish
            1·
            5 months ago

            How are you going to use your computer when the kernel panics. That’s kind of the problem, it panicked. It would be nice if it rebooted after a minute or two

            • bastion@feddit.nl
              3·
              5 months ago

              Any information given would obviously be for use with another device.

              QR code, for example. These are instructions or information about the crash, not links (except the QR code, which would obviously be read by another device).