Linux/Proton: A call to an OS function failed

[itsdnoftheworld]

Hello, I have been having an annoying issue running Dyndolod 3 on my Proton setup related to texconv. While running Dyndolod after successfully generating xlodgen and texgen, I am unable to proceed with generating Dyndolod, as I eventually get a message saying "Could not execute "Z:\home\dillon\Games\DynDOLOD\Edit Scripts\Texconvx64.exe" -nologo -gpu 0 -y -m 1 -aw 256 -f R8G8B8A8_UNORM -o "C:\users\steamuser\Temp\DynDOLOD_SSE" "C:\users\steamuser\Temp\DynDOLOD_SSE\379794EC272A4EF98BAF93F0B0726085.dds". Then I get a pop-up about Call to an OS Function Failed. No .esp is mentioned.

Since I am on Linux, I don't have UAC or AV on my computer, and after changing permissions of some of the folders, specifically my game folder, mods folder, and the Dyndolod folder I have been able to run it once or twice. However, after changing a texture mod, I have been completely unable to get around this Texconv issue. I believe that Texconv should be running, since I can see it in the task manager and I can see some .dds files being converted. I also was able to run texgen and xlodgen with no issue. In fact I have run Dyndolod successfully earlier today! I have tried placing Dyndolod folder in both my Z: drive (the native Linux system) and my C: drive (the emulated Windows drive), and both run into the same error. I also reinstalled and repaired dotnet and C++, and I was able to run texconv (the official one from Github) with the below output. I also was able to convert images into .dds from the command line. However I could not replicate this with the one downloaded alongside Dyndolod. Is this expected behavior?

I am currently unable to test on Windows since my install is all messed up, but I am just looking to see if there is anything I have missed in troubleshooting. Any advice would be greatly appreciated.
 

Bug Report: https://pastebin.com/B3Te9XG4

SSE Log: https://paste.ee/p/Hhg78

Texconv Test: https://paste.ee/p/6vtVc

[MagneticIce]

I myself have been carrying out a fair amount of testing around the "A call to an OS function failed" error so I figured I would share my findings.

Firstly, this is specifically an issue with Texconv and as such it also effects other software that uses Texconv such as Wabbajack.

Secondly, this error only occurs on versions of wine with the staging patches applied to it (i.e. wine-staging, proton etc.). The basic version of wine without the staging patches can be used to run both Texconv and Dyndolod without issue (at least as of wine version 9.22).

Thirdly, it seems like this error may only occur on specific distributions of Linux but I haven't done enough testing to confirm this.

Fourthly, this error occurs at random. I tried running Texconv on the same texture file over 200,000 times using a bash script and found that, with a probability of around 1 in 4000, Texconv would fail and would not produce any output. When Texconv failed, the following attempt to run Texconv always succeeded so I suppose one failure doesn't affect the odds of another failure occurring.