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

[Bug 56565] New: Command and Conquer 3 Tiberium Wars installer crashes
by WineHQ Bugzilla July 22, 2026

July 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=56565 Bug ID: 56565 Summary: Command and Conquer 3 Tiberium Wars installer crashes Product: Wine Version: 9.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- Split from bug #53561. This bug is about a crash / hang in the installer for the retail release of Command and Conquer 3 Tiberium Wars when used with the recommended installation type. (The advanced installation type is unusable under Wine, see the original bug #53561.) After clicking on the next button on the installation type screen, installer appears to try and copy files. This is supposed to have a progress indicator that fills up, but it gets drawn in wine as completely full, with status "Copying new files". The UI has stopped updating and placing another window (Wine or from the host's WM) over it will cause graphical corruption. After about a minute on my machine, the UI window disappears entirely. The msiexec process however is still running in the background, and can be seen on the task bar if wine is running with a virtual desktop. It is also still visible in wine's taskmgr.exe. Where it shows two msiexec processes and one unnamed 32bit process. (Wine's taskmgr shows "*32" for the process name.) After this the process does not exit unless killed. Doing so kills both msiexec processes and the unnamed 32bit process. Looking through the registry after killing the installer, we find that it did create the needed registry keys expected by the game, in addition to installing the games files at the expected default location. The game does run in this state. So it appears that the installation was successful, despite the bug. Running the installer with WINEDEBUG="+msi" causes the installer to run correctly. I.e. It doesn't crash / hang indefinitely. Although, the UI still stops updating while the files are copied, it will recover in this case and allow the installer to run to completion. With the user able to exit the installer normally. WINEDEBUG="+msi" log attached. -- 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.

2 6

[Bug 55011] New: Cuda-application M/WarpEM got stuck or crashes in wine-staging/7.21, wine/8.9+nvidia-libs
by WineHQ Bugzilla July 22, 2026

July 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=55011 Bug ID: 55011 Summary: Cuda-application M/WarpEM got stuck or crashes in wine-staging/7.21, wine/8.9+nvidia-libs Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: nvcuda Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- M of WarpEM gets stuck very early and eventually crashes. The following steps are needed to reproduce this: 1) install WarpEM according to [1] into wine-staging between v7.17 and v7.21, or wine-8.9 with nvidia-libs. (do not try with wine-staging 7.22 or later, because that has cuda support disabled). This has been testing this with "Shared WoW64" configuration of Wine. Trying to use Wine with the "new WoW64 approach" using -enable-archs=i386,x86_64 did also not work for me, because it failed much earlier when trying to install Cuda/WarpEM. 2) Data (5.5TB!) for testing is available from here [1]. Download and unpack Warpem_test.tar.gz to a directory that is accessible from wine. The screenshots Step1-7 should help to understand how M is supposed to be used. 3) Start M.exe. In my case, I do this ulimit -s 655360 wine $WINEPREFIX/drive_c/Warp/M.exe or vglrun wine $WINEPREFIX/drive_c/Warp/M.exe 4) Within M, do the following steps (see also Step1-7 in [2]): - Step 1: In the GUI window click "LOAD EXISTING FROM FILE" - Step 2: select ...\M_j33\Gag_c2_processing.population - Step 3: Upper right corner Refine button. - Step 4: Click refine - Step 5+6: workers are now testing the memory - Step 7: Eventually (after several minutes), one of the works crash, and there is no further progress. On Windows, this finishes and a new screen appears for the next step. This is not the case here. It gets stuck, and and eventually I stopped wine with <ctrl-C>. A log file is also available [2], but it is too large (1.1 GB) to be included here. If you have suggestions with WINEDEBUG filter should be used, let me know. [1] https://appdb.winehq.org/objectManager.php?sClass=version&iId=40620&iTestin… [2] https://pub.ista.ac.at/~schloegl/warpem-test-data/ -- 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.

2 5

[Bug 54197] New: cuda-z and warpem fail in wine-staging 7.22 and later
by WineHQ Bugzilla July 22, 2026

July 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=54197 Bug ID: 54197 Summary: cuda-z and warpem fail in wine-staging 7.22 and later Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- Created attachment 73728 --> https://bugs.winehq.org/attachment.cgi?id=73728 screenshot of running cuda-z one wine-staging 7.22 cuda-z fails to run in wine-staging 7.22 and later. It reports the error "CUDA not found. Please update the nvidia-driver.". cuda-z runs fine under wine-staging 7.21 (and earlier) on the same machine with the same nvidia driver. The application "WarpEM" can be also not used anymore because it does not find any GPU. I suspect that disabling the nvcuda-support patches in wine-staging [1] is the reason for this breakage. I believe bug #54102 is related, but the bug report says that this occured already in v7.21. But this issue is not reproducible to me in 7.21 only in 7.22. [1] https://gitlab.winehq.org/wine/wine-staging/-/commit/6c3797b3e8dba19698328c… [2] https://bugs.winehq.org/show_bug.cgi?id=54102 -- 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.

2 5

[Bug 52528] New: cuda 10.0 and 10.2 installation fails with "err:ole:CoRevokeClassObject COM was not initialized"
by WineHQ Bugzilla July 22, 2026

July 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=52528 Bug ID: 52528 Summary: cuda 10.0 and 10.2 installation fails with "err:ole:CoRevokeClassObject COM was not initialized" Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- When trying to get warpem http://www.warpem.com/warp/?page_id=65 running, I'm trying to install cuda 10.0 or 10.2, according to these instructions https://gist.github.com/imaami/37105333c0d16210b2cac9d4032155aa on Wine-7.0 (stable), wine 7.1 (devel), and wine 7.1 (Staging). Staging provides some version of cuda, but the application crashes; a possibile reason is Cuda version mismatch. The installation procedure of Cuda 10.x proceedes quite far, but fails at the end always with .... .... 0138:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0138:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0140:fixme:ole:CoInitializeSecurity 00000000, -1, 00000000, 00000000, 0, 3, 00000000, 0, 00000000 stub 0138:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFA, 0032FEAC 0138:err:ole:CoRevokeClassObject COM was not initialized Because I was not sure whether the important parts are installed, I tested with Cuda-Z, too. But Cuda-Z does not recognize the GPU's, in "stable" and "devel" (with "Staging" the gpu is recognized) The host system is Debian11, and two GTX 1080Ti cards, nvidia-driver/libcuda1 460.91. I tested Cuda 10.0 as well as Cuda10.2. In order reproduce this issue, You need to run these commands: URL_100=https://developer.nvidia.com/compute/cuda/10.0/Prod/local_installer… URL_102=http://developer.download.nvidia.com/compute/cuda/10.2/Prod/local_i… wget -nc $URL_100 wget -nc $URL_102 wineboot -i winetricks msxml3 winetricks win10 wineconsole cmd.exe /c "$(basename $URL_100)" -s \ {cu{dart,objdump,pti},nv{cc,prune,disasm,prof,ml_dev},memcheck, \ {cu{blas,fft,rand,solver,sparse},nvgraph,npp,nvrtc}{,_dev}}_10.0 wineconsole cmd.exe /c "$(basename $URL_102)" -s \ {cu{dart,objdump,pti},nv{cc,prune,disasm,prof,ml_dev},memcheck, \ {cu{blas,fft,rand,solver,sparse},nvgraph,npp,nvrtc}{,_dev}}_10.2 -- 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.

2 6

[Bug 58247] New: ABNT Keyboard Not Working Properly in Wine with Wayland Driver
by WineHQ Bugzilla July 21, 2026

July 21, 2026

http://bugs.winehq.org/show_bug.cgi?id=58247 Bug ID: 58247 Summary: ABNT Keyboard Not Working Properly in Wine with Wayland Driver Product: Wine Version: 10.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: xnep1(a)hotmail.com Distribution: --- Created attachment 78588 --> http://bugs.winehq.org/attachment.cgi?id=78588 Tracefile with winedebug=keyboard,key showing "/" not working When running Wine applications using the Wayland driver, certain keys on the Brazilian ABNT2 keyboard (such as the slash /, question mark ?, and other special characters) do not function correctly. These keys either generate no character. In contrast, when using the X11 driver (wine X11), the same keys function as expected, and the correct characters are produced. Upon inspection, the scan codes received under Wayland are extended (e.g., 0x259 instead of 0x59 for the slash key), which seems to lead to incorrect mapping or interpretation by Wine. This issue appears to stem from incomplete or incorrect handling of extended scan codes or keyboard layout mapping for the br-abnt2 layout in the Wayland input. In my tests, I forced the correct scan code for the slash key (0x59), and after this adjustment, the key started working properly again. I have attached a trace log file showing the key input events during the failure. Although I am currently using a modified version of Wine to generate this trace, the problem also occurs on the stable Wine release. (It's late and I'm not going to redo the test just to have a clean trace file. Sorry.) -- 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.

2 7

[Bug 59226] New: unimplemented function msvcp140_atomic_wait.dll.__std_tzdb_get_sys_info using the STL
by WineHQ Bugzilla July 21, 2026

July 21, 2026

http://bugs.winehq.org/show_bug.cgi?id=59226 Bug ID: 59226 Summary: unimplemented function msvcp140_atomic_wait.dll.__std_tzdb_get_sys_info using the STL Product: Wine Version: 10.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)list.winehq.org Reporter: winehq-bugzilla(a)asdff45.de Distribution: --- Created attachment 80130 --> http://bugs.winehq.org/attachment.cgi?id=80130 wine output when running the mentioned C++ code Using std::chrono::time_zone::to_local causes unhandled exception. Unhandled exception: unimplemented function msvcp140_atomic_wait.dll.__std_tzdb_get_sys_info called in 64-bit code (0x006fffffbfd817). The code i used to test this: #include <iostream> #include <chrono> int main() { std::cout << std::format("Encountered on: {:%F %T}", std::chrono::floor<std::chrono::seconds>(std::chrono::current_zone()->to_local(std::chrono::system_clock::now()))) << std::endl; return 0; } The crash happens in "to_local" which calls "_Get_info" which calls "__std_tzdb_get_sys_info". -- 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.

1 2

[Bug 45104] New: OOB read in gdiplus
by wine-bugs＠winehq.org July 21, 2026

July 21, 2026

https://bugs.winehq.org/show_bug.cgi?id=45104 Bug ID: 45104 Summary: OOB read in gdiplus Product: Wine Version: 3.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: robert.gawlik(a)rub.de Distribution: --- Original submitted report can be found here: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1764719 (*) Out-of-bounds read in dlls/gdiplus/metafile.c:2528 (last commit: dd2624a24fba400bf59b9396e496d16c43d399d9): The parameters data, dataSize and recordType are completely user controlled and flow into a memcpy() call in line 2528. If the length of data is less than dataSize, then this results in an out-of-bounds read. 2461 GpStatus WINGDIPAPI GdipPlayMetafileRecord(GDIPCONST GpMetafile *metafile, 2462 EmfPlusRecordType recordType, UINT flags, UINT dataSize, GDIPCONST BYTE *data) 2463 { .... 2471 2472 if (recordType >= 1 && recordType <= 0x7a) 2473 { 2474 /* regular EMF record */ 2475 if (metafile->playback_dc) 2476 { 2477 switch (recordType) 2478 { .... 2520 default: 2521 { 2522 ENHMETARECORD *record = heap_alloc_zero(dataSize + 8); // <== dataSize is completely user controlled 2523 2524 if (record) 2525 { 2526 record->iType = recordType; 2527 record->nSize = dataSize + 8; 2528 memcpy(record->dParm, data, dataSize); // <== data is user controlled, memcpy performs OOB read 2529 2530 if(PlayEnhMetaFileRecord(metafile->playback_dc, metafile->handle_table, 2531 record, metafile->handle_count) == 0) // (record is user controlled => source of many vulnerabilities) 2532 ERR("PlayEnhMetaFileRecord failed\n"); If you need more information (EMF trigger file, etc.) let me know! -- 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.

2 11

[Bug 43881] New: GOG LEGO Batman: broken graphics due to shader compiling failure
by wine-bugs＠winehq.org July 21, 2026

July 21, 2026

https://bugs.winehq.org/show_bug.cgi?id=43881 Bug ID: 43881 Summary: GOG LEGO Batman: broken graphics due to shader compiling failure Product: Wine Version: 2.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: farmboy0+winehq(a)googlemail.com Distribution: --- The shader contains a string declaration like this: string description = "Ubershader" This leads to the following output: trace:d3dcompiler:compile_shader Checking compilation target "vs_3_0" trace:d3dcompiler:push_scope Pushing a new scope fixme:hlsl_parser:hlsl_parse Array. trace:d3dcompiler:compilation_message :144:7: error: syntax error, unexpected KW_STRING -- 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.

3 8

[Bug 54648] New: Call of Juarez needs "isnan" handling
by WineHQ Bugzilla July 21, 2026

July 21, 2026

https://bugs.winehq.org/show_bug.cgi?id=54648 Bug ID: 54648 Summary: Call of Juarez needs "isnan" handling Product: vkd3d Version: 1.6 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 0718:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 0718:err:d3dcompiler:D3DCompile2 Shader log: 0718:err:d3dcompiler:D3DCompile2 <anonymous>:18:6: E5005: Function "isnan" is not defined. 1.6-195-g2880be64 -- 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.

2 6

[Bug 24063] New: World in conflict fails to start in DX10 mode
by wine-bugs＠winehq.org July 21, 2026

July 21, 2026

http://bugs.winehq.org/show_bug.cgi?id=24063 Summary: World in conflict fails to start in DX10 mode Product: Wine Version: 1.3.1 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: xvachon(a)gmail.com Created an attachment (id=30246) --> (http://bugs.winehq.org/attachment.cgi?id=30246) Log +d3d10 World in Conflict is unable to start in DX10 mode. Native dxdiagn.dll was used to avoid http://bugs.winehq.org/show_bug.cgi?id=11114 and sh winetricks d3dx10 was run too. I uploaded a +d3d10 log. If you need other debug channels, please ask. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

3 15