The old one was too confusing for new users. It wasn’t clearly step by step like all the other installers on linux.

if you put the same NVME to one of the other slots does it still give this issue?

There is also bluefin lts (from the same ppl) if someone wants a more actively supported bootc system.

Currently most cooperate linux companies are not in the business of selling linux desktop itself. Rather its linux for servers, administration, embedded things (like cars), and other enterprisey stuff. So at least at the moment they are not looking to profit of linux desktop users directly which has saved us from enshittiffication attempts.

But even if they in the future attempt to do something fishy, that most users dont agree with, I think by the virtue of how stuff works on linux it will be very easy for people to move to something else or a fork, and still get 95-99% of the same experience. This in turn will force companies to think twice before doing something like this.

A good example here is canonical/Ubuntu who has made questionable decisions in the past and each time they had to take it back. Even now, Snap due to its use of a centralized store is almost universally shunned by the linux community and is only supported maintained by canonical. While Flatpak is supported by the wider linux community with people from different projects contributing to it (though I sometimes worry about everyone centralizing on Flathub to the point where they are actively discourage other projects from launching/maintaining their own stores/repos).

This is why we need to build and champion tech that is resistant to control and enshittiffication. Then we dont have to worry too much about who is developing it.

Impressive work, thanks!

KWin has gained support for the initial version of the Wayland session restore protocol

I found it interesting that they were merging support for a not-yet-merged protocol so I looked it up.

It seems the plan is to use the new experimental protocol thing that was introduced a while back:

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/392

I think x86 is basically the only platform that’s used ACPI

ARM and x86. From wikipedia:

Revision 5.0 of the ACPI specification was released in December 2011,[15] which added the ARM architecture support.

ETA: Sorry I was wrong. ACPI doesnt solve this*. Arm SystemReady SR/ES does and its why Ampere cpus can boot on linux on release without too much work.

Sadly its currently only used for iot/server stuff but hopefully it will eventually make its way to consumer tech. We need to raise awareness on this and pressure companies to commit to this standard.

*From what I read, WoA has full ACPI support but qcoms ACPI apis only work on Windows. [1 (ms link)][2]

Yeah its really unfortunate that most arm chips/devices use DTs instead of conforming to ACPI. However with ARM becoming more prominent on servers (and desktops), Im hoping this changes. There is now a push for ACPI on Arm since thats what companies running Arm on servers want. Ampere server cpus eg have ACPI support and arm now has docs on ACPI. I hope qualcomm is also forced to support ACPI. I think they will have to do it if they want to see their cpus being used in data centers and the like.

Yeah fedora does it even for small updates, not just kernel updates. But only if you update through the store.