Skip to content
This repository has been archived by the owner on Sep 3, 2021. It is now read-only.

WINE not on path when using protontricks #19

Open
KorinFlakes opened this issue Sep 22, 2018 · 4 comments
Open

WINE not on path when using protontricks #19

KorinFlakes opened this issue Sep 22, 2018 · 4 comments

Comments

@KorinFlakes
Copy link

When attempting to use protontricks to install either foss_corefonts or corefonts (protontricks 644560 foss_corefonts) I recieve this output:

[INFO] Found Steam directory at /home/user/.steam/steam. You can also define Steam directory manually using $STEAM_DIR
[INFO] Winetricks path is set to /home/user/Downloads/protontricks/winetricks
[INFO] Found proton version 3.7. You can also define the proton version manually using $PROTON_VERSION
[INFO] WINESERVER environment variable is not available Setting WINESERVER environment variable to proton bundled version
[INFO] Found 0 Steam library folders
[INFO] Found the prefix directory at /home/user/.steam/steam/steamapps/compatdata/644560/pfx
------------------------------------------------------
WINE is /home/user/.steam/steam/steamapps/common/Proton 3.7/dist/bin/wine, which is neither on the path nor an executable file
------------------------------------------------------

The fonts don't get installed and as a result, the game is not displaying the needed texts.
I've installed wine, winetricks and have steam setup properly to use proton.

@lucifertdark
Copy link

The newest version of Winetricks is here on Github, if you installed the one provided by your OS (like I did at first) it's probably out of date. https://github.com/Winetricks/winetricks

@Matoking
Copy link
Contributor

Matoking commented Sep 28, 2018

Had this same problem and running the command manually revealed the following error message:
00b3:err:esync:esync_init Server is running with WINEESYNC but this process is not, please enable WINEESYNC or restart wineserver.

WINEESYNC=1 protontricks ... did the trick, but killall wineserver would probably work as well and be more reliable. Or not, I'm not exactly sure. :P

@ryanmusante
Copy link

ryanmusante commented Sep 29, 2018

To be sure.

kill -SIGHUP $(pgrep wineserver)

@Sirmentio
Copy link
Owner

I think the answers given here are suitable, I think, trying a newer version of winetricks could work.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants