It’s decades old is is probably broken. Run from the console and see what happens. More than likely it’s a core dump.

openSUSE Tumbleweed. Or EndeavorOS if you want to join the Arch side.

Fedora requires less maintenance which is important in a university scenario. But then you have those Exam Safe Browsers which don’t run on wine anyway.

If you’re going to miss AUR-levels of package count, my advice is to grab openSUSE (preferably non-Leap), get familiar with zypper and yast, then add the Packman repo. Combined with the OBS (basically the openSUSE version of the AUR), you’ll have pretty high package availability.

openSUSE also requires less maintenance than Arch.

But generally, I recommend EndeavourOS, just add the chaotic-aur so you don’t spend hours compiling, and have fun!

I agree with you.

I don’t hate Manjaro’s developers, but they simply do not know what they are doing. They over promise and under deliver.

Arch Linux 32.

Kdenlive’s pretty good.

Yes, IK WBM is not the problem here. My systems don’t show a logo at all, and they don’t have a “hide logo” options.

I never bought my current machines. Funnily enough, they don’t show any logos on bootup, (Windows Boot Manager is smth else)

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

Secure Boot is just Bootloader Signature Enforcement controlled by M$, it’s not gonna prevent Superfish 2.0 from happening.

Unfortunately, I don’t have a coreboot-able system. When I move out I’ll make that a priority.

That’s called CSM, and Intel removed it in late 2020. I’m not sure if AMD still has it, but they still have S3 sleep afaik. Go Team Red for your next buy, I am too.

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:

1. Screen turns on
2. I pick EndeavorOS in systemd-boot
3. It starts spitting out logs (I love this behavior)
4. It switches modes once the backlight is loaded
5. I log in
6. KDE loads

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.

Mine only switches modes once, on load save backlight.

Secure Boot is an utter piece of bullshit from the depths of hell.

Yes.

I know of one Fox, and he is Fox McCloud.

https://manjarno.pages.dev

Basically, the Manjaro team has no idea what they’re doing.

The ManjarNO sheep can fuck off to Reddit for all I care.

No, and trying to use a pure BIOS system these days is a headache.

You can always just reflash your firmware from a trusted OS via FWUPD.

Now it’s trying to either partial upgrade OR delete your desktop. Your system is fucked.

Oof. You uninstalled Mesa’s AMD config because a troll on the internet tried to partial upgrade your system. You’re kinda fucked.