~/.steam/steam/steamapps/compatdata/774361/pfx isn't a valid path about mf-install

[z0z0z]

Try $HOME instead of ~.

[stitch1231]

Thank you, but now I'm getting this after running the install command.

./mf-install.sh: 23: export: 4.11/dist/bin:/home/stepan/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin: bad variable name

Is it because my Steam is installed in ~/.steam instead of ~/.local/shared?

I'm kinda lame with Linux, so apologies if I'm asking stupid questions.

[z0z0z]

4.11/dist/bin:/home/stepan/.local/bin

You can see it's added a relative (not absolute) path called "4.11/dist/bin" to your $PATH.

This is likely the full path "$HOME/.local/share/steam/steamapps/common/Proton 4.11"

Except it got butchered at the first space in "Proton 4.11". Why? I don't know. What exactly did you do, and did you edit the script?

[stitch1231]

I didn't edit the script. The thing is... there is no "steam" folder in my $HOME/.local/share/. My Steam is installed in $HOME/.steam/.

I think that's the issue? The script assumes it's in .local?

[z0z0z]

The script doesn't assume it's path at all.

The paths are exclusively specified by you, through setting the WINEPREFIX environment variable, and optionally an environment variable called PROTON.

You could have it set to WINEPREFIX="/root/anime/wine prefixes/foobar".

And that would be valid so long as you have a Wine prefix there.

Steam by default installs itself into $HOME/.local/share/Steam, with folders symlinking to it in $HOME/.steam.

Note that "Steam" is different from "steam", filenames are case sensitive in Unix.

This script still shouldn't have problems with symlinks, spaces, or $HOME in the path name though. Wine itself however doesn't like "~" for setting WINEPREFIX.

[stitch1231]

Alright, I will try to use the .local paths then. Thank you.

[z0z0z]

The $HOME/.steam paths should work fine too, you don't actually need to use $HOME/.local/share directly. There's something you're doing that isn't right.

The script doesn't care about using $HOME, or symlinks to the folder, or spaces, I just tried this myself:

WINEPREFIX="$HOME/.steam/steam/steamapps/compatdata/582010/pfx" PROTON="$HOME/.steam/steam/steamapps/common/Proton 4.11" ./mf-install.sh -proton

It does care if you use "~", but only because Wine itself doesn't like that.

[stitch1231]

Here's a screenshot that should show everything important, that is where I extracted the installer, and what I put into my terminal: https://i.imgur.com/o3oW8V2.png

[z0z0z]

Well that is right, even if you did extract mf-install to that folder for some reason.

At this point I'm curious why that doesn't work for you. Are you on some alternative shell other than bash? Like fish?

echo $SHELL

[stitch1231]

Nope, this is a default Ubuntu 18.04 installation. That command prints /bin/bash. I'll try to put the extracted files into a separate folder then.

[z0z0z]

I think I may know what the problem is.

Ubuntu may be using dash instead of bash as your default shell for #!/bin/sh.

Try doing the same thing but specifically specify bash mf-install.sh -proton

[stitch1231]

This worked! Thanks a lot for your time and help!

EDIT: I'll close the issue if you don't want to add anything more.

[z0z0z]

Thanks for reporting the issue, because of this I'm gonna change the shebang to #!/bin/bash.

Even though everything in the script should be shell independent, I guess some shells still have problems with basic stuff.

[michaelforney]

I don't think there is anything wrong with "basic stuff" with dash, it is following the POSIX standard.

In

export WINEDLLPATH=""$PROTON"/dist/lib/wine:"$PROTON"/dist/lib64/wine"

why do you leave $PROTON outside of the quotes? That means that it is subject to field splitting, which is causing the issue.

I think

export WINEDLLPATH="$PROTON/dist/lib/wine:$PROTON/dist/lib64/wine"

is what you want here, and should work fine.

[z0z0z]

With that I was specifically trying to encapsulate the variable within quotes, so no matter what crazy path full of characters like # ! @ $ % someone might have it in, it gets quoted.

You're right though, after testing this, it isn't proper.

However I would like to say that bash has no problem with this.

It won't work either way if someone has : in the path, but seriously though?