Unattended remote desktop has been the major sticking point for my switch, I have gotten it to work once I have logged in, but someone needs to log me in after a system reboot. I heard they were working on this with the new login manager, but I haven’t heard anything more about it.

You could inspect the script, it should be a one line shell command

FOSS devs especially, you do this for the good of everyone for little benefit to yourselves.

I guarantee that most contributors who aren’t being paid are doing their commits out of spite, but I can definitely applaud them for being as vindictive as they are.

I understand what you were saying now, when I read it before, it presented as one point(“please the share holders”) rather than your intended meaning.

I tend to agree that company backed projects go to shit after the shareholders get involved, but while there is nothing stopping Valve from doing an IPO in the future, they are currently a privately held company. This means they have no irrational share holders to appease. I surmize that this is the main reason why the Valve does nothing and wins meme exists because unlike most other corporations, Valve has the luxury of doing nothing.

I am very much the same with locking the system manually, and on KDE it is the same as the windows shortcut ie Super + L

and the third has stated they will not implement age attestation methods.

Do you have a source l, I went looking earlier and couldn’t find anything

If I were to take a guess, it is because it requires you to do software installation via CLI. If you are looking for a distro with a software store, I would say fedora or lmde is the move

I can’t help you there, I don’t personally use cachy I am just making assumptions based upon what I have heard and how it works on other distros

Packages != kernel, so probably not. I don’t know how power usery you want to be, if fine with some tinkering then staying with arch makes sense and as I said in the prior post I recommend endeavoros. If you want no tinkering, kubuntu is fine I would just lookup snaps and see what you are getting yourself into, and if that turns you away I would recommend mint lmde.

Some quick googling tells me that their optimized packages require 12th gen or newer, so that is likely what was messing you up. here is the link I found if you are interested, but I think your hardware is just to old.

I don’t know how old your hardware is, but iirc cachyos’s kernel specifically doesn’t support older hardware, so it could be that it is just too old. If I were you I would try out endeavoros if you can deal with a little more technical package management or you could use the base arch kernel on cachy. Of course your switch to kubuntu should continue to work assuming it was a kernel issue, I just don’t like canonicals vision.

Iirc manjaro changes the package management to not be rolling release, I think you would have to add back in the base arch repos and risk versioning issues.

I don’t know what a x-kiosk is, that might work, in any case if someone is on gnome or KDE, any solutions that rely on x11 will be deprecated in 2 & 3 major versions respectively

That is operating under the assumption that you aren’t using Wayland, as far as I could determine after a few hours of tinkering the only way to get a remote desktop to work under Wayland is by using an app that queries the xdg portal since Wayland’s harden permissions will stop xwayland based remote desktop solutions.

I use rustdesk over LAN for my remote desktop which has been rather stable and quick, although I don’t know the exact protocol that it uses, so if rdp is necessary I wouldn’t know of that is satisfactory for op’s needs.

I’m not good at reading these releases, is the armory support saying that the kernel will handle the rgb and fan headers that currently require a separate dkms module?

You could put him on to cachy os, iirc it has graphical package management and is built on arch.

I personally don’t understand why that command doesn’t run every time the system starts up by default, I wrote a script that ran it on startup years ago and I can’t tell you how many times it tells me that there were files that needed repairing.

Dual boot isn’t that bad if you just use separate drives; the issue is only with Windows and Linux on one drive.

This is only true if you boot Windows by switching the boot order in your bios, if you boot windows through grub or systemdboot, it is liable to overwrite files. That being said, keeping them on separate drives removes all but the afformentioned issue, so I would still highly recommend doing so if you plan on dual booting.