I haven’t played this one, but I did the one from KanoOS several years ago, and it was really helpful for learning some of the common CLI tools, like cat, cd, and grep.

More of these kinds of games is a good thing, IMO!

No, you don’t need to be worried. For example, Flatseal is a program to manage other flatpaks. This means that, by design, it needs to be able to grant flatpaks certain permissions that may expose them to system services they need to operate correctly.

One user mentioned that these new warnings aren’t particularly helpful, because they don’t give a good explanation of what or why, and they just foster anxiety in users who just want to install an otherwise reputable flatpak.

I don’t know anything about xournal++, but I would imagine it’s also reputably safe, and somebody else can verify for sure.

If it’s for someone else, I’d pick Mate or XFCE. Should feel familiar to Windows (which is what I’d guess they’re coming from), and it should be light enough to work on that hardware.

ElementaryOS comes with Pantheon, which is also very light, iirc, and it might be worth trying out via a live ISO.

So excited for this. I’m going to start a new game when it drops.

Yep, distrobox is a wrapper for Podman, which is also installed by default.

But I agree, there’s actually not a ton of functional difference between SteamOS and Bazzite, unless you want/need to use your Deck like a laptop. If you are only doing gaming, SteamOS is actually the better choice, because Valve has patches and modifications that aren’t yet included in upstream that maximize the hardware’s capabilities and stability.

KH2 is where I would say the gameplay really takes off.

And where I’ve heard from other fans that the story takes a dive off a cliff. So you get better gameplay and a mess of a story.

I do not have personal experience to verify, but multiple friends confirmed this to be the case.

Look at the preinstalled program Flatseal. It’s specifically for managing flatpak permissions.

It’s a distro that makes all but a few system directories immutable. This means you can’t just install whatever you want in the same way you would install in a traditional Linux system.

This comes with some benefits:

• Malicious and buggy software can’t permanently fuck up your installation. Even root can’t edit those directories.
• Each system update replaces only the system layer, but you can rollback to the previous one if something breaks.
• You can rebase to other images (like going from Fedora Kinoite to UBlue Aurora) with a simple command, and you don’t need to reinstall anything or worry about backing up your /home directory.
• Most software is installed via flatpaks or appimages, keeping a layer of separation between your system and your applications.
• Distroboxes/Podman containers can handle a lot of additional software while keeping it safely containerized.
• The system is generally reproducible, so the core of what you have is the core of what everybody else has.

Some drawbacks:

• You can’t install whatever you want however you want. There are some hard limitations on where files are allowed to go, and installing certain software that interacts with the kernel can be tricky (I’m currently trying to figure out the best way to install my VPN provider’s client).
• There’s a definite learning curve to working with containers. It’s not always as simple as “create container, install thing.”
• There’s a definite learning curve to retraining yourself to think in layers/containers.

Some examples of modern immutable distros are:

• Fedora Silverblue
• Fedora Kinoite
• Universal Blue Aurora
• Universal Blue Bluefin
• Universal Blue Bazzite
• NixOS
• BlendOS

I have to agree. I’m hoping Cosmic will be somewhere in-between!

My knowledge is limited, but you should be using that command to create service files, from what I understand. There’s some extra stuff that happens in the background (like putting symlinks in the correct places) after you write out the changes using that command.

Where is the service file located on your system?

Did you create it with sudo systemctl edit --force --full, or did you use a text editor (or was it automatically generated by an installer)?

Sorry I didn’t get back sooner, but I made some progress.

What do you mean with “work in progress”?

Their words (second video, I think), and more in reference to how they are still working out how they haven’t yet covered all of the use cases (like maybe my needs can’t currently be met by rpm-ostree or bootc). rpm-ostree has functional limitations, and bootc is still being developed. Obviously, both are still useable and useful, and Universal Blue has been using them for quite a while. I may have been reading too much into it with the “depreciation” comment.

So, did you try the following methods when installing the .run file? If so, how did it go?

It can’t work on its own. Running with sh or making it executable runs the script, but it fails when it tries to write its icon and .desktop entry to /usr (it also doesn’t take an --appimage-extract argument). You can use sudo rpm-ostree usroverlay to create a temporary FS overlay for /usr, but it’s wiped on the next boot. Still, that allowed the installation to complete.

I discovered that it’s installing all of the necessary components to /opt, and they remain functional. I was able to manually run the daemon script required and get a WireGuard tunnel established in the client.

Now, I’m trying to get a .service module to work so it can run automatically as root on a reboot with systemd. So far, it’s giving me a 126 exit code, so I still haven’t figured out how to escalate its privileges automatically, but this is the most progress I’ve made to date.

Correct, and if you just type ujust, you’ll get a list of all the “recipes” you can apply with that command (that’s what they’re called).

Alternatively, OP can contact the maintainers and see if they can add the necessary recipe. They’re really nice and responsive—even offered to add a semi-common print driver to the image for another user.

I love you Kitchen Breakfast Gun™!

But wait. One update failed. Why? Ah, the rescue partition is too small… THE ONE THAT DUMB SON-OF-BITCH CREATED ON ITS OWN AS PART OF THE INSTALL!

Shit, I forgot about this bug! Such a weird design choice to make the installer fuck up its own partitions.

I feel like it’s more common in indie games to get post-launch improvements like FSR. Still, seems like it’s becoming more common, especially in games that are graphically intensive.

You said it’s off-brand, and I have to wonder what kind of Bluetooth radio they used. Do you know what Bluetooth version it has?

I don’t like the fact that even if you have a Pro or Enterprise license, some amount of telemetry is still being sent to MS for any number of nebulous reasons.

At least with bigger names like Fedora et al, they give you the option up front to opt-in, and you can have a reasonable amount of trust that they won’t do it in secret.

The Microsoft support forums are pitifully hilarious, too.

“Hi, I need help with N. I’ve tried X, Y, and, Z.”

“Hello, sorry to hear that you’re having trouble with N. Have you tried X, Y, or Z?”

“Yes.”

“I’m sorry to hear that it’s still not working. Please refer to this thread, and feel free to contact Microsoft Support with any future questions. Have a nice day.”

“But my problem still isn’t solved. Hello?”

I wasn’t that into computers at that point in my life, but it was definitely a time where “computers” was a hobby, in the same way that restoring old motorcycles was/is a hobby. Sure, you might take it out for a spin every now and again, but a lot more time is spent tinkering than simply using.

I’m constantly amazed by how much better the end-user experience is today, even just from 10 years ago. The installers are better, the pre-configured software and settings are more thoughtfully chosen, and now we’re at the beginnings of meaningful Linux gaming for non-hobbyists.

We truly stand upon the shoulders of giants, and I look forward to the future.