https://bugs.winehq.org/show_bug.cgi?id=46218
--- Comment #12 from Erich E. Hoover erich.e.hoover@gmail.com --- (In reply to Olivier F. R. Dierick from comment #2)
Regression testing is finished.
The issue doesn't occur with wine-staging minus patchset server-Inherited_ACLs.
I double checked and get 100% consistent results.
The patchset contains one patch "server: Inherit security attributes from parent directories on creation. (try 7)" by Erich E. Hoover.
CCing Erich E. Hoover.
Going through email that I should have read sooner...
Okay, what probably is happening here is that the prefix was created without wine-staging and then run with it. The aforementioned patch applies the inheritable security attributes of the parent folder to new children, which is the way SDs are supposed to work.
The security descriptors work best if you don't switch back and forth between regular wine and wine-staging, since wine's default security descriptors can be problematic if copied, but this generally only affects applications that are incredibly picky. It's also possible that the security descriptor for the Cache folder is wrong, which would make it only work if wine-staging _doesn't_ create Cache because later when wine-staging copies its security descriptors then it restricts the children incorrectly.
So, if someone is willing to investigate then I would suggest: 1) create a fresh prefix with wine-staging and try the game with wine-staging 2) create a fresh prefix with regular wine and then try the game with wine-staging 3) create a fresh prefix with wine-staging and try the game with regular wine
Depending on which of these scenarios work then that would narrow down whether the issue is in the security descriptor for Cache or sharing a prefix between regular wine and wine-staging.