final edit: You want real logs instead? add this to your kernel command: drm.panic_screen=kmsg
Kinda funny, kinda neat.
I have no idea what the QR-code might reveal (I could not read it from this picture), so I pixelised it just to be sure.
FWIW I know exactly what happened and did not panic. To reproduce, boot your device with init=/bin/sh, then type exit.
CachyOS
The picture above is generated by Drm panic which is part of the kernel itself, or maybe a separate module. The data in the QR code is the kmsg log.
Not systemd, which wasn’t running when that happened.
And it’s been around for years; I guess I haven’t had a kernel panic in a long time.
No.
Scanning the QR code (on a different device presumably) might do that though.
It’s kinda what QR codes do.
But I agree, it’s not a good idea. Because people will scan that code and let their slabs of glass do their thing.