Missing kernel config is a good guess at this point. If this is your first gentoo install I would recommend using the distribution kernel at first without manual configuration. It makes it easier to setup your system first to a usable state and then later you can still do a manual kernel config but at least have a back-up kernel that works until you get the manual config right.

Gentoo user....but assuming now it's about building on distributions that don't automate it like gentoo.

Disadvantages:

• No easy way to uninstall again. Some build systems generate lists of files that were installed or even some uninstall rules but that requires to either keep the build directory with the source-code around or to make backups of the necessary build files for proper uninstall. And in some build systems there are no helpers for uninstalling at all.
• Similar...updating doesn't guarantee to remove all traces of the previous version. If the new build overwrites every file of the previous version...fine. But if an update version doesn't need files anymore that were installed in previous versions those will usually not get remove from your system and stick around.
• In general lack of automatism for updates
• Compiling takes time
• You are responsible for dealing with ABI breakages in dependencies. In most cases the source-code you compile will depend on other libraries. Either those come from your distro or you also build them from source...but in both cases you are responsible for rebuilding a package if an update to one of the dependencies breaks the ABI.
• You need build-time dependencies and depending on your distro also -devel packages installed. If source-code you install needs an assembler to build you have to install that assembler which wouldn't be necessary if you installed the binary (You can remove those build-dependencies again of course until you need to rebuild). Similar for -devel packages for libraries from your distro....if the source-code depends on a library coming from your distro it also needs the header files, pkgconfig files and other development relevant files of that library installed which many distros split out in own -devel packages and that aren't necessary for binaries.
• You have to deal with compile flags and settings. It's up to you to set the optimization level, architecture and similar for your compiler in environment variables. Not a big deal but still something someone has to look into at the start.
• You have to deal with compile-time options and dependencies. The build-systems might tell you what packages are missing but you have to "translate" their errors into what to install with your package manager and do it yourself. Same for the detection of the build systems...you have to read the logs and possibly reconfigure source-code after installing some dependencies if he build systems turned off features you want because of lacking dependencies.
• Source-code and building need disk space so make sure you have enough free. Similar with RAM...gentoo suggests 2GB of ram for each --job of make/ninja but that's for extreme cases, you usually can get away with less than 2GB per job.

Of course you also gain a lot of advantages...but that wasn't asked ;)

You can "escape" most of the mentioned disadvantages by using a distro like gentoo that automates much of this. It's probably worth a look if you plan on doing this regularly.

edit:typos

From the mail it doesn't exactly look like "upstream dependencies on systemd" but rather like a lack of features in sysvinit:

The second reason for dropping System V is that packages like GNOME and soon KDE's Plasma are building in requirements that require capabilities in systemd that are not in System V. This could potentially be worked around with another init system like OpenRC, but beyond the transition process it still does not address the ongoing workload problem.

So it seems a bit like sysvinit is simply a dead end and there is definitively not enough manpower for a transition to openrc/elogind/whatever...and it's a good chance to consolidate the exiting workforce on a single version. Sounds all pretty reasonable to me. But it can't really serve as example for systemd being an absolute requirement even for LFS now and them being "forced" to use it.

I was wondering too why anyone would ever want this...but the proposal explains it:

Support for UEFI on MBR was originally added in blivet#764 to accommodate cloud image use cases, such as AWS, which at the time did not support UEFI booting on GPT disks. These constraints no longer apply to modern cloud platforms, making MBR-based UEFI setups unnecessary for current Fedora deployments.

So basically it was some workaround a few years ago. I have a hard time to see any reason speaking against the removal.

"Timber!"

I remember playing this some years ago...it was a lot of fun. Back then the "Atlantis" (I think...not sure, its been some years) campaign wasn't completely finished so maybe time to give it another shot :).

Try adding a PATH=/home/werecat/Grayjay line to your .desktop file. Without it the application will run with your home directory as your working-directory...and there the data files are missing (Why you need to copy them to your home). The path entry makes the program work in /home/werecat/Grayjay where the data directories actually are.

Edit: That is assuming when you started it manually you did a cd Grayjay and a ./Grayjay or similar. So you changed your working directory there first before starting it. If that is not the case ignore my post ;)

You can set most KDE menus to show the "Comment" key of the .desktop files instead of the "Name" key. So "KDE Advanced Text Editor" instead of "Kate".

Packages can come with several "programs" that aren't necessarily named the same as the package. Example: Calibre installs menu items for "Calibre", "EBookViewer" and "EBookEditor" on my distro.

It's not about forgetting...it' about helping to quickly find what you just installed and what is all included.

If it could the anti-cheat system wouldn't be worth using. Being able to "trick" the anti-cheat system into thinking something else is going on than actually happens is the same an actual "cheat" would do. That's why kernel level anti-cheat system go though a lot of trouble to detect any kind of virtualization or similar tricks...the moment you could trick them into accepting a fake kernel is also the moment that fake kernel can pretend the fake input it generates actually comes from a real mouse or the checksum of that openGL/vulkan library is exactly the one expected and not the one of some altered libraries that "accidentally" forget to not render stuff behind walls...

It's also something that needs to be kept in mind when talking about "Companies can just enable the linux support in their anti-cheat systems but they don't." While this is true of course it also means the kernel-level anti-cheat systems are bared from kernel-access and degraded to user-space only. And as people have access to the source-code of the linux kernel nothing is stopping anyone from just modifying the kernel to...give more "favorable results" while playing the game. Of course the linux playerbase it too tiny to really offer a market for such cheats...but it's not completely unreasonable to not want to erode the capabilities of your anti-cheat system (That is of course if you believe they work in the first place...but that's a different discussion).

Obscure as in "only for a very specific purpose and nothing else"?...

Well, there is the Mircrosoft linux distro for their azure cloud

I guess DD-WRT as distro for router is also kind of obscure. Or the more general openWRT for embedded systems.

Cautionary

Just to make this clear (Sorry if it's unnecessary, but maybe still useful info for others)...Path= lines in .desktop files are not related at all to the $PATH environment variables. They do something completely different (And yes, picking Path as key was a terrible choice in my view). Path= lines in .desktop files change the current working directory...they do about the same as a cd <directory> in a shell.

They do not change where a .desktop file looks for executables....only indirectly if a executable runs another file relative to the current directory or looks for images/icons/audio/other data relative to the current working directory.

And I have no clue why it doesn't work with TryExec...the desktop file spec doesn't mention anything about that :( ( https://specifications.freedesktop.org/desktop-entry-spec/latest/recognized-keys.html )

https://wiki.gentoo.org/wiki/Intel#X_drivers

What do you have in your VIDEO_CARDS variable in your portage settings?

Edit: Also if you configured your own kernel make sure to look at the section above the one i linked if you have everything needed enabled in your kernel config.

Edit2: About the ~amd64 keyword...gentoo packages come in two "branches". The stable and the testing branch. Normally you install a package in the stable version. But if you want you can set the ~amd64 keyword for a package and you get the testing version ( https://wiki.gentoo.org/wiki/ACCEPT_KEYWORDS ). You can mix stable and testing package on your system as you like...but often testing packages will require other testing packages to be installed. For KDE for example plasma 6.8 is currently the testing version and 6.6.6 and 6.7.5 are the stable versions (you can pick which one you want).

I really recommend you read the "Working with gentoo" and "Working with portage" section of the handbook...they explain most of this.

On-screen keyboard was already mentioned, but there are some other small things that might be useful for some:

Reboot/shutdown without having to login (Your husband/wife/partner can shutdown your computer without first having to login and be greeted by the porn folder on your desktop...nah seriously, this can be useful at times when your turn on the computer, get called away and someone else can easily shut down the computer after you didn't return for some hours)

Keyboard language selection before password entry. Very useful in multi-language households/companies.

The WM selection also allows kiosk-like behaviour in special cases...like you don't start a WM but start in kodi media player for a movie evening or you create your own WM session file for a single game that runs as soon as you login.

For me the real advantages of baloo are metadata search and KDE integration.

Searching for tags with baloosearch6 tag:<tag> is something I use rather often, I even use the star ratings in baloosearches with rating>=6. Combine that with a mimetype and and you have a quick playlist of all music you rated with 4 or more stars in dolphin: baloosearch rating>=8 AND type:audio.

I also using baloosearch for images....the width and height keys are really useful for finding textures with specific dimension...something like baloosearch type:image AND Width>=2048 AND Height>=2048

And the of course the KDE integration that makes this really useful...you can use baloosearch queries everywhere in KDE, in open-file dialogs, as bookmarks in dolphin or file-dialogs, for desktop widgets showing folders...you can easily create an activity that has several folder-views on the desktop each showing a different set of files with specific tag...so left folder-view showing all files tagged "WIP" while right folder-view shows all files tagged "Finished" (To use queries in KDE you need them in the form baloosearch:/?querry=<the querry as you would use it in balooserarch6>

Edit:I wrote a reddit post some years ago about this...hope linking reddit is okay here: https://www.reddit.com/r/kde/comments/pmcshj/tip_baloosearch_kioslave/

Yep, I really don't understand why people use baloo without content indexing...if you do that other means like your fd or even mlocate will probably be better solutions if all you need is filename search. KDE integration is really the only advantage left then...and I don't really see much need of creating bookmarks/folderviews with filename searches, you hardly ever have reoccurring searches for the same filenames.

Baloo only makes sense to use with content indexing in my view...and there it hardly has any equal. I personally can't be without this feature anymore. I use it actively since KDE4 days (anyone remembering nepomuk?) and my whole workflow is built on it.

I imagine the "update from another system" path runs in troubles with more complex gentoo installs than just the base system. For a full update from the live disk it will have to include lots and lots of (often exotic) tools that might be used in the building process (document generators like doxgen, lexer, testing frameworks, several build systems and make-likes. programming languages...) in addition to being able to build against the already installed updates for packages while not accidental building against packages that are not updated yet.

Or you go the simpler way and only do a base update from the live-system...only update the base build system and package management of the gentoo system and afterwards boot in a "broken" system in which only the basics works and rebuild it from there.

For be both those options sound less desirable than what is suggested in the blog.

It not being worth using is good, I want this malware practice to die.

Which is a noble goal in my view, I completely agree. But you will not be able to use anything like wine to achieve this...anti-cheat software is specifically designed to prevent all the things that wine does (For the reason that there is no technical difference between a "cheat program" and what wine does)

i’m sure there are already workarounds on windows, it’s not like cheating has been eliminated there

Actually I read about an interesting way a few months ago...on games that enabled linux support in their anti-cheat systems windows "cheats" started spoofing the OS signature to make the anti-cheat system think it runs on wine and turning of the kernel-level anticheat...

But as I said, the effectiveness of anit-cheat is a different discussion independent of the question if wine will support them. Even if anti-cheat systems are ineffective it doesn't change that they are mainly aimed at stopping exactly the kind of "trickery" wine does. Wine would have to play the same cat and mouse game with anti-cheat as cheats do...if it finds a away to work around them the anti-cheat systems need to find a way to prevent that workaround.