#Rocket League Boot Fails on Mint Steam from Separate Hard Drive

1 messages · Page 1 of 1 (latest)

glossy dragon
#

My Rocket League install on Steam will not boot when installed on a separate hard drive from my Linux Mint install. I try to click Play in the Rocket League steam library page but when it just stops and does not open any windows. Rocket league would install and run properly when installed on my SSD with Linux Mint on it. However, I have little space on the SSD. I have tried different Proton versions ranging from the latest stable to hot fix and others. Some Proton versions will boot the game but only the version in which Rocket leagues tells you the game is not compatible with Linux and to close the game. I have tried verifying the integrity of the game. I have tried deleting Steam cache, disabling pre-cacheing shaders, and tried nuking the Steam App ID folder in compdata.

Here is the Proton log of the attempt to run Rocket League:

Proton: 1749140930 proton-9.0-4f
SteamGameId: 252950
Command: ['/mnt/1ADE15A5DE1579E9/SteamLibrary/steamapps/common/rocketleague/Binaries/Win64/RocketLeague.exe']
Options: {'forcelgadd'}
depot: 3.0.20250616.139560
pressure-vessel: 0.20250616.0 scout
scripts: 0.20250616.0
sniper: 3.0.20250616.139560 sniper 3.0.20250616.139560
Kernel: Linux 6.14.0-28-generic #28~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 25 10:47:01 UTC 2 x86_64
Language: LC_ALL None, LC_MESSAGES None, LC_CTYPE None
Effective WINEDEBUG: +timestamp,+pid,+tid,+seh,+unwind,+threadname,+debugstr,+loaddll,+mscoree
======================
wineserver: /mnt/1ADE15A5DE1579E9/SteamLibrary/steamapps/compatdata/252950/pfx is not owned by you
wine: using kernel write watches, use_kernel_writewatch 1.
wine: '/mnt/1ADE15A5DE1579E9/SteamLibrary/steamapps/compatdata/252950/pfx' is not owned by you```

What troubleshooting steps might I take to get Rocket League to boot on my separate hard drive? Might it be a permissions issue with the drive it is installed to since that drive might have had Windows installed on it previously?
nimble beacon
#

!ntfs

young ventureBOT
#

#faq message

nimble beacon
#

If it's a permissions issue you could chown it (I'm very short on time atm so haven't read the full log I apologize)

glossy dragon
#

It is NTFS from what I can see

└─sdd1
     ntfs         Program Storage   1ADE15A5DE1579E9                      367.7G    61% /mnt/1ADE15A5DE1579E9
#

I'm not familiar with what chown refers to.

#

There is a dual boot Windows install on that drive so I'm uncertain is changing the ownership prevents that Windows install from booting.

nimble beacon
young ventureBOT
glossy dragon
#

That makes sense. When I get a drive formatted to ext4 I will try again.

nimble beacon
#

!ntfs

young ventureBOT
#

#faq message