After looking around, you might be facing an issue with Flatpak permissions. Here's a comment I found on Reddit created by u/avamk where they solved the same issue.

All right, after much trying I installed Flatseal and enabled the Firefox Flatpak's access to my home folder.

After this, it created the expected profile folder under ~/.mozilla/firefox/. I put my custom userChrome.css into that profile folder, and >enabled it in my about:config under toolkit.legacyUserProfileCustomizations.stylesheets per these instructions.

With all of these, the custom userChrome.css is finally working!

Link to original post: https://libreddit.tiekoetter.com/r/firefox/comments/rq40cj/cant_find_profile_folder_for_firefox_flatpak_on/

No, slow transfer speeds should not outright stop an app from functioning.

No worries, also to note there may be multiple pods as well as containers, so be sure to check those as well. Although, you can get a pretty good hint at which container is failing based on the application events log that you can first see when you click on the app.

I wanted to provide some screenshots in my last reply, but I was getting an error while trying to upload them, hopefully some of these might help to guide you.

For Application Events:

Example of Multiple Pods:

That's awesome, thank you for posting a guide! I took a quick look through, and it looks great, I'll definitely be sure to use this resource to get EmuJS running for my TrueNAS Scale server when I get the time.

From the logs you've provided, it appears the MariaDB server indicated a normal shutdown process without providing a specific reason for the shutdown initiation. So I'm assuming within your app it's running multiple containers, would you be able to provide the log of the container that is running into an error that's causing your app to call the shutdowns.

What do the app logs say?

Not OP, but I also use flat keycaps, so I thought I'd chime in. I'm not really sure why your hands would hurt with flat keycaps, but one of the reasons I chose to use flats were to allow for easier chording with Plover.

Gotcha I guess that makes sense, personally I haven't noticed any slow-downs but to each their own.

If you want to build up your ratio, you should try part seeding or outside seeding.

Oh! Hmm, I've never run into that issue before. Although I have noticed on some instances it works faster and more reliable than others.

Following communities could be another issue entirely, sometimes you have to subscribe then unsubscribe multiple times in order to get it to work.

I wonder if someone has already created a bot that asks chat-GPT to create a piece of code, grabs it to try and run it, and then just goes back and forth with chat-GPT to fix the errors. Now the code would probably be a complete mess, but I wonder if non-coders could use it to create helpful one-off tools they can't find anywhere else.