protonscr

EAC Detection Between Drives Fails

protonopen
ValveSoftware/Proton#9700 · opened 2026-04-22 by Rage-GitHub · updated 2026-04-28 · 2 comments · github
RRage-GitHub 2026-04-22 github

Your system information

  • Steam client version (build number or date): 1776812172
  • Distribution (e.g. Ubuntu): CachyOS
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs: steam-logs.tar.gz
  • GPU: Nvidia

Please describe your issue in as much detail as possible:

Games that have EAC as part of their installation process repeatedly fail to run if they're installed on other drives, via fstab mount points. If the game is installed on the same drive that Steam itself is installed on, EAC runs perfectly fine, but if not it fails with "Failed to get the process path'".

Steps for reproducing this issue:

  1. Mount a drive with fstab
  2. Install any game with EAC on the mounted drive
  3. Run it through Steam, using any Proton version
Ggashpot 2026-04-27 github

had the same issue as you, fixed it by adding the "exec" tag in "/etc/fstab" to the drive that i wanted to use for games.

RRage-GitHub 2026-04-28 github

had the same issue as you, fixed it by adding the "exec" tag in "/etc/fstab" to the drive that i wanted to use for games.

@gashpot that's strange, i already have exec added as a flag in fstab but still get the issue.

EDIT: huh, so i unmounted and remounted my drives and made sure to save the flags again for the mount points and it seems to be working now...

Nothing extracted yet.