this post was submitted on 04 Jul 2024
71 points (100.0% liked)

Linux

8090 readers
24 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
top 12 comments
sorted by: hot top controversial new old
[–] [email protected] 9 points 4 months ago

For anyone curious, the preview image contains this link

The trace seems to be part of the request. It's only using digits to encode; I wonder why not at least base64

[–] [email protected] 5 points 4 months ago (1 children)

What in the Microsoft Windows is going on here?

[–] [email protected] 4 points 4 months ago

Potterdung's hand in it probably. That said, it makes it much easier to extract information about an error condition on a machine you might not have keyboard access to... assuming you do have screen access to, tho.

[–] [email protected] 3 points 4 months ago* (last edited 4 months ago) (3 children)

This seems like a regression. We use logs to tell us what's wrong for a reason.

Why would I want to scan a qr code on my phone to read shit on a tiny screen you could've just printed on the computers display?

Also this is gonna play out great in secured environments where cameras are a no no.

Leave shit like this to the fuckers with no taste at Microsoft. Kernel panics are supposed to be verbose.

[–] [email protected] 56 points 4 months ago (1 children)

Why would I want to scan a qr code on my phone to read shit on a tiny screen you could’ve just printed on the computers display?

Because getting it off your crashed computer's display and into text format, so it can be grepped or posted in a bug report, is a cumbersome task. (OCR tools are not ubiquitous, convenient, or reliable.) And an impossible task when half the crash dump scrolled off the screen.

Also this is gonna play out great in secured environments where cameras are a no no.

It's optional.

Leave shit like this to the fuckers with no taste at Microsoft. Kernel panics are supposed to be verbose.

That's how I felt when the BSoD screen was introduced, but with this new way of using it to reliably deliver more information than ever before, it's starting to look useful.

[–] [email protected] 10 points 4 months ago

i love how this is like a sentence for sentence uptranslation of my comment. thank you for sharing :)

[–] [email protected] 13 points 4 months ago (2 children)

(non industry person, heads up)

We use logs to tell us what's wrong for a reason.

sometimes u can’t access logs easily, no? especially if something is real busted

Why would I want to scan a qr code on my phone to read shit on a tiny screen you could've just printed on the computers display?

phone usually stays on when ur trying to reboot and finick with stuff, whereas computer screen turns off. other alternative to keep a persistent copy i guess would be to print it out but that’s not eco friendly

Also this is gonna play out great in secured environments where cameras are a no no.

can’t speak to this but hopefully u can disable it?

Leave shit like this to the fuckers with no taste at Microsoft. Kernel panics are supposed to be verbose.

that qr code is massive, looks pretty verbose to me. idk i like moves to make linux more accessible. people are always calling for the ‘year of the linux desktop’ and then turn around and do backlash to try to keep things obfuscated and unfriendly to the average human, especially, again, where u can probably disable it if wanted. idk i guess im pretty critical of that tendency.

[–] [email protected] 7 points 4 months ago (1 children)

people are always calling for the ‘year of the linux desktop’ and then turn around and do backlash to try to keep things obfuscated and unfriendly to the average human

To be fair to both of these groups in my impression those are usually separate people. People definitely have different visions for what good design is here.

The thing that strikes me as bad is when Unix conservatives (for lack of a better term) actively resists features to support use in modern, bit-mapped graphics as opposed to 70’s teletype terminals etc. But that’s just a terrible position, not necessarily hypocrisy, assuming they don’t care about Linux as the kernel in a desktop operating system for people whose hobby is not configuring their computer.

[–] [email protected] 0 points 4 months ago

this does explain quite a bit, thanks for the clarification

[–] [email protected] 0 points 4 months ago (1 children)

, where u can probably disable it if wanted.

these things should be opt-in, not opt-out. Opt-out is the way Microsoftism get (and have already gotten into) Linux.

[–] [email protected] 0 points 4 months ago

looks like its opt in good news

[–] [email protected] 4 points 4 months ago

From the article:

As kernel error messages can be quite lengthy especially if including a stack trace and at times not even fitting the contents within the screen, patches posted today allow for condensing kernel error messages into QR codes.