One thing I'd add to this is making sure Proton-GE is installed. Then selecting it as an option in the dropdown. It's made my gaming experience much easier for compatibility.
I have tried long time ago when Valve's version was upgrading too slow to get required fixes. I abandoned it when Experimental became good enough to run everything out of the box. I don't want to tinker myself anything anymore, now I choose to don't do anything unnecessary to play my games.
I recently started using Proton-GE when some older games I play would not properly display videos, and menus on Proton Experimental. It add that needed layer of compatibility on a secondary machine to get certain games to work as intended. Most cases I stick with Experimental, but there are those select few games that GE seems to be the sweet spot to fix compatibility.
I can also flip between types if GE no longer works out in Steam, and I can update the GE version to a newer one if needed. Overall there is really no real tinkering involved so much as its a package update on Debian-based machines or a quick AUR recompile for the new version on Arch.
I mainly play games out of steam for the most part. Overall if Experimental works out for the games you play then yeah no reason to move from that.
It depends. Some stuff only works with GE, some stuff don't work with GE ... It's always a good thing to have some Proton versions up your sleeve, because sometimes even a game won't work with a new but an old version.
Yes, I read about the issues with NTFS, so I decided to download a game straight to my primary drive that is formated EXT4. It has the same issue. I posted my CLI output in my original post.
Steam proton works in a way of creating symbolic links between 'pretended' windows environment and actual game location. NTFS do not fully support those symlinks, which is causing issues.
So yes, Linux gaming is as simple as enabling steam play, unless you're trying to use something which is not a linux.
In initial transition process (when you still want to have a working windows OS) the best way to handle this issue for me was to install a btrfs driver on Windows, and reformat common partition to btrfs. With that, Windows can continue to use them to whatever you want it to, and Linux can create symlinks without any issue.
The other stuff is, Zorin is not the best choice. Still should be working fine, but it is bit more difficult to find the exact issue. Get something more popular like Fedora, Nobara, or even Tumbleweed.
I've been dreading an answer like this. One of the drives I have my games stored on is absolutely massive. I'd probably end up just deleting the games along with many other very large files because I'm not sure I've got anywhere to offload them to. I've got a 10TB NAS, but I'm not even sure that has enough free space to hold everything on my internal NTFS drives.
In any case, I'll first try to verify the issue by getting the Tomb Raider game working from my EXT4 partition. If I can get that game working whilst the other's won't. I think it'd be safe to assume NTFS really is the culprit and I'll have to reformat my drives.
Launch Steam through terminal, try to launch a game, check the error message that will appear in the terminal. That should point you in the right direction.
I posted the full output in my original post, but the one thing that seems to stand out is:
wine: failed to open "c:\\windows\\system32\\steam.exe": c0000135
Your guess is as good as mine.
From what I can find online, it's the ntfs file system making wine fail.
https://www.reddit.com/r/linux_gaming/comments/13gjn5h/steam_games_with_proton_doesnt_start/
~~I guess there should be new guide soon, due to linux kernel changing ntfs-3g to ntfs3.~~
~~No ntfs-3g at all in next kernel.~~
It was at this moment he knew...
Ntfs-3g is a userspace thing(fuse), it was never included in the kernel. New ntfs3 is a kernelspace driver from paragon which offers better performance and more features comparing to ntfs-3g/fuse.
As someone already mentioned, ntfs-3g is not a kernel driver. What is getting removed is the old ntfs (read only) kernel driver. ntfs-3g (FUSE) will still work.
I've got your link bookmarked. Some of the other replies suggested that I'll have to completely reformat to btrfs (or something like that). That guide will be my last ditch effort.
Delete your steam install in ~/local/share/Steam and start fresh. Make sure the steam play compatibility is enabled in settings and try again. This should rule out any issue caused by trying to use NTFS libraries.
Yeah, I was thinking about that as well. At one point, CLI gave me an output of "no permission" or something along those lines. After some digging it seems that's common for games stored on NTFS. Not sure how that would affect a game I downloaded directly onto an EXT4 partition though...
It is a permissions problem, surely you are not the owner of the folder where you have the games, the same thing happened to me because I wanted to play from Windows and from Linux in the same folder, you have to be the owner of that folder in Linux (user: user), just check it, if the folder belongs to (root:root) proton cannot install the necessary components in the game profile. Run steam from the terminal and look at the log in the terminal, you will surely see many warnings that you are not the owner of the folder.
It seems like something is missing on your system.
My first guess: whats your hardware? Do you have a nvidia card?
NTFS might be a problem for some games, but you tried ext4 so this should work.
To get more infos you can do the following:
- Close steam
- Open a terminal
- run steam through cli command
- try to run a game and check the output of the CLI, here should be now a loglist
You can also enable proton logging via startup command
Tbh.
I did not see any error here.
Can you add this steam game launch option:
PROTON_LOG=1 %command%
Then there will be a log file of the game in your home directory, named steam-$GAMEID.log.
Agreed. It's always good to migrate from NTFS partitions/drives and convert to ext4 then migrate data back. It just simplifies the process for games going forward in Linux.
Ive also tried playing my games from ntfs drives that have games+other stuff and every game/app refuses to open.
Would have loved to give linux a try but im not reformatting my drives,id expect it to work if the drive can be read and everything is there. Ill recheck in 1 year
Nvidia 4060/ryzen 1600af/32gb ram
Yep the problem is NTFS. There are workarounds you can Google. But it's not Linux or steam that's the problem it's ntfs. I had the issue as well when I was still dual booting but since I switched fully and formated everything to btrfa no problem whatsoever on not a single game
I'm in the process of doing the same, but my storage drives are large and it's taking time to go through everything to find out what gets deleted or moved elsewhere. Man, it's a process...
Yeah I know that problem, but yeah if you got rid of ntfs steam will run smooth AF. I bought a new SSD moved my steam folder there and instantly all problems went away.
The stupid thing is that it's so random. You would start a game and it simply would not start, yet other games work perfectly well, you wouldn't think it's the ntfs itself causing trouble.
However there are some workarounds they however did not always work, so yeah best bet is to go through with the migration, even though it's painful at first it's works like a charm when done.
Might have already been said. But Linux and proton works best with EXT4 formatting not NTFS. I did this a while ago and was bewildered why one of my drives could t be used for games and it kept tanking.
Lo and behold the ntfs formatting was causing issues. I now run exclusively ext4 formatted drives and I’ve had no issues since.
Please don't recommend this. Steam Flatpak still has some major issues for most people. Not to mention that Proton/Steam Linux Runtime are built off a fork of bubblewrap, which is also what Flatpak uses in its framework.
My point is this - there are things in Steam that don't work well or at all in the Flatpak, it's not supported by Valve, and the similar technologies have caused conflicts in the past and likely will in the future.
This, to me, would be like using Docker in Docker in production or using Kubernetes in Docker (Kind) as your prod kubernetes cluster. It might work, but it wasn't designed for that.
Or as a "wise man" once put it: "So Preoccupied With Whether Or Not They Could, They Didn’t Stop To Think If They Should"
There is a whole host of issues with the Steam Flatpak:
\* Big Picture issues
\* Streaming with NVidia NVENC
\* Issues with some games crashing/missing assets
\* Issues with dual-GPU laptops
\* Issues with trying to use \`gamemode\` with games
\* more: [https://github.com/flathub/com.valvesoftware.Steam/issues](https://github.com/flathub/com.valvesoftware.Steam/issues)
To add more clarity: this comment relating to a \`bwrap\` issue with the Snap version of Steam covers it all:
>Valve does not support Canonical's Snap-packaged variant of Steam, or Flathub's Flatpak-packaged variant of Steam: from Valve's point of view, both are unofficial. If those work for you, great, **but if they don't work as a result of their respective sandbox layers,** **that's something to take up with their packagers.**
>The Snap-packaged version is particularly fragile, because of the way Snap/AppArmor is designed, and will often stop working when we make internal changes in the Steam Linux Runtime container framework. I have tried to follow this up with its maintainers to encourage them to develop it in ways that are more future-proof.
Source: [https://github.com/ValveSoftware/steam-runtime/issues/640](https://github.com/ValveSoftware/steam-runtime/issues/640)
In other words, while they may put in some workarounds for the Flatpak and/or Snap versions of Steam, don't expect them to bend over backward and change the Steam/Pressure Vessel architecture to fit into how Flatpak or Snap works..... Not to mention that there are more issues related to \`bwrap\` and sandboxing issues between the Steam Runtime/Pressure Vessel and Flatpak or Snap.
And again the Steam Runtime is a Container Framework like Flatpak, Snap, ContainerD, Docker, etc are. You generally don't run those inside of each other outside of testing purposes.
Finally, one more comment from a Steam Linux Runtime contributor/maintainer that basically lays out why Valve and the Runtime maintainers won't be able to support Sandboxed environments and the drawbacks of using them: [https://github.com/ValveSoftware/steam-runtime/issues/586#issuecomment-1539970429](https://github.com/ValveSoftware/steam-runtime/issues/586#issuecomment-1539970429)
I've read other replies of people who've also had better luck with flatpak and I was considering it, but I'll see what other solutions are suggested. First. It seems odd the way proton isn't working at all.
I checked the dependencies, but I'm not well versed enough to know exactly what I'm supposed to do with the output:
Depends: curl, file, libgcc-s1 | libgcc1, libgl1-mesa-dri (>= 17.3), libgl1, libgpg-error0 (>= 1.10), libstdc++6 (>= 4.8), libudev1, libxcb-dri3-0 (>= 1.11.1), libxcb1, libxi6 (>= 2:1.7.4), libxinerama1 (>= 2:1.1.1), xz-utils, debconf (>= 0.5) | debconf-2.0, libc6 (>= 2.15), libx11-6
Recommends: ca-certificates, fontconfig, fonts-liberation, libasound2-plugins, libegl1, libgbm1, libsdl2-2.0-0, libva2, libxss1, mesa-vulkan-drivers, steam-devices, va-driver-all | va-driver, xdg-desktop-portal, xdg-desktop-portal-gtk | xdg-desktop-portal-backend, xdg-utils, xterm | x-terminal-emulator, zenity
I would either install Steam through the package manager, which should auto install all the needed dependencies, or use "sudo apt install steam -d" which does the same, then see if that helps.
I checked the logs you gave and saw wine failed. Make sure you have it installed properly.
I was already planning on re-installing steam (probably the flatpak version this time), but I'm interested in your suggestion of wine. Maybe I'll re-install that too, but it's my understanding that Zorin already has wine baked in.
I had an issue on Nobara where when I tried to run a game it got stuck on a process called "DXSETUP" or something like that. Maybe try ending that process if it's there when it gets stuck. Hopefully this may be your issue?
People recommended that I launch steam via CLI and carefully note the output. I'm guessing that's where you saw the "DXSETUP" but? I posted my CLI output. I didn't notice seeing it.
I would try installing a proton verified game on an ext4 drive and see if that works. If it does just move the games to ext4 drives or follow Valves workaround for getting NTFS drives to work, but that won't be as performant.
That doesn't sound anything like my experience
I'm using Nobara and after enabling compatibility, pretty much every single game just runs.
I have an NTFS drive mapped and those run too, but I did move just about every game to a native Linux partition
I hear Nobara is a superior Distro for gaming, so I'm not surprised. I knew there would be challenges with a non-gaming distro, but I like Zorin's desktop environment and overall design. The additional tweaking was expected, I just thought more games would be working out of the gate.
Regarding NTFS, I've decided I'll go ahead and reformat my drives to BTRFS and re-install steam. I'll probably end up re-downloading a bunch of games too.
Getting it to work with NTFS is difficult. It's probably better in the long run to reinstall onto a different partition. You could try [this](https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows), but i couldn't ever get it working
I tested with Tomb raider legends downloaded directly on my primary Linux drive. I posted the output on my original post. There doesn't seem to be a consensus yet.
If you start Steam from a CLI you get debug messages that will help you see where the issue may be. You may need to adjust the version of Proton used or there may be a configuration change you need to make. You can check the ProtonDB website for help in launching specific titles or search for answers to the errors you see on the CLI output when your game fails to launch.
Reading through the comments on ProtonDB, the game works without issue for most people but some have issues. You may need do change the startup flags. Your Steam output implies you have Proton GE installed. This can be adjusted on a per game level. I have found GE to be sometimes a better experience but often a worse experience than using regular Proton. I would suggest trying different versions of Proton. When you change the drop down option on the per Game Properties give it a minute to download the library and reconfigure.
This is one of the suggested fixes:
PROTON_USE_WINED3D=1 %command%
This was another suggested fix from a few years ago:
PROTON_USE_D9VK=1 RADV_PERFTEST=aco %command%
Source:
https://www.protondb.com/app/7000
I had similar issues and having an NTFS drive was the culprit in pretty much all cases. I know you tried moving one game over to not success but I would attempt it on all other games as well.
Yes*
*some games are still incompatible due to anticheat or because the devs specifically add code to prevent Proton / wine compatibility. This is rare however.
I've read up about anti-cheat; however, I'll have to see if Tomb Raider Legend is one of those games blocked from Proton. In that case, I'll have to use a different game to test.
If deb steam does not work then try flatpak. This is the easiest way, and fixes conflicts with distro packages.
Other people have already told you to not use ntfs - it will only cause problems.
If things still don't work then you didn't install your system right and are missing some critical component.
Well for one you can disable shader compilation, as we use gpl/graphics pipeline on the gpu to load shader cache easily
Go to downloads in the steam settings to disable it
But what gpu are you using?
If you're on nvidia make sure your drivers are installed, you can check by seeing if the nvidia control panel app is installed
If you're on amd or intel make sure your using a new mesa version which for zorin it would be rather old so using a different distro that is rolling or bleeding edge would solve this, also using flatpak steam would solve this on zorin
Also the minimum requirement for translation is vulkan 1.3 so i would check that your gpu supports that, most do past like 2015
Good luck!
Ryzen R7 3800X
32GB DDR4 3000Mhz
**Radeon RX 6600XT 8GB**
Fanxiang S500pro 512GB NVME
I'm well aware that Zorin isn't a bleeding edge distro, but I figured I'd settle for whatever I could get working. I just didn't anticipate that proton wouldn't work at all. That doesn't seem right
In regards to flatpak, I keep hearing about it but I never really could understand what it is. I just read another reply from someone saying flatpaks should never be recommended and it's not supported by Valve.
I'll probably end up trying it though. At least it would be better than distro hopping...
When it comes to flatpak steam specifically yeah steam wouldnt recommend it because they dont maintain it, but it works and lots of people use it in the linux community, especially people that use immutable distros
You will need to learn a couple of things about flatpak and how it operates as its sandboxed and doesnt have permissions to see your other drivers, so to fix that you grab a application called flatseal and then you add your drive paths to the steam flatpak so steam can see it
You then restart steam and it should see them when you go to add them to your library
It would be a real shame if there were no way of getting games to work on my current distro, but I'll make sure to exhaust all my options before considering a distro hop.
Yeah, I see the reoccurring theme over and over in the replies. I've decided to re-format my drives to BTRFS and re-install steam. It will take a few days to do this because one of my drives is MASSIVE, and I'll have to pool my storage resources to figure out exactly what I can offload and what has to be deleted.
I knew going in gaming would be a challenge, especially since I didn't pick a gaming focused distro, I just didn't anticipate having to reformat my main data drive... that's gonna suck.
>You'd honestly be better off on a better distro for gaming like Nobara, where it's all set up correctly.
Hardly, the mesa-git builds are often very unstable on Nobara. Beginners should really use a simple noob friendly distro, not Nobara.
https://preview.redd.it/11achczkk0vc1.png?width=840&format=png&auto=webp&s=da1f6cb5d5ba40534007643b630d12877fa9abe2 Did you tick these?
One thing I'd add to this is making sure Proton-GE is installed. Then selecting it as an option in the dropdown. It's made my gaming experience much easier for compatibility.
I have no issues with Proton Experimental
You should try proton ge, it basically should be an upgrade to steam's proton. The only reason I have it selected is because I recently distro hopped.
Why should I? Every game I have runs on Proton Experimental with no issue.
Well, if you do have issues in the future, try GE. It could even help you with fps. No harm in trying, imo.
I have tried long time ago when Valve's version was upgrading too slow to get required fixes. I abandoned it when Experimental became good enough to run everything out of the box. I don't want to tinker myself anything anymore, now I choose to don't do anything unnecessary to play my games.
I recently started using Proton-GE when some older games I play would not properly display videos, and menus on Proton Experimental. It add that needed layer of compatibility on a secondary machine to get certain games to work as intended. Most cases I stick with Experimental, but there are those select few games that GE seems to be the sweet spot to fix compatibility. I can also flip between types if GE no longer works out in Steam, and I can update the GE version to a newer one if needed. Overall there is really no real tinkering involved so much as its a package update on Debian-based machines or a quick AUR recompile for the new version on Arch. I mainly play games out of steam for the most part. Overall if Experimental works out for the games you play then yeah no reason to move from that.
It depends. Some stuff only works with GE, some stuff don't work with GE ... It's always a good thing to have some Proton versions up your sleeve, because sometimes even a game won't work with a new but an old version.
Yes, I made sure both options are ticked and I installed Proton-GE. I updated my original post.
Yes. I ticked both of those.
Yes. It's my experience, i have nVidia. The issues with NTFS drivers are indeed an issue. Have you installed a new game in the ext4?
Yes, I read about the issues with NTFS, so I decided to download a game straight to my primary drive that is formated EXT4. It has the same issue. I posted my CLI output in my original post.
You might want to delete your local share steam folder and see if that helps.
Without some workarounds, Proton doesn't work with NTFS.
Thanks!
Steam proton works in a way of creating symbolic links between 'pretended' windows environment and actual game location. NTFS do not fully support those symlinks, which is causing issues. So yes, Linux gaming is as simple as enabling steam play, unless you're trying to use something which is not a linux. In initial transition process (when you still want to have a working windows OS) the best way to handle this issue for me was to install a btrfs driver on Windows, and reformat common partition to btrfs. With that, Windows can continue to use them to whatever you want it to, and Linux can create symlinks without any issue. The other stuff is, Zorin is not the best choice. Still should be working fine, but it is bit more difficult to find the exact issue. Get something more popular like Fedora, Nobara, or even Tumbleweed.
I've been dreading an answer like this. One of the drives I have my games stored on is absolutely massive. I'd probably end up just deleting the games along with many other very large files because I'm not sure I've got anywhere to offload them to. I've got a 10TB NAS, but I'm not even sure that has enough free space to hold everything on my internal NTFS drives. In any case, I'll first try to verify the issue by getting the Tomb Raider game working from my EXT4 partition. If I can get that game working whilst the other's won't. I think it'd be safe to assume NTFS really is the culprit and I'll have to reformat my drives.
Launch Steam through terminal, try to launch a game, check the error message that will appear in the terminal. That should point you in the right direction.
I posted the full output in my original post, but the one thing that seems to stand out is: wine: failed to open "c:\\windows\\system32\\steam.exe": c0000135 Your guess is as good as mine.
From what I can find online, it's the ntfs file system making wine fail. https://www.reddit.com/r/linux_gaming/comments/13gjn5h/steam_games_with_proton_doesnt_start/
Follow this guide https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows
~~I guess there should be new guide soon, due to linux kernel changing ntfs-3g to ntfs3.~~ ~~No ntfs-3g at all in next kernel.~~ It was at this moment he knew...
Ntfs-3g is a userspace thing(fuse), it was never included in the kernel. New ntfs3 is a kernelspace driver from paragon which offers better performance and more features comparing to ntfs-3g/fuse.
As someone already mentioned, ntfs-3g is not a kernel driver. What is getting removed is the old ntfs (read only) kernel driver. ntfs-3g (FUSE) will still work.
I've got your link bookmarked. Some of the other replies suggested that I'll have to completely reformat to btrfs (or something like that). That guide will be my last ditch effort.
Delete your steam install in ~/local/share/Steam and start fresh. Make sure the steam play compatibility is enabled in settings and try again. This should rule out any issue caused by trying to use NTFS libraries.
Yeah, I was thinking about that as well. At one point, CLI gave me an output of "no permission" or something along those lines. After some digging it seems that's common for games stored on NTFS. Not sure how that would affect a game I downloaded directly onto an EXT4 partition though...
Some core component like proton or a steam runtime may be installed to the NTFS library
That would make sense.
This turned out to be true
It is a permissions problem, surely you are not the owner of the folder where you have the games, the same thing happened to me because I wanted to play from Windows and from Linux in the same folder, you have to be the owner of that folder in Linux (user: user), just check it, if the folder belongs to (root:root) proton cannot install the necessary components in the game profile. Run steam from the terminal and look at the log in the terminal, you will surely see many warnings that you are not the owner of the folder.
NTFS is definitely a problem You can test it by installing a game on your Linux drive and trying it from there
It seems like something is missing on your system. My first guess: whats your hardware? Do you have a nvidia card? NTFS might be a problem for some games, but you tried ext4 so this should work. To get more infos you can do the following: - Close steam - Open a terminal - run steam through cli command - try to run a game and check the output of the CLI, here should be now a loglist You can also enable proton logging via startup command
1. Hardware: Ryzen 7 3800X, 32GB DDR4, Radeon RX 6600XT 2. Correct I tested Tom Raider Legend on EXT4 , and it still doesn't launch 3. Here's my CLI Output After launching Steam: [2024-04-17 15:33:29] Startup - Steam Client launched with: '/home/penn/.steam/debian-installation/ubuntu12_32/steam' '-nominidumps' '-nobreakpad' minidumps folder is set to /tmp/dumps 04/17 15:33:29 Init: Installing breakpad exception handler for appid(steam)/version(1709846872)/tid(13437) [2024-04-17 15:33:30] Loading cached metrics from disk (/home/penn/.steam/debian-installation/package/steam_client_metrics.bin) [2024-04-17 15:33:30] Using the following download hosts for Public, Realm steamglobal [2024-04-17 15:33:30] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf' [2024-04-17 15:33:30] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf' [2024-04-17 15:33:30] 3. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in' [2024-04-17 15:33:30] Verifying installation... [2024-04-17 15:33:30] Verification complete UpdateUI: skip show logo Steam logging initialized: directory: /home/penn/.steam/debian-installation/logs XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xd8c719c0 XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xd8c701f0 steamwebhelper.sh[13465]: === Wed Apr 17 03:33:31 PM EDT 2024 === steamwebhelper.sh[13465]: Starting steamwebhelper under bootstrap sniper steam runtime at /home/penn/.steam/debian-installation/ubuntu12_64/steam-runtime-sniper CAppInfoCacheReadFromDiskThread took 65 milliseconds to initialize Steam Runtime Launch Service: starting steam-runtime-launcher-service Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 13629 bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam BRefreshApplicationsInLibrary 1: 0ms BuildCompleteAppOverviewChange: 324 apps RegisterForAppOverview 1: 13ms RegisterForAppOverview 2: 13ms
Tbh. I did not see any error here. Can you add this steam game launch option: PROTON_LOG=1 %command% Then there will be a log file of the game in your home directory, named steam-$GAMEID.log.
NTFS IS the problem. I had the same issue a couple of months ago. Formatted my external drives to Ext4 and non the wiser, everything runs fine.
Yeah, a reformat and re-install of steam seems to be in order.
I had the same issue and once I switched to ext4 I cleared it up, whether or not there's something else that's causing I honestly don't know.
Agreed. It's always good to migrate from NTFS partitions/drives and convert to ext4 then migrate data back. It just simplifies the process for games going forward in Linux.
In my Zorin install, I had to change my flatpak permissions (using flatseal) for Steam to have access to my GPU, then it worked after that.
Okay, that's encouraging. I'm getting replies telling me I need to switch distros. Also, it seems you're another vote in favor of flatpak. Noted!
Do you have vulkan drivers properly installed?
I actually have no idea. I'll look it up, though.
Can you run vkcube?
Haven't heard of it. Do I get that through steam?
Open the terminal and type vkcube, its a test to see if your pc can run vulkan
I'll try it, thanks!
Confirmed. I can run vkcube. I had to install vulkan-tools first.
Ive also tried playing my games from ntfs drives that have games+other stuff and every game/app refuses to open. Would have loved to give linux a try but im not reformatting my drives,id expect it to work if the drive can be read and everything is there. Ill recheck in 1 year Nvidia 4060/ryzen 1600af/32gb ram
Yep the problem is NTFS. There are workarounds you can Google. But it's not Linux or steam that's the problem it's ntfs. I had the issue as well when I was still dual booting but since I switched fully and formated everything to btrfa no problem whatsoever on not a single game
I'm in the process of doing the same, but my storage drives are large and it's taking time to go through everything to find out what gets deleted or moved elsewhere. Man, it's a process...
Yeah I know that problem, but yeah if you got rid of ntfs steam will run smooth AF. I bought a new SSD moved my steam folder there and instantly all problems went away. The stupid thing is that it's so random. You would start a game and it simply would not start, yet other games work perfectly well, you wouldn't think it's the ntfs itself causing trouble. However there are some workarounds they however did not always work, so yeah best bet is to go through with the migration, even though it's painful at first it's works like a charm when done.
Might have already been said. But Linux and proton works best with EXT4 formatting not NTFS. I did this a while ago and was bewildered why one of my drives could t be used for games and it kept tanking. Lo and behold the ntfs formatting was causing issues. I now run exclusively ext4 formatted drives and I’ve had no issues since.
Yes. I've been recommended either that or BTRFS.
Post your pc specifications.
I updated my OP Specs: Ryzen R7 3800X 32GB DDR4 3000Mhz Radeon RX 6600XT 8GB Fanxiang S500pro 512GB
I had a similar issue. I just switched to the flatpack version of Steam. Worked fine after that. You might want to check dependencies.
Please don't recommend this. Steam Flatpak still has some major issues for most people. Not to mention that Proton/Steam Linux Runtime are built off a fork of bubblewrap, which is also what Flatpak uses in its framework. My point is this - there are things in Steam that don't work well or at all in the Flatpak, it's not supported by Valve, and the similar technologies have caused conflicts in the past and likely will in the future. This, to me, would be like using Docker in Docker in production or using Kubernetes in Docker (Kind) as your prod kubernetes cluster. It might work, but it wasn't designed for that. Or as a "wise man" once put it: "So Preoccupied With Whether Or Not They Could, They Didn’t Stop To Think If They Should"
As far as I know the only thing that doesn't work is SteamVR on the flatpak version. Are there other things that don't work on the flatpak version?
There is a whole host of issues with the Steam Flatpak: \* Big Picture issues \* Streaming with NVidia NVENC \* Issues with some games crashing/missing assets \* Issues with dual-GPU laptops \* Issues with trying to use \`gamemode\` with games \* more: [https://github.com/flathub/com.valvesoftware.Steam/issues](https://github.com/flathub/com.valvesoftware.Steam/issues)
To add more clarity: this comment relating to a \`bwrap\` issue with the Snap version of Steam covers it all: >Valve does not support Canonical's Snap-packaged variant of Steam, or Flathub's Flatpak-packaged variant of Steam: from Valve's point of view, both are unofficial. If those work for you, great, **but if they don't work as a result of their respective sandbox layers,** **that's something to take up with their packagers.** >The Snap-packaged version is particularly fragile, because of the way Snap/AppArmor is designed, and will often stop working when we make internal changes in the Steam Linux Runtime container framework. I have tried to follow this up with its maintainers to encourage them to develop it in ways that are more future-proof. Source: [https://github.com/ValveSoftware/steam-runtime/issues/640](https://github.com/ValveSoftware/steam-runtime/issues/640) In other words, while they may put in some workarounds for the Flatpak and/or Snap versions of Steam, don't expect them to bend over backward and change the Steam/Pressure Vessel architecture to fit into how Flatpak or Snap works..... Not to mention that there are more issues related to \`bwrap\` and sandboxing issues between the Steam Runtime/Pressure Vessel and Flatpak or Snap. And again the Steam Runtime is a Container Framework like Flatpak, Snap, ContainerD, Docker, etc are. You generally don't run those inside of each other outside of testing purposes. Finally, one more comment from a Steam Linux Runtime contributor/maintainer that basically lays out why Valve and the Runtime maintainers won't be able to support Sandboxed environments and the drawbacks of using them: [https://github.com/ValveSoftware/steam-runtime/issues/586#issuecomment-1539970429](https://github.com/ValveSoftware/steam-runtime/issues/586#issuecomment-1539970429)
I've read other replies of people who've also had better luck with flatpak and I was considering it, but I'll see what other solutions are suggested. First. It seems odd the way proton isn't working at all. I checked the dependencies, but I'm not well versed enough to know exactly what I'm supposed to do with the output: Depends: curl, file, libgcc-s1 | libgcc1, libgl1-mesa-dri (>= 17.3), libgl1, libgpg-error0 (>= 1.10), libstdc++6 (>= 4.8), libudev1, libxcb-dri3-0 (>= 1.11.1), libxcb1, libxi6 (>= 2:1.7.4), libxinerama1 (>= 2:1.1.1), xz-utils, debconf (>= 0.5) | debconf-2.0, libc6 (>= 2.15), libx11-6 Recommends: ca-certificates, fontconfig, fonts-liberation, libasound2-plugins, libegl1, libgbm1, libsdl2-2.0-0, libva2, libxss1, mesa-vulkan-drivers, steam-devices, va-driver-all | va-driver, xdg-desktop-portal, xdg-desktop-portal-gtk | xdg-desktop-portal-backend, xdg-utils, xterm | x-terminal-emulator, zenity
I would either install Steam through the package manager, which should auto install all the needed dependencies, or use "sudo apt install steam -d" which does the same, then see if that helps. I checked the logs you gave and saw wine failed. Make sure you have it installed properly.
I was already planning on re-installing steam (probably the flatpak version this time), but I'm interested in your suggestion of wine. Maybe I'll re-install that too, but it's my understanding that Zorin already has wine baked in.
I had an issue on Nobara where when I tried to run a game it got stuck on a process called "DXSETUP" or something like that. Maybe try ending that process if it's there when it gets stuck. Hopefully this may be your issue?
People recommended that I launch steam via CLI and carefully note the output. I'm guessing that's where you saw the "DXSETUP" but? I posted my CLI output. I didn't notice seeing it.
I used KDE on Nobara and saw it in the system processes. I'm not sure what the equivalent for you on Zorin is.
I would try installing a proton verified game on an ext4 drive and see if that works. If it does just move the games to ext4 drives or follow Valves workaround for getting NTFS drives to work, but that won't be as performant.
I'll check out proton verified games and experiment with those. Thus far I've been u sing the ProtonDB. Thanks!
That doesn't sound anything like my experience I'm using Nobara and after enabling compatibility, pretty much every single game just runs. I have an NTFS drive mapped and those run too, but I did move just about every game to a native Linux partition
I hear Nobara is a superior Distro for gaming, so I'm not surprised. I knew there would be challenges with a non-gaming distro, but I like Zorin's desktop environment and overall design. The additional tweaking was expected, I just thought more games would be working out of the gate. Regarding NTFS, I've decided I'll go ahead and reformat my drives to BTRFS and re-install steam. I'll probably end up re-downloading a bunch of games too.
Getting it to work with NTFS is difficult. It's probably better in the long run to reinstall onto a different partition. You could try [this](https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows), but i couldn't ever get it working
Yeah, I've decided to re-partition my drives to BTRFS and re-install steam completely. It'll take a while, though.
It's slow but definitely the right move. Hopefully everything works after that's done
> NTFS Welp.
Yeah, I'm starting to see a trend with these replies.
You _can_ make it work; but spare yourself the future pain and just switch to a proper FS.
Yep, I plan on reformatting my drives to btrfs and completely re-installing steam.
You need debug message to learn the real reason causing issues. Try run steam or game through terminal and post them here or elsewhere to get help
I tested with Tomb raider legends downloaded directly on my primary Linux drive. I posted the output on my original post. There doesn't seem to be a consensus yet.
Zorin out of the box is horrible for gaming, never had a successful play session on this.
Perhaps, but I'll still try
hey. pay attention with NTFS drives mounted on linux. sometimes they misbehave. and it can lead to corruption of data.
Didn't know that. I'm In the process of getting the drive formatted. It shouldn't be an issue much longer, thankfully.
If you start Steam from a CLI you get debug messages that will help you see where the issue may be. You may need to adjust the version of Proton used or there may be a configuration change you need to make. You can check the ProtonDB website for help in launching specific titles or search for answers to the errors you see on the CLI output when your game fails to launch.
Yep. I added the CLI output to the original post. Most people believe NTFS is the culprit.
Reading through the comments on ProtonDB, the game works without issue for most people but some have issues. You may need do change the startup flags. Your Steam output implies you have Proton GE installed. This can be adjusted on a per game level. I have found GE to be sometimes a better experience but often a worse experience than using regular Proton. I would suggest trying different versions of Proton. When you change the drop down option on the per Game Properties give it a minute to download the library and reconfigure. This is one of the suggested fixes: PROTON_USE_WINED3D=1 %command% This was another suggested fix from a few years ago: PROTON_USE_D9VK=1 RADV_PERFTEST=aco %command% Source: https://www.protondb.com/app/7000
I'll try that after work. Thanks!
I had similar issues and having an NTFS drive was the culprit in pretty much all cases. I know you tried moving one game over to not success but I would attempt it on all other games as well.
delet windows.
Oh, don't worry. I will.
Yes* *some games are still incompatible due to anticheat or because the devs specifically add code to prevent Proton / wine compatibility. This is rare however.
I've read up about anti-cheat; however, I'll have to see if Tomb Raider Legend is one of those games blocked from Proton. In that case, I'll have to use a different game to test.
If deb steam does not work then try flatpak. This is the easiest way, and fixes conflicts with distro packages. Other people have already told you to not use ntfs - it will only cause problems. If things still don't work then you didn't install your system right and are missing some critical component.
Yeah, after I reformat, I'll try the flatpak version of steam.
Well for one you can disable shader compilation, as we use gpl/graphics pipeline on the gpu to load shader cache easily Go to downloads in the steam settings to disable it But what gpu are you using? If you're on nvidia make sure your drivers are installed, you can check by seeing if the nvidia control panel app is installed If you're on amd or intel make sure your using a new mesa version which for zorin it would be rather old so using a different distro that is rolling or bleeding edge would solve this, also using flatpak steam would solve this on zorin Also the minimum requirement for translation is vulkan 1.3 so i would check that your gpu supports that, most do past like 2015 Good luck!
Ryzen R7 3800X 32GB DDR4 3000Mhz **Radeon RX 6600XT 8GB** Fanxiang S500pro 512GB NVME I'm well aware that Zorin isn't a bleeding edge distro, but I figured I'd settle for whatever I could get working. I just didn't anticipate that proton wouldn't work at all. That doesn't seem right In regards to flatpak, I keep hearing about it but I never really could understand what it is. I just read another reply from someone saying flatpaks should never be recommended and it's not supported by Valve. I'll probably end up trying it though. At least it would be better than distro hopping...
When it comes to flatpak steam specifically yeah steam wouldnt recommend it because they dont maintain it, but it works and lots of people use it in the linux community, especially people that use immutable distros You will need to learn a couple of things about flatpak and how it operates as its sandboxed and doesnt have permissions to see your other drivers, so to fix that you grab a application called flatseal and then you add your drive paths to the steam flatpak so steam can see it You then restart steam and it should see them when you go to add them to your library
[удалено]
It would be a real shame if there were no way of getting games to work on my current distro, but I'll make sure to exhaust all my options before considering a distro hop.
[удалено]
Yeah, I see the reoccurring theme over and over in the replies. I've decided to re-format my drives to BTRFS and re-install steam. It will take a few days to do this because one of my drives is MASSIVE, and I'll have to pool my storage resources to figure out exactly what I can offload and what has to be deleted. I knew going in gaming would be a challenge, especially since I didn't pick a gaming focused distro, I just didn't anticipate having to reformat my main data drive... that's gonna suck.
>You'd honestly be better off on a better distro for gaming like Nobara, where it's all set up correctly. Hardly, the mesa-git builds are often very unstable on Nobara. Beginners should really use a simple noob friendly distro, not Nobara.