Not until I can have my pretty screensavers. Yes, I care. When my laptops are on battery they don’t need to S3 sleep, nor s0idle. They just show pretty animations that prompt for a password and let me in, without waiting ten years for it to wake up from its slumber
My HP crapbook doesn’t have this OEM logo bullshit. Only the windows bootloader shows it, and the logo file is stored in the BGRT. So I don’t think I’m affected unless the WBM or systemd-boot have this vuln.
Mine:
<span style="color:#323232;">1. Screen turns on
</span><span style="color:#323232;">2. I pick EndeavorOS in systemd-boot
</span><span style="color:#323232;">3. It starts spitting out logs (I love this behavior)
</span><span style="color:#323232;">4. It switches modes once the backlight is loaded
</span><span style="color:#323232;">5. I log in
</span><span style="color:#323232;">6. KDE loads
</span>
I will never understand people who install Plymouth, it just adds complexity in the boot process. If your distro installs this then I understand why: so it doesn’t look like you’re “hacking the government”. If your distro doesn’t install it and you install it then you probably picked the wrong distro.