May 2026 - Wine-Bugs - list.winehq.org

[Bug 59746] SteelSeries GG 110.0 crashes on startup in .NET System.Security.Cryptography.X509Certificates.CertificateRequest..ctor

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59746 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |d71531e780bb79f8f22bcbc1cce | |08568062c92ed Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- Thanks for the detailed bug report. This one should be fixed by d71531e780bb79f8f22bcbc1cce08568062c92ed. Please open separate bug reports for new problems. -- 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.

May 14, 2026

[Bug 59747] Total War: Shogun 2 needs support for 'vs30_border' entry point

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59747 --- Comment #5 from Zeb Figura <z.figura12(a)gmail.com> --- You should be seeing a file labeled something like "vkd3d-shader-###-vs_3_0-preproc.hlsl". Is that really absent? Can you please attach a log with WINEDEBUG=+d3dcompiler VKD3D_SHADER_DEBUG=trace ? -- 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.

May 14, 2026

[Bug 59732] Custom WinXP/7 app printing garbled from wine 9 onwards

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59732 --- Comment #6 from Rafał Mużyło <galtgendo(a)o2.pl> --- Well, given that 8.8 had a major wineps.drv rework, that's likely what broke. I wonder what corner case your app covers, that hasn't been stumbled upon for all that time elsewhere... (8.13 doesn't have anything labeled 'crash fix', but one of the psdrv commits fixes a potential div by zero, so perhaps...) So, a 'psdrv' log from 8.8 and 8.13 each, if you don't mind, given that only you have access to the app. -- 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.

May 14, 2026

[Bug 59749] New: sapi: ISpVoice::SetPriority and GetStatus return E_NOTIMPL, breaking Overwatch 2 Audio Captions (and likely any SAPI app that polls status or checks SetPriority's HRESULT)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59749 Bug ID: 59749 Summary: sapi: ISpVoice::SetPriority and GetStatus return E_NOTIMPL, breaking Overwatch 2 Audio Captions (and likely any SAPI app that polls status or checks SetPriority's HRESULT) Product: Wine Version: 11.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: sapi Assignee: wine-bugs(a)list.winehq.org Reporter: bohdan(a)tkachenko.dev Distribution: --- dlls/sapi/tts.c has three ISpVoice methods still stubbed out with FIXME(...stub...); return E_NOTIMPL; - spvoice_SetPriority (line 1231) - spvoice_GetPriority (line 1238) - spvoice_GetStatus (line 1212) SetPriority and GetStatus are both on the hot path for Overwatch 2's "Audio Captions" accessibility TTS feature (Steam AppID 2357570, runs under Proton - which ships unmodified upstream Wine SAPI). They cause two distinct failure modes: 1. During voice setup, OW2 calls ISpVoice::SetPriority(SPVPRI_NORMAL) and checks the HRESULT. E_NOTIMPL makes it abort TTS init entirely - PLAY SAMPLE produces silence and the in-game UI gives no error. 2. If SetPriority is forced to return S_OK (verified by binary-patching the stub), the engine successfully synthesizes the first sample. The game then calls ISpVoice::Speak(text, SPF_ASYNC, ...) and tight-polls ISpVoice::GetStatus waiting for SPVOICESTATUS.dwRunningState == SPRS_DONE. Stock GetStatus returns E_NOTIMPL and writes nothing into the status struct, so the game polls forever and subsequent PLAY SAMPLE clicks silently do nothing. Other SAPI apps that use Speak(SPF_DEFAULT) or Speak(SPF_ASYNC) + WaitUntilDone(INFINITE) never hit these methods and work fine on stock Wine, which is why this hasn't been reported before despite the stubs being old. OW2's accessibility code is unusually defensive. Steps to reproduce ================== 1. Install Wine 11.8+ (or any current Proton - same upstream code: ValveSoftware/wine branch proton_11.0 dlls/sapi/tts.c is byte-identical to wine-mirror/wine master, MD5 verified). 2. Install Overwatch 2 (free-to-play, Steam AppID 2357570) - or any SAPI app that checks SetPriority's HRESULT. 3. In game settings -> Accessibility, enable Audio Captions and select a Proton voice (e.g. "Proton Voice - English (United States) - LIBRITTS-R 14"). 4. Click PLAY SAMPLE. Actual: silence; in-game UI gives no error. With WINEDEBUG=+sapi: spvoice_SetVoice -> picks ProtonTTS_libritts-r_3 spvoice_SetOutput(NULL) -> default audio out spvoice_SetRate(3) -> S_OK spvoice_SetVolume(100) -> S_OK spvoice_SetPriority(0) -> STUB -> E_NOTIMPL [BUG #1] spvoice_Release -> game gives up here After binary-patching SetPriority to return S_OK: spvoice_Speak(text, SPF_ASYNC=1) -> audio plays once loop: spvoice_GetStatus(&status, NULL) -> STUB -> E_NOTIMPL, status untouched ... [BUG #2 - tight poll forever] Expected: PLAY SAMPLE plays the voice sample, and the button works again on every subsequent click. Workaround: binary-patch the two E_NOTIMPLs, or use a locally-built Wine with the patches below. Fix === A patch is being prepared for wine-devel implementing all three methods plus tests. Sketch: - SetPriority/GetPriority: store value on struct speech_voice, validate against SPVPRI_NORMAL/ALERT/OVER. - GetStatus: populate SPVOICESTATUS from cur_stream_num (last queued), a new last_stream_num/last_hr updated in speak_proc, and async_wait_queue_empty(&queue, 0) for dwRunningState. Patch verified against Wine's existing dlls/sapi/tests/ suite (new tests added) and end-to-end in OW2: both PLAY SAMPLE clicks play correctly with no wedge. -- 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.

May 14, 2026

[Bug 59739] Ability to set theme for all prefixes easily

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59739 --- Comment #25 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to fatihbakal7 from comment #24) > Everything you say makes sense here until the last part. Who ever stored > themes in .cache?? ~/.cache meant as arbitrary example based on existing directory where wine may dump files and not meant to suggest it as an actual path to be used: /home/any/.cache/wine: -rw-rw-r-- 1 any any 53M May 12 09:05 wine-gecko-2.47.4-x86.msi -rw-rw-r-- 1 any any 82M Oct 14 2025 wine-mono-10.2.0-x86.msi -rw-rw-r-- 1 any any 82M Nov 4 2025 wine-mono-10.3.0-x86.msi -rw-rw-r-- 1 any any 82M Dec 4 05:15 wine-mono-10.4.0-x86.msi -rw-rw-r-- 1 any any 83M Mar 13 05:33 wine-mono-11.0.0-x86.msi -rw-rw-r-- 1 any any 80M May 6 15:57 wine-mono-11.1.0-x86.msi -- 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.

May 13, 2026

[Bug 59739] Ability to set theme for all prefixes easily

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59739 --- Comment #24 from fatihbakal7(a)protonmail.com --- > Does this mean you typically use Steam app to manage and launch games? Sorta? I use heroic games launcher most of the time and sometimes steam. > My experience is oriented around dev/testing vs player with plain vanilla > wine always the primary target platform. I use GE-Proton without Steam for > testing Steam-like behavior when necessary but run via command line like > vanilla wine. I use ge-proton with heroic games launcher > Therefore if users are dependent upon launchers for managing themes then > indeed it may be less convenient for them to have to set for every game if a > global theme setting is not offered by their tools. In that case a shared > path such as ~/.cache may provide a valid solution. Everything you say makes sense here until the last part. Who ever stored themes in .cache?? > Unclear if global theme override would conflict with any game prefix > specific settings such as if similar support was added for global version > override that conflicts with game specific version and how that should be > resolved. I mean it'd just be a .reg/.msstyle/.theme file that will be imported and I don't think that can break things. Even if it did it wouldn't be groundbreaking. > I'm not aware of Proton setting any specific themes per game prefix so maybe > other's have more insight into whether that might be an issue. They all use the default theme just like wine. And just like wine you gotta set it yourself to each prefix. -- 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.

May 13, 2026

[Bug 59680] Path of Exile: font rendering related crash

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59680 --- Comment #27 from Vitor Coimbra <vitorcoliveira91(a)gmail.com> --- (In reply to समीरसिंह Sameer Singh from comment #26) > Is the mark rendered when the game is run on Windows? Unfortunately, I don't have a Windows machine to confirm that, so I asked in the global chat if anyone can see it and a couple of people replied "yes", so while it's not certain (they may have been trolling after all), it's very likely to be rendering for them. -- 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.

May 13, 2026

[Bug 59680] Path of Exile: font rendering related crash

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59680 --- Comment #26 from समीरसिंह Sameer Singh <lumarzeli30(a)gmail.com> --- (In reply to Vitor Coimbra from comment #25) > Wait, nevermind, I got it. NixOS can apply patches from its own > configuration file using overlays, I just had to figure out how to do that. > The patches technically were applied to the 11.8 release rather than master, > but I don't think that's gonna change much anyway. I think. > > Once again it took a bit to build it from scratch one more, but I was > finally able to run it. So, I did the following tests: > > 1) wine notepad > > Pasted "e๋" into edit area, no crash. > > 2) wine sublime_text > > Pasted "e๋" into "File name..." input field. Also no crash. Typing normal > characters into the edit area seemed to make the program hang though. Not > sure if it's something on my system. > > 3) Copied the dlls to Proton - Experimental's i386 and x86_64 directories > and booted up Path of Exile. Pasted "e๋" into chat and did not crash. It > didn't seem to render the mark though, which is a bit strange. But > regardless, the crashes seem to be fixed at least. Is the mark rendered when the game is run on Windows? -- 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.

May 13, 2026

[Bug 59739] Ability to set theme for all prefixes easily

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59739 --- Comment #23 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to fatihbakal7 from comment #22) > > Some games run differently depending on the windows versions set as > > described here: https://bugs.winehq.org/show_bug.cgi?id=44675#c15 > > I've been gaming on linux for about 6 years now and this is the first time > hearing about this. I've played countless of games and sometimes I had to > install components like dotnet and what not but even that was pretty rare. > (Umu wasn't a thing for most of the those 6 years) > > That being said there's stuff like umu-fixes which apply changes like these > automatically. I know umu is for proton and when a game required a specific > fix (e.g. version change or installing a dependency) wine users would have > to run it themselves anyways (I don't think there's something like > umu-protonfixes (https://github.com/Open-Wine-Components/umu-protonfixes) > that auto apply fixes for games for plain wine so I don't think I'm wrong on > this. > > A theme isn't exactly a fix so both users of wine & proton would have to run > that manually per prefix. Which I believe is enough to justify this. Thanks for more background on your gaming experience. Does this mean you typically use Steam app to manage and launch games? My experience is oriented around dev/testing vs player with plain vanilla wine always the primary target platform. I use GE-Proton without Steam for testing Steam-like behavior when necessary but run via command line like vanilla wine. Therefore if users are dependent upon launchers for managing themes then indeed it may be less convenient for them to have to set for every game if a global theme setting is not offered by their tools. In that case a shared path such as ~/.cache may provide a valid solution. Unclear if global theme override would conflict with any game prefix specific settings such as if similar support was added for global version override that conflicts with game specific version and how that should be resolved. I'm not aware of Proton setting any specific themes per game prefix so maybe other's have more insight into whether that might be an issue. -- 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.

May 13, 2026

[Bug 59680] Path of Exile: font rendering related crash

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59680 --- Comment #25 from Vitor Coimbra <vitorcoliveira91(a)gmail.com> --- Wait, nevermind, I got it. NixOS can apply patches from its own configuration file using overlays, I just had to figure out how to do that. The patches technically were applied to the 11.8 release rather than master, but I don't think that's gonna change much anyway. I think. Once again it took a bit to build it from scratch one more, but I was finally able to run it. So, I did the following tests: 1) wine notepad Pasted "e๋" into edit area, no crash. 2) wine sublime_text Pasted "e๋" into "File name..." input field. Also no crash. Typing normal characters into the edit area seemed to make the program hang though. Not sure if it's something on my system. 3) Copied the dlls to Proton - Experimental's i386 and x86_64 directories and booted up Path of Exile. Pasted "e๋" into chat and did not crash. It didn't seem to render the mark though, which is a bit strange. But regardless, the crashes seem to be fixed at least. -- 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.

May 13, 2026

[Bug 59747] Total War: Shogun 2 needs support for 'vs30_border' entry point

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59747 --- Comment #4 from Andrey Gusev <andrey.goosev(a)gmail.com> --- (In reply to Zeb Figura from comment #3) > Can you please attach all of the shaders dumped by setting > VKD3D_SHADER_DUMP_PATH? See shader attachment in comment 1. Dumped just one file. As I said before the only difference is in prefix of .hlsl file - vs_3_0 for DX9 and vs_4_0 for DX11. Source is identical. -- 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.

May 13, 2026

[Bug 59680] Path of Exile: font rendering related crash

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59680 --- Comment #24 from समीरसिंह Sameer Singh <lumarzeli30(a)gmail.com> --- (In reply to Vitor Coimbra from comment #23) > (In reply to समीरसिंह Sameer Singh from comment #21) > > 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- > > dependencies, 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) > > Thank you for the very thorough instructions. If anyone else wants to test > this on NixOS, step a) is basically the following command: > > nix-shell -p wine64Packages.stagingFull.nativeBuildInputs > wine64Packages.stagingFull.buildInputs > winePackages.stagingFull.nativeBuildInputs > winePackages.stagingFull.buildInputs wget git > > This will pull in all dependencies needed to build wine 32 and 64 bits (as > well as wget and git) straight from the nixpkgs repo into a nix-shell > session. Then just follow the rest of the instructions as written. > > Ok, so after waiting quite a while for wine to build (I don't have a good > computer), I tried running the following test (from the build directory > created by the above instructions): > > 1) ./wine programs/notepad/i386-windows/notepad.exe > > but was met with the following output: > > [nix-shell:~/wine/build]$ ./wine programs/notepad/i386-windows/notepad.exe > wine: created the configuration directory '/home/vitorc/.wine' > 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly > L"Microsoft.Windows.Common-Controls" (6.0.0.0) > Wine cannot find the FreeType font library. To enable Wine to > use TrueType fonts please install a version of FreeType greater than > or equal to 2.0.5. > http://www.freetype.org > Wine cannot find the FreeType font library. To enable Wine to > use TrueType fonts please install a version of FreeType greater than > or equal to 2.0.5. > http://www.freetype.org > 004c:fixme:actctx:parse_depend_manifests Could not find dependent assembly > L"Microsoft.Windows.Common-Controls" (6.0.0.0) > 0054:fixme:actctx:parse_depend_manifests Could not find dependent assembly > L"Microsoft.Windows.Common-Controls" (6.0.0.0) > Wine cannot find the FreeType font library. To enable Wine to > use TrueType fonts please install a version of FreeType greater than > or equal to 2.0.5. > http://www.freetype.org > Wine cannot find the FreeType font library. To enable Wine to > use TrueType fonts please install a version of FreeType greater than > or equal to 2.0.5. > http://www.freetype.org > 004c:err:vulkan:vulkan_init_once Failed to load libvulkan.so.1 > 004c:err:wgl:egl_init Failed to load libEGL.so.1: libEGL.so.1: cannot open > shared object file: No such file or directory > 004c:err:wgl:X11DRV_OpenGLInit Failed to load libGL: libGL.so.1: cannot open > shared object file: No such file or directory > 004c:err:wgl:X11DRV_OpenGLInit OpenGL support is disabled. > 0054:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr > 0x80004002 > 0054:err:ole:CoMarshalInterface Failed to marshal the interface > {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 > 0054:err:ole:apartment_get_local_server_stream Failed: 0x80004002 > 0054:err:ole:start_rpcss Failed to open RpcSs service > 004c:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr > 0x80004002 > 004c:err:ole:CoMarshalInterface Failed to marshal the interface > {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 > 004c:err:ole:apartment_get_local_server_stream Failed: 0x80004002 > Wine cannot find the FreeType font library. To enable Wine to > use TrueType fonts please install a version of FreeType greater than > or equal to 2.0.5. > http://www.freetype.org > 0094:err:winediag:gnutls_process_attach failed to load libgnutls, no support > for encryption > 0094:err:winediag:process_attach failed to load libgnutls, no support for > pfx import/export > Wine cannot find the FreeType font library. To enable Wine to > use TrueType fonts please install a version of FreeType greater than > or equal to 2.0.5. > http://www.freetype.org > 009c:err:winediag:gnutls_process_attach failed to load libgnutls, no support > for encryption > 009c:err:syslink:SYSLINK_SetFont Failed to create link font! > > Upon further reflecting on why this could be happening, I'm guessing it > could be FHS related, since NixOS does not follow it. wine is probably > looking for runtime stuff in places it won't be in. Again, just a guess > though. If this is indeed an FHS issue, then have you tried building an FHS environment with all the runtime libraries wine needs, to run wine from? See: https://ryantm.github.io/nixpkgs/builders/special/fhs-environments/ -- 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.

May 13, 2026

[Bug 59680] Path of Exile: font rendering related crash

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59680 --- Comment #23 from Vitor Coimbra <vitorcoliveira91(a)gmail.com> --- (In reply to समीरसिंह Sameer Singh from comment #21) > 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- > dependencies, 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) Thank you for the very thorough instructions. If anyone else wants to test this on NixOS, step a) is basically the following command: nix-shell -p wine64Packages.stagingFull.nativeBuildInputs wine64Packages.stagingFull.buildInputs winePackages.stagingFull.nativeBuildInputs winePackages.stagingFull.buildInputs wget git This will pull in all dependencies needed to build wine 32 and 64 bits (as well as wget and git) straight from the nixpkgs repo into a nix-shell session. Then just follow the rest of the instructions as written. Ok, so after waiting quite a while for wine to build (I don't have a good computer), I tried running the following test (from the build directory created by the above instructions): 1) ./wine programs/notepad/i386-windows/notepad.exe but was met with the following output: [nix-shell:~/wine/build]$ ./wine programs/notepad/i386-windows/notepad.exe wine: created the configuration directory '/home/vitorc/.wine' 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. http://www.freetype.org Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. http://www.freetype.org 004c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0054:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. http://www.freetype.org Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. http://www.freetype.org 004c:err:vulkan:vulkan_init_once Failed to load libvulkan.so.1 004c:err:wgl:egl_init Failed to load libEGL.so.1: libEGL.so.1: cannot open shared object file: No such file or directory 004c:err:wgl:X11DRV_OpenGLInit Failed to load libGL: libGL.so.1: cannot open shared object file: No such file or directory 004c:err:wgl:X11DRV_OpenGLInit OpenGL support is disabled. 0054:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002 0054:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 0054:err:ole:apartment_get_local_server_stream Failed: 0x80004002 0054:err:ole:start_rpcss Failed to open RpcSs service 004c:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002 004c:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 004c:err:ole:apartment_get_local_server_stream Failed: 0x80004002 Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. http://www.freetype.org 0094:err:winediag:gnutls_process_attach failed to load libgnutls, no support for encryption 0094:err:winediag:process_attach failed to load libgnutls, no support for pfx import/export Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. http://www.freetype.org 009c:err:winediag:gnutls_process_attach failed to load libgnutls, no support for encryption 009c:err:syslink:SYSLINK_SetFont Failed to create link font! Upon further reflecting on why this could be happening, I'm guessing it could be FHS related, since NixOS does not follow it. wine is probably looking for runtime stuff in places it won't be in. Again, just a guess though. -- 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.

May 13, 2026

[Bug 59739] Ability to set theme for all prefixes easily

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59739 --- Comment #22 from fatihbakal7(a)protonmail.com --- > Some games run differently depending on the windows versions set as > described here: https://bugs.winehq.org/show_bug.cgi?id=44675#c15 I've been gaming on linux for about 6 years now and this is the first time hearing about this. I've played countless of games and sometimes I had to install components like dotnet and what not but even that was pretty rare. (Umu wasn't a thing for most of the those 6 years) That being said there's stuff like umu-fixes which apply changes like these automatically. I know umu is for proton and when a game required a specific fix (e.g. version change or installing a dependency) wine users would have to run it themselves anyways (I don't think there's something like umu-protonfixes (https://github.com/Open-Wine-Components/umu-protonfixes) that auto apply fixes for games for plain wine so I don't think I'm wrong on this. A theme isn't exactly a fix so both users of wine & proton would have to run that manually per prefix. Which I believe is enough to justify this. -- 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.

May 13, 2026

[Bug 57980] Adobe Creative Cloud requires unimplemented function KERNEL32.dll.SetThreadpoolTimerEx

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=57980 mirh <mirh(a)protonmail.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh(a)protonmail.ch -- 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.

May 13, 2026

[Bug 59747] Total War: Shogun 2 needs support for 'vs30_border' entry point

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59747 --- Comment #3 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Andrey Gusev from comment #2) > Created attachment 80929 [details] > preproc > > It just shows a splash screen for about 5 seconds and then crashes. Can you please attach all of the shaders dumped by setting VKD3D_SHADER_DUMP_PATH? -- 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.

May 13, 2026

[Bug 59732] Custom WinXP/7 app printing garbled from wine 9 onwards

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59732 --- Comment #5 from hascc <hugoac2004(a)gmail.com> --- Hello, I've tested wine-devel from 8.1 onwards on a fresh bookworm / daedalus. The results up to now are: * Wine-devel up to 8.7 "prints" that particular report perfectly. * Wine-devel from 8.8 to 8.12 crashes / does segmentation fault when trying to print that report. * Wine-devel 8.13 prints without crashing, but it prints the "garbled" way. -- 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.

May 13, 2026

[Bug 59739] Ability to set theme for all prefixes easily

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59739 --- Comment #21 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to fatihbakal7 from comment #19) > is that you'd have to run something once per prefix in both cases. > Which most users + launcher (heroic/lutris) developers won't be willing to > do. Some games run differently depending on the windows versions set as described here: https://bugs.winehq.org/show_bug.cgi?id=44675#c15 Currently I test these version variations by always prefixing game launching command with `winecfg /v win10;` Do users & devs already have to change versions for some game prefixes to run as expected? If so then having to run something extra to set themes per prefix seems the same. Many games work for default win10 but plenty are buggy for win10 and require win8 or earlier to be set which requires changing the version. -- 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.

May 13, 2026

[Bug 59739] Ability to set theme for all prefixes easily

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59739 --- Comment #20 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to fatihbakal7 from comment #19) > I said .local/share I meant XDG_DATA_HOME. Isn't by that logic ~/.cache/wine > also hardcoded? > > The command approach will hit the same thing as it is right now. > > The deal is that you'd have to run something once per prefix in both cases. > Which most users + launcher (heroic/lutris) developers won't be willing to > do. Thanks for clarifying the problem assumes users + launcher won't be willing to run extra theme setting commands while launching games. This explains what you consider "too much of a hassle." > I think they knew the goal with that clearly so there was no need to explain > anything. There's no way they don't know what xdg does/is considering > there's already xdg related stuff for Downloads/Documents etc.. so I don't > think it would've made any differnece As @dösinger mentioned for XDG PR, it wasn't clear what problem you were trying to actually solve other than conform to XDG: And to add an unspoken concern: What exact problem are you solving, and are you sure you are not just replacing it with different issues. As with @sivov recommendation, if devs/users aren't willing to script extra commands considered "too much of a hassle" for convenience then perhaps a proposal to reuse existing ~/.cache may be valid. Although the problem hardly seems that major to not be solved easily via existing available solutions. -- 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.

May 13, 2026

[Bug 59739] Ability to set theme for all prefixes easily

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59739 --- Comment #19 from fatihbakal7(a)protonmail.com --- > hard-coded path changes I said .local/share I meant XDG_DATA_HOME. Isn't by that logic ~/.cache/wine also hardcoded? > Motive and value of XDG MR was not clarified I think they knew the goal with that clearly so there was no need to explain anything. There's no way they don't know what xdg does/is considering there's already xdg related stuff for Downloads/Documents etc.. so I don't think it would've made any differnece > As @dösinger mentioned, theme handling involves multiple options that are > probably better handled via existing winecfg logic extended with additional > theme command options vs environment variables to handle various options > that may need to be supported. The command approach will hit the same thing as it is right now. Right now you can just do; WINEPREFIX=/path/to/pfx wine/umu-run regedit /path/to/theme.reg and with that winecfg command pr merged it'd just be WINEPREFIX=/path/to/pfx winecfg /t /path/to/theme.reg/.msstyle/.style The deal is that you'd have to run something once per prefix in both cases. Which most users + launcher (heroic/lutris) developers won't be willing to do. -- 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.

May 13, 2026

[Bug 59747] Total War: Shogun 2 needs support for 'vs30_border' entry point

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59747 --- Comment #2 from Andrey Gusev <andrey.goosev(a)gmail.com> --- Created attachment 80929 --> http://bugs.winehq.org/attachment.cgi?id=80929 preproc It just shows a splash screen for about 5 seconds and then crashes. -- 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.

May 13, 2026

[Bug 59739] Ability to set theme for all prefixes easily

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59739 --- Comment #18 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to fatihbakal7 from comment #15) > I don't think you realize that he meant that about the xdg PR. We were word > on a theme PR by upstream people. The xdg and that theme prs are completely > seperate so just keep that in mind. I hope we get some feedback on the theme > stuff soon I realize @julliard's response was for XDG PR but consider it likely to apply regarding hard-coded path changes suggested here. Motive and value of XDG MR was not clarified and path changes suggested here seemed related so I extrapolated based on conclusions there. As @dösinger mentioned, theme handling involves multiple options that are probably better handled via existing winecfg logic extended with additional theme command options vs environment variables to handle various options that may need to be supported. -- 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.

May 13, 2026

[Bug 59739] Ability to set theme for all prefixes easily

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59739 --- Comment #17 from Nikolay Sivov <bunglehead(a)gmail.com> --- I don't think we'll get more variables for such comparatively minor configuration option. Configured theme path is stored in the registry, if you need to resolve unix to windows path we have winepath program for that. So to me it looks like we have everything to script such changes. -- 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.

May 13, 2026

[Bug 59739] Ability to set theme for all prefixes easily

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59739 --- Comment #16 from fatihbakal7(a)protonmail.com --- (In reply to Stian Low from comment #14) > (In reply to Stefan Dösinger from comment #13) > > One thing worth contemplating is what other settings might be useful to > > expose in a similar way. > > Agreed. So far my patch only considers extending to support theme settings > via command line. This paired with something like WINEGLOBALTHEME=1 (makes it use the global theme from .config/ would be the way to go imo. Time will tell what Alexandre or other maintainers will be willing to merge. -- 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.

May 13, 2026

[Bug 59745] Wine crashes when a custom window is created to show information

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59745 Matthias Zorn <matthias0178+wine(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |testcase -- 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.

May 13, 2026