Closed Eonfge closed 5 years ago
Thank you for the bug report. I'll take a look on it.
from what i see Proton is exporting the WINEPREFIX variable:
WINEPREFIX=/home/brezerk/.local/share/Steam/steamapps/compatdata/214730/pfx/
this is good
in order to control the process, you have to supply all variables like:
WINEDLLPATH=/home/brezerk/.local/share/Steam/steamapps/common/Proton\ 3.7/dist/lib64/wine WINEPREFIX=/home/brezerk/.local/share/Steam/steamapps/compatdata/214730/pfx/ WINEESYNC=1 /home/brezerk/.local/share/Steam/steamapps/common/Proton\ 3.7/dist/bin/wineserver -k
or you will get ABI mismatch:
wine client error:0: version mismatch 557/560.
Your wineserver binary was not upgraded correctly,
or you have an older one somewhere in your PATH.
Or maybe the wrong wineserver is still running?
So here is the issue:
Currently q4wine relays on the information present in the q4wine db regarding the wineprefix information:
execObj.cmdargs = "-kill";
execObj.execcmd = "wineserver";
if (!this->runWineBinary(execObj, db_prefix.getName(prefix_path), false)){
return false;
}
I think it is not the best solution: since you can have such side-running process in general (not really related to Proton). So I guess I need to change logic a bit: we need to extract the environment variables for the process.
as for the process list. this commit will fix the process display: https://github.com/brezerk/q4wine/commit/7bfd03ff6c14e58fcadb57f99c4b7eada96a6c66 you will be able to control single process via 'Stop current' and 'Renice'. The 'Stop wine' action will require additional fix.
This one https://github.com/brezerk/q4wine/commit/7ef9192e4aa84387b8de9745fd7a8d2f59dfe7f4 will address the 'Stop wine' action.
Should be all set now. Test please and reopen if needed.
Thanks.
Currently, Q4Wine has partial for Valve Proton processes in it's system. It would be useful if something was done with this in a more constructive manner. See the image:
There are roughly two options: