Yes, I read your comment. It’s okay if you didn’t understand my comment. Clearly you don’t understand how filesystems and drive mounting works under Linux or the role of desktop environments in managing filesystems, mounting, and permissions. I don’t doubt that you’re genuinely struggling here, but there is no call for that kind of hostility. You might have some hope for figuring it out if you open your mind to the fact that you don’t fully understand what your problem is.
Steam expects the games to be in a particular place with a particular set of permissions and ownership relative to the user(s) and/or group(s) expected to use those game files. I’m telling that Linux doesn’t care where those files physically reside. You can tell Steam that those files are exactly where Steam expects them to be at the filesystem level, without messing with Steam configs, nautilus, gnome, or KDE. There are several ways to do this, but without understanding the requirements of your machine no one here will be able to give you effective advice.
I’ve seen some other comments from you about running something or other as root or just blanket chmods to 777 and I can tell you from experience that those are rarely effective solutions and can sometimes make things worse (just try something like that when configuring ssh configs, keys, and permissions).
Almost guaranteed a Flatpak thing. I know you said X11 versus Wayland was your issue, but likely some quirk of the two window managers was allowing it to work.
Adding the drive path in Flatseal or installing non-Flatpak Steam would likely fix it.
It doesn’t matter where or how I mount the drive, the problem isn’t the drive; idk how I could have made that clearer.
The problem only happens under KDE and Gnome on Wayland; the nautilus thing was just a curiosity. Did you read my comment?
Yes, I read your comment. It’s okay if you didn’t understand my comment. Clearly you don’t understand how filesystems and drive mounting works under Linux or the role of desktop environments in managing filesystems, mounting, and permissions. I don’t doubt that you’re genuinely struggling here, but there is no call for that kind of hostility. You might have some hope for figuring it out if you open your mind to the fact that you don’t fully understand what your problem is.
Steam expects the games to be in a particular place with a particular set of permissions and ownership relative to the user(s) and/or group(s) expected to use those game files. I’m telling that Linux doesn’t care where those files physically reside. You can tell Steam that those files are exactly where Steam expects them to be at the filesystem level, without messing with Steam configs, nautilus, gnome, or KDE. There are several ways to do this, but without understanding the requirements of your machine no one here will be able to give you effective advice.
I’ve seen some other comments from you about running something or other as root or just blanket chmods to 777 and I can tell you from experience that those are rarely effective solutions and can sometimes make things worse (just try something like that when configuring ssh configs, keys, and permissions).
Almost guaranteed a Flatpak thing. I know you said X11 versus Wayland was your issue, but likely some quirk of the two window managers was allowing it to work.
Adding the drive path in Flatseal or installing non-Flatpak Steam would likely fix it.
I don’t generally do flatpaks, I just tried it to see if it would remove the issue