Is this a new report?

Yes

System Info

Void 6.14.2 x86_64 AuthenticAMD notuptodate hold rFFFFFFFFFFFFFFFFFFFF

Package(s) Affected

wine

Does a report exist for this bug with the project's home (upstream) and/or another distro?

possibly n/a

Expected behaviour

wine fose_loader.exe runs

Actual behaviour

Assertion failed in .\main.cpp (149): Launching Fallout failed (code = 00000057 (87))

Steps to reproduce

Build+install wine x86-64 (glibc) with wow64 - ./xbps-src pkg -o wow64 wine

wine fose_loader.exe

For a bit I've been going back to wine-10.1 because 10.2 was botched and they introduced bugs in 10.3. After using non-xbps-src to bisect the bug in 10.3, I uninstalled with make uninstall and xbps-remove, then re-installed the patched 10.5.

After this, fose quit working. I have tried to go back to 10.1, and to downgrade mesa which I am currently on a later version than Void. There are a few other packages (gmmlib, intel-media-driver) I have PRs for and updated but I didn't think they should be related.

Unsure what could have stopped this from working as it worked a few days ago before I touched wine again. Maybe there is some 'magic file' that I got rid of from an old version or something?

wine-32bit seems to run without issues. Installing wine from my git-bisect also has the same error though. I figured since this was working fine, it was probably a packaging thing, if not I can open a bug there.

(Also, side note, /bin/wine 'in srcpkgs/wine/files' reports wow64 as missing wine-32bit. I think this is just a incorrect warning because programs run fine.)