http://bugs.winehq.org/show_bug.cgi?id=59680 --- Comment #21 from समीरसिंह Sameer Singh <lumarzeli30@gmail.com> --- (In reply to Vitor Coimbra from comment #20)
First of all, thanks for the very quick work @Sameer Singh!
Glad, I could be of help :)
Also, I'm probably going to need some serious handholding on how to test this, especially given that I'm on NixOS. I'm not super knowledgeable on how to tinker with Wine in general, lol.
I am not at all familiar with NixOS, so I can only give you some general purpose distro steps, you can then maybe adapt them to Nix. 1.First clone and compile the wine repo with the patches. a) Install the required system dependencies by reading this: https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine#satisfying-build-d..., it does not give the specific package names for NixOS, so you have to find it out on your own. Once the build dependencies are installed. b) git clone https://gitlab.winehq.org/wine/wine.git --depth 1 c) cd wine d) wget https://gitlab.winehq.org/wine/wine/-/merge_requests/10859.patch e) wget https://gitlab.winehq.org/wine/wine/-/merge_requests/10868.patch f) git apply 10859.patch g) git apply 10868.patch h) mkdir build && cd build i) ../configure --enable-archs=i386,x86_64 j) make -j$(nproc) Wait for it to compile, this may take some time, On my system with 16 threads it took around 24 minutes to compile. After the compilation is complete: 2. ./wine notepad 3. paste "e๋" in the notepad, the notepad will not crash. If you want to test the patches on "Path of Exile". I am assuming that you are launching the game from steam using Proton Experimental. 4. Copy 32 and 64 bit gdi32.dll from <wine repo path>/build/dlls/gdi32/i386-windows/gdi32.dll (for 32bit) and <wine repo path>/dlls/gdi32/x86_64-windows/gdi32.dll 5. Paste the 32bit dll in "~/.steam/steam/steamapps/common/Proton - Experimental/files/lib/wine/i386-windows" and the 64bit in "~/.steam/steam/steamapps/common/Proton - Experimental/files/lib/wine/x86_64-windows" 6. Launch the game as normal from steam and test. If you face any problem while performing the above steps then you can ask here.
Another thing is that I think it's worth reminding everyone that there's a very good analysis in the GitHub thread linked in the original post (linked here again for convenience: https://github.com/ValveSoftware/Proton/issues/58#issuecomment-4040483961) which goes over causes and possible problematic code locations. Of course there's no guarantee it's a *complete* analysis, but there should still be valuable info in there.
Thanks, I read that and the suggestions are present in the patch. -- 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.