2026-09-26 09:46 UTC
Replies (5)
-
@eleijeep@piefed.social 2026-09-26 10:20
So it’s leaking information about your system to an external site? That’s just what we need.
-
@A_norny_mousse@piefed.zip 2026-09-26 12:26
yes, it was Systemd who implemented it. I see. I guess I haven’t seen a kernel panic in a while. Yeah, not the best idea. Can it be disabled? It’s a static service, i.e. it is triggered by something else. A quick 5min search revealed nothing. I can always mask it, but I’m not sure that’s the best solution here.
-
@signofzeta@lemmygrad.ml 2026-09-26 13:58
That QR code could be helpful, but why can’t we have both? Show me the backtrace and logs, and stick a code in the corner in case I need the Internet’s help.
-
@LeLachs@lemmy.ml 2026-09-26 18:17
I disagree. The logs typically do not fit on the screen in text form, especially on low resolutions (like if the system has to fall back on an alternative graphics mode, which tends to happen more frequently in the event of a crash). Granted, a website is not the best possible solution and has the risk of leaking data but at least it is “a” solution. The data is encoded sure, but not in an obfuscated way. If you wanted, you could decode it with other means (for example a dedicated app that scans it).
-
@pipe01@programming.dev 2026-09-27 01:42
It’s a kernel thing, not systemd