Janne Pulkkinen

What exception does the file parser raise in this case? It would be better to catch only that since we risk silently ignoring other errors.

The last line of your traceback seems to be missing, but I managed to reproduce the error: it's UnicodeDecodeError. In this case I think ``` try: f.read() except UnicodeDecodeError: return...

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...

> Why do you even use hardcoded paths? Just look in $PATH for winetricks. Something like this: > > ```python > def find_executable(executable, path=None): > """Find if 'executable' can be...

Python 3.2 reached end-of-life on 2014-10-12 and I'm pretty sure most Proton users are running fairly modern software, so I don't think this will be an issue. I've created a...

I can reproduce this when using Proton 5.0 and the Flatpak version of Protontricks. Other installation methods (eg. pipx) work just fine, but I haven't yet been able to figure...

> I am having a similar issue where the ultimate error code ends up being: " warning: /home/deck/.var/app/com.github.Matoking.protontricks/cache/protontricks/proton/Proton 5.0/bin/wine cmd.exe /c echo '%AppData%' returned empty string, error message "fsync: up...

Could you try running the command again with the `-v` flag (eg. `protontricks -v 1091500 vcrun2019`)? This could also be related to #72 if your distro is too old. This...

@Malternative3772 I was able to reproduce the issue, kind of. The system Wine is able to install `vcrun2019` correctly. I was also able to install `vcrun2019` for a Proton game...

I tested this more, and I was able to install `vcrun2019` fine on a newly created Wine prefix using Proton Experimental and the newest Winetricks version. `vcrun2017` on the other...