

Would it work if it’s done from a previous, presumably untainted commit?
Theoretically yes, but at the moment I have more than 150 KDE packages installed; you would need to do this for each one and then make sure that they actually work together in this specific combination. Then, for each package you would need to check if any security bugfixes exist upstream that don’t exist in your fork and backport these.
I would say that is the bare minimum; you probably also want any bugfixes that are implemented upstream.
I guess with a team of a few people this would be doable, at least for some time; sooner or later some dependency (e.g. systemd) will be updated in such a way that your fork is no longer compatible and then you will either have to integrate the slop code from upstream to make it work, or do that on your own.
By the way, https://en.wikipedia.org/wiki/Trinity_Desktop_Environment is a fork of KDE 3, but that has no support for e.g. dark mode.








This really depends on your kernel. Try looking in
/var/log/messages. If you haveCONFIG_PSTOREenabled, you might have something in/sys/fs/pstore.Also you can put something like
console=ttyUSB0,115200in the kernel command line and read them over serial.