Give this a shot and see if it works. It’s pretty clever, and you won’t need to mess with much you may not understand yet: https://github.com/ctsdownloads/steam-drive-mounter-bu

Yeah, it’s worth asking though, because the solution has extra steps if it’s packaged with Snap or Flatpak.

Are you running Steam with Snap or Flatpak by chance?

Yep, that’s what that means. Steam is probably active before your DE touches that mount, which then auto-mounts it for you.

What’s your DE, and did you manually change any settings to have it auto-mounts this partition?

Are you relying on your DE to mount this partition, or do you have an fstab entry for it?

This is almost always a race condition where the mount is not available to access by the time the Steam client starts (usually because it auto-starts). If not, there is an options issue somewhere in the fstab entry or your DE auto-mounts this partition only after you try and access it.

An easy test: reboot your machine, before launching Steam, use your file manager to browse said partition, THEN start Steam and see if it is properly loaded.

Just stick with Fedora for your desktop if you want a traditional desktop workflow without having to jump through hoops. Any of the immutable distros have hoops you don’t want to mess with as a beginner, and the decades of forum and docs history generally won’t have information specific to your immutable distro and how to manage, so stick with the basics and Fedora.

All distros perform the same in general as far as gaming goes. There is negligible if any difference even tuned straight to the kernel, hands down.

The only thing you’ll need to figure out is what Desktop Environment you fit better with to start: KDE or Gnome.

Gnome is more like MacOS, and KDE is more like Windows. Both can be used at the same if you really wish, and there is nothing stopping you from altering whatever you install to behave like some other distro trivially.

Fedora is a good starter to figure out what you do and don’t like about which bits, and then make more informed decisions after using it for awhile.

Things mostly work fine in Proton, but this is more a software development and game engine issue than anything else. If developers wanted to make their games more compati5with Linux or Proton they could, it just costs money and effort.

Disable secure boot, and enable the restricted repos, then do an apt update and see what’s left to be installed. Make sure the iwlwifi package is installed.

More likely to be hardware than software. Have you checked your temps and voltages lately?

Check dmesg for errors related to memory, and after the machine comes back up, check your logs prior to it shutting down.

Overheating and bad memory present similar to this, but bad voltage could as well depending.

You need a driver for the controller, or an input library . It doesn’t “just work” in this sense.

If you have Steam installed and the controller works fine in games there, this is the issue. Steam runs the Steam input library, and takes the input from the device and translates it into compatible commands for the games.

Try this out: https://github.com/DanielOgorchock/joycond

How? You can turn them off.

Does it still happen if you lower the settings a notch though?

I don’t click Google Drive links.

What I CAN tell you is that if it’s time-based, it’s either heat or memory. There is no third thing.

Now, it could be a memory leak in the game, which would be widespread and others would see the same. That’s something that has to be addressed by developers.

Do you have temp info, or just CPU and Memory? If the latter, and you can see a continual increase in memory until it has issues, that’s a memory leak more than likely. If others are reporting the same, you’re not going to find anything to help you here.

Best advice I can give you is to lower settings and play for as long as you can until the devs fix that.

First, always check ProtonDB and see if other people have the same issues or tweaks to fix.

Second, get some system metrics, and check logs to see if anything obvious is showing.

You need logs, but I’m certain your OOMKilling the host. Pay less attention to what the VM is doing, and more to what the host is doing. Passing that amount of data through a VM on a host with only 4GB of RAM sounds like it’s destined to fail. Put a hard limit on the memory the VM can use and see if that helps, but I just don’t think you have the resources to manage this in the way you’re attempting.

A better question is: if you’re only running PBS on this machine, why is it in a VM?

1. What do you mean “on the same bridge”? A bridged network is a connection from a virtual adapter through the host machine for network access. Is review these connections to make sure you haven’t done something like duplicate an adapter and attempt to share address space. Also confirm which piece of networking is broke: DNS, ping, using DHCP, default gateway?
2. Pretty sure PBS is advised to NOT be used for targets on the same machine while running in a VM. I’ve seen people with the same issues many times, and it’s because it’s running in a VM and attempting to execute backups on the same instance. It’s supposed to be run a distinctly separate instance itself that can communicate with the clients on all targets.
3. https://www.wundertech.net/installing-jellyfin-on-proxmox/

I think this might be more of a selfhosting question, so maybe better for that sub.

I use Proton for business since it runs on everything. Zero issues.

Headers don’t interact with the kernel, so there’s no stability issue there. I assume what you did was install a mainline kernel in an Ubuntu flavor of something, then needed the headers for the Vbox extensions, but headers aren’t available in packages for mainline kernel versions.

You can build VirtualBox and it’s components, or just the components from source. That means install the packages bits, then download kernel source, and use it to build the extensions, then you can package and install them.

https://www.virtualbox.org/wiki/Linux build instructions

I would just make sure you’re only READING from the NTFS volume. Writing to NTFS is technically supported, but due to the nature of the filesystem, it will run into errors at some point as others may have mentioned.

Instagram/Threads has been implementing very difficult to bypass controls for content. If you can’t easily get it, it’s probably not worth it.