http://bugs.winehq.org/show_bug.cgi?id=59952 --- Comment #2 from Timothy Paul Lottes <timothylottes@protonmail.com> --- I have been filing bugs I find in Wine as I find them. And while it would be awesome if those bugs got fixed, I don't have any illusions given the number of Wine bugs that exist, and the fact that I'm filing bugs for just one unreleased application, that there is any hope these bugs get fixed any time soon. There are just too many other high priority items to work on. This is a serious request, the one central feature that allows someone to work around Wine bugs is to have a working Linux syscall. I already have a "running in Wine" detector for workaround paths. I don't use these anti-cheat systems that bypass Windows libraries and go direct to Windows syscalls. In fact the majority of Windows applications do not go direct to Windows syscalls. So having a way to force off Wine's trapping of syscalls is a really clean solution to the problem. I have a way to force disable the Wine detection and workaround paths to be more responsible when shipping the Windows binary. And I do a native Linux/etc binary as well. So Wine usage is strictly for development to avoid having to actually run Windows on a day to day basis. As more people try to get off the Windows platform, but still are forced to ship Windows binaries for the majority of customers. You might find more developers like myself trying to move over to Wine. Having this workaround path is very important so we can be unblocked. I also have no problem writing up a description of the Linux system call workarounds that I'd employ in the associated Wine bugs so if someone gets to those, they have some good reference material to work from. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.