wine-bugs July 2024

wine-bugs@winehq.org

1 participants
1483 discussions

[Bug 49944] New: Tom Clancy's Splinter Cell: Conviction fails to detect audio device
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=49944 Bug ID: 49944 Summary: Tom Clancy's Splinter Cell: Conviction fails to detect audio device Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 68335 --> https://bugs.winehq.org/attachment.cgi?id=68335 wbemprox Stops launching with 'No audio device detected' message. Workaround is rename systemdetection.dll in 'src/system' or disable wbemprox. wine-5.18-161-gcce4f36e21 -- 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 6

[Bug 55662] New: Different behaviour of "set" command
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=55662 Bug ID: 55662 Summary: Different behaviour of "set" command Product: Wine Version: 8.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: ch.panel(a)free.fr Distribution: --- behavior of these commands are different in wine and windows in a batch file set test=A set /P test="type A or B (%test%) :" echo "%test%" pause if the user type nothing the result is : "A" on windows "" on wine -- 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 5

[Bug 32679] New: cmd.exe Add support for || and &&
by wine-bugs＠winehq.org 28 Jul '24

28 Jul '24

http://bugs.winehq.org/show_bug.cgi?id=32679 Bug #: 32679 Summary: cmd.exe Add support for || and && Product: Wine Version: 1.5.21 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: cmd AssignedTo: wine-bugs(a)winehq.org ReportedBy: us(a)edmeades.me.uk Classification: Unclassified Add support to cmd.exe for the && and || functionality - They are currently parsed and handled ok, but not correctly processed -- 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.

2 34

[Bug 56972] New: Warlords III: Darklords Rising shows empty screen in virtual desktop
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56972 Bug ID: 56972 Summary: Warlords III: Darklords Rising shows empty screen in virtual desktop Product: Wine Version: 9.13 Hardware: x86-64 URL: https://store.steampowered.com/app/2916220/Warlords_II I_Darklords_Rising/ OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: 03e43434c2bcf6424d60ee9dc1f595aa18714eef Distribution: ArchLinux I bumped into this bug while checking whether bug #53716 still occurs in recent Wine (yes it does). Reproduced with the Steam and GOG.com versions. When initiating a single-player game from the launcher, the sounds of the intro video can be heard but only the empty virtual desktop can be seen. The screen remains empty when the game enters the main menu. Nether in fullscreen mode the game starts properly: switches the desktop to low resolution, the game icon is present in the taskbar but can't be activated. The problem is present since commit 03e43434c2bcf6424d60ee9dc1f595aa18714eef (win32u: Introduce a new window surface helper to set window shape.) X.Org X Server 1.21.1.13 on Arch Linux XFCE 4.18 -- 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 4

[Bug 55798] New: Unreal Engine 5.2: Wine minidumps take hours to load into a debugger
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=55798 Bug ID: 55798 Summary: Unreal Engine 5.2: Wine minidumps take hours to load into a debugger Product: Wine Version: 8.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: aiden.deloryn(a)tensorworks.com.au Distribution: --- === Overview === When attempting to load a Wine generated minidump from an Unreal Engine application using a debugger (such as Visual Studio or VS Code), it takes a number of hours for the file to load. If left uninterrupted during this time, the process does eventually complete and all of the expected debug data becomes visible within the IDE. This behaviour has only been observed for minidumps of type MiniDumpNormal. When working with a Wine generated minidump of type MiniDumpWithFullMemory, the debugger is able to load the file within a few seconds. === Steps to Reproduce === 1. Build this minimal sample application https://github.com/TensorWorks/BuggyFirstPersonDemo.git on a Windows machine with Unreal Engine 5.2.1 using the following command: C:\<UE_INSTALL_DIR>\Engine\Build\BatchFiles\RunUAT.bat BuildCookRun -utf8output -clientconfig=DebugGame -project="C:\<PATH_TO_PROJECT_DIR>\BuggyFirstPersonDemo.uproject" -noP4 -cook -build -stage -prereqs -pak -archive -archivedirectory="C:\<PATH_TO_PROJECT_DIR>\GameBuilds" -platform=Win64 2. Copy the build directory (C:\<PATH_TO_PROJECT_DIR>\GameBuilds) to a Linux machine and run the application using Wine (DXVK required): wine ./GameBuilds/Windows/BuggyFirstPersonDemo/Binaries/Win64/BuggyFirstPersonDemo-Win64-DebugGame.exe -windowed -ResX=800 -ResY=600 3. Trigger a crash by picking up the gun and shooting the large white cube. Note: hold down the right mouse button to aim/look, and press the left mouse button to shoot. 4. Copy the crash dump from ./GameBuilds/Windows/BuggyFirstPersonDemo/Saved/Crashes/<CRASH_ID>/UEMinidump.dmp to a Windows machine and attempt to load it using Visual Studio or VS Code (for VS Code you will need the C/C++ extension from Microsoft installed). === Actual Results === The minidump takes hours to load into Visual Studio and VS Code. MemoryListStream contains over 950,000 memory ranges (see additional information below). === Expected Results === The minidump takes less than a minute to load into Visual Studio and VS Code, which is true for full memory minidumps generated under Wine and any minidump generated under Windows. === Build Date & Hardware === wine-8.14 on Ubuntu 22.04.3 LTS x86-64 === Additional Builds and Platforms === Also reproducible on wine-8.17 and wine-8.0.2 === Additional Information === When analysing and comparing minidumps generated under Wine versus those generated under Windows using the Microsoft Crash Dump File Checker tool “DumpChk” (https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/dumpchk), a significant discrepancy can be observed in the normal minidump generated under Wine. In particular, the number of memory ranges in MemoryListStream is substantially higher, as can be seen in the excerpts below. Note that full memory minidumps have also been included from both Windows and Wine for additional context and comparison. Windows - MiniDumpNormal: Stream 3: type MemoryListStream (5), size 00000804, RVA 0006FF09 128 memory ranges [OMITTED] Total memory: 463cc Wine - MiniDumpNormal: Stream 4: type MemoryListStream (5), size 00EA0FF4, RVA 0002986B 958719 memory ranges [OMITTED] Total memory: 15bd62e Windows - MiniDumpWithFullMemory: Stream 5: type Memory64ListStream (9), size 0000EAC0, RVA 000C8D45 3755 memory ranges [OMITTED] Total memory: a74c1000 Wine - MiniDumpWithFullMemory: Stream 7: type Memory64ListStream (9), size 0000E260, RVA 0006ADFB 3621 memory ranges [OMITTED] Total memory: 7ab14000 Note: You can generate a full memory minidump using the provided sample application by specifying the -fullcrashdumpalways flag. For example: wine ./GameBuilds/Windows/BuggyFirstPersonDemo/Binaries/Win64/BuggyFirstPersonDemo-Win64-DebugGame.exe -windowed -ResX=800 -ResY=600 -fullcrashdumpalways -- 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 3

[Bug 48455] New: Native Instruments Native Access 1.9 installer hangs during installation of ISO Mounter driver (missing handling of architecture-specific SourceDisks{Names,Files} .inf sections)
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=48455 Bug ID: 48455 Summary: Native Instruments Native Access 1.9 installer hangs during installation of ISO Mounter driver (missing handling of architecture-specific SourceDisks{Names,Files} .inf sections) Product: Wine Version: 5.0-rc5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. The driver sub-installer just hangs (churning cpu), blocking the main installer forever. Stable download link via Internet Archive: https://web.archive.org/web/20190227215247/https://www.native-instruments.c… --- snip --- $ wine ./Native\ Access\ 1.9.1\ Setup\ PC.exe ... --- snip --- Reduced case by calling driver sub-installer directly, after killing main installer: --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files (x86)/Native Instruments/IsoDriver/x64 $ WINEDEBUG=+seh,+relay,+loaddll,+process,+setupapi wine ./NI-drvinst.exe instroot "root\NIWinCDEmu" "C:\Program Files (x86)\Native Instruments\IsoDriver\NIWinCDEmu.inf" >>log.txt 2>&1 ... 002d:trace:setupapi:SetupDiInstallDriverFiles devinfo 000000000011C1C0, device_data 000000000022F6C0. ... 002d:trace:setupapi:SetupOpenInfFileW L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver\\NIWinCDEmu.inf" -> 000000000011D990 ... 002d:trace:setupapi:SetupGetStringFieldW context 000000000011D990/000000000011D990/9/0 index 1 returning L"Drivers_Dir" ... 002d:trace:setupapi:SetupQueueCopySectionW queue 000000000011DDD0, src_root L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver", hinf 000000000011D990, hlist 000000000011D990, section L"Drivers_Dir", style 0x10000. ... 002d:trace:setupapi:SetupQueueCopyIndirectW root=L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver" path=(null) file=L"NIWinCDEmu.sys" -> dir=L"C:\\windows\\system32\\drivers" file=L"NIWinCDEmu.sys" descr=(null) tag=(null) ... 002d:trace:setupapi:SetupDefaultQueueCallbackW start copy L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver\\NIWinCDEmu.sys" -> L"C:\\windows\\system32\\drivers\\NIWinCDEmu.sys" ... 002d:trace:setupapi:queue_copy_file copying file L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver\\NIWinCDEmu.sys" -> L"C:\\windows\\system32\\drivers\\NIWinCDEmu.sys" ... 002d:trace:setupapi:do_file_copyW copy L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver\\NIWinCDEmu.sys" to L"C:\\windows\\system32\\drivers\\NIWinCDEmu.sys" style 0x10000 002d:Call KERNEL32.GetFileAttributesW(006fd540 L"C:\\windows\\system32\\drivers\\NIWinCDEmu.sys") ret=00259e09 ... 002d:Ret KERNEL32.GetFileAttributesW() retval=ffffffff ret=00259e09 002d:Call KERNEL32.CopyFileW(006fd4a0 L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver\\NIWinCDEmu.sys",006fd540 L"C:\\windows\\system32\\drivers\\NIWinCDEmu.sys",00000000) ret=0025a064 .... 002d:Call ntdll.NtCreateFile(0022e100,80100080,0022e128,0022e118,00000000,00000000,00000007,00000001,00000060,00000000,00000000) ret=7b0110a1 002d:Ret ntdll.NtCreateFile() retval=c0000034 ret=7b0110a1 002d:Call ntdll.RtlNtStatusToDosError(c0000034) ret=7b011190 002d:Ret ntdll.RtlNtStatusToDosError() retval=00000002 ret=7b011190 ... 002d:Ret KERNEL32.CopyFileW() retval=00000000 ret=0025a064 002d:warn:setupapi:do_file_copyW failed to copy, err 2 ... <repeats endlessly> ... 002d:trace:setupapi:SetupDefaultQueueCallbackW need media L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver" L"NIWinCDEmu.sys" ... 002d:trace:setupapi:SetupDefaultQueueCallbackW start copy L"C:\\Program Files (x86)\\Native Instruments\\IsoDriver\\NIWinCDEmu.sys" -> L"C:\\windows\\system32\\drivers\\NIWinCDEmu.sys" ... --- snip --- Content of 'NIWinCDEmu.inf': --- snip --- [Version] Signature="$WINDOWS NT$" Class=SCSIAdapter ClassGuid={4d36e97b-e325-11ce-bfc1-08002be10318} Provider=%NI_MFNAME% DriverVer= 08/05/2011, 1.0.0.2 CatalogFile=NIWinCDEmu.cat [DestinationDirs] DefaultDestDir = 12 [SourceDisksNames.x86] 1 = %DiskId1%,,, [SourceDisksNames.amd64] 1 = %DiskId1%,,, [SourceDisksFiles.x86] NIWinCDEmu.sys = 1,\x86 [SourceDisksFiles.amd64] NIWinCDEmu.sys = 1,\x64 [Manufacturer] %NI_MFNAME%=Standard, NTamd64 [Standard] %NIWinCDEmu.DeviceDesc%=NIWinCDEmu_Device, root\NIWinCDEmu [Standard.NTamd64] %NIWinCDEmu.DeviceDesc%=NIWinCDEmu_Device, root\NIWinCDEmu [NIWinCDEmu_Device.NT] CopyFiles=Drivers_Dir [Drivers_Dir] NIWinCDEmu.sys,,,2 ;-------------- Service installation [NIWinCDEmu_Device.NT.Services] AddService = NIWinCDEmu,%SPSVCINST_ASSOCSERVICE%, dev_Service_Inst ; -------------- busenum driver install sections [dev_Service_Inst] DisplayName = %dev.SVCDESC% ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 3 ; SERVICE_DEMAND_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %12%\NIWinCDEmu.sys LoadOrderGroup = Extended Base [Strings] SPSVCINST_ASSOCSERVICE= 0x00000002 NI_MFNAME = "Native Instruments GmbH" DiskId1 = "ISO Mounter Installation Disk #1" NIWinCDEmu.DeviceDesc = "ISO Mounter" dev.SVCDESC = "ISO Mounter driver" --- snip --- The problem here is that Wine's 'get_source_info' doesn't take architecture-specific 'SourceDisksNames' and 'SourceDisksFiles' .inf sections into account. Wine source: https://source.winehq.org/git/wine.git/blob/b3abc343c373ee5fd0764a3ceedeef5… --- snip --- 289 static void get_source_info( HINF hinf, const WCHAR *src_file, SP_FILE_COPY_PARAMS_W *params, 290 WCHAR *src_root, WCHAR *src_path) 291 { 292 static const WCHAR SourceDisksNames[] = 293 {'S','o','u','r','c','e','D','i','s','k','s','N','a','m','e','s',0}; 294 static const WCHAR SourceDisksFiles[] = 295 {'S','o','u','r','c','e','D','i','s','k','s','F','i','l','e','s',0}; 296 297 INFCONTEXT file_ctx, disk_ctx; 298 INT id, diskid; 299 DWORD len; 300 301 /* find the SourceDisksFiles entry */ 302 if (!SetupFindFirstLineW( hinf, SourceDisksFiles, src_file, &file_ctx )) return; 303 if (!SetupGetIntField( &file_ctx, 1, &diskid )) return; 304 305 /* now find the diskid in the SourceDisksNames section */ 306 if (!SetupFindFirstLineW( hinf, SourceDisksNames, NULL, &disk_ctx )) return; 307 for (;;) 308 { 309 if (SetupGetIntField( &disk_ctx, 0, &id ) && (id == diskid)) break; 310 if (!SetupFindNextLine( &disk_ctx, &disk_ctx )) return; 311 } 312 313 if (SetupGetStringFieldW( &disk_ctx, 1, NULL, 0, &len ) && len > sizeof(WCHAR) 314 && (params->SourceDescription = heap_alloc( len * sizeof(WCHAR) ))) 315 SetupGetStringFieldW( &disk_ctx, 1, (WCHAR *)params->SourceDescription, len, NULL ); 316 317 if (SetupGetStringFieldW( &disk_ctx, 2, NULL, 0, &len ) && len > sizeof(WCHAR) 318 && (params->SourceTagfile = heap_alloc( len * sizeof(WCHAR) ))) 319 SetupGetStringFieldW( &disk_ctx, 2, (WCHAR *)params->SourceTagfile, len, NULL ); 320 321 if (SetupGetStringFieldW( &disk_ctx, 4, NULL, 0, &len ) && len > sizeof(WCHAR) 322 && len < MAX_PATH - lstrlenW( src_root ) - 1) 323 { 324 lstrcatW( src_root, backslashW ); 325 SetupGetStringFieldW( &disk_ctx, 4, src_root + lstrlenW( src_root ), 326 MAX_PATH - lstrlenW( src_root ), NULL ); 327 } 328 329 if (SetupGetStringFieldW( &file_ctx, 2, NULL, 0, &len ) && len > sizeof(WCHAR) && len < MAX_PATH) 330 { 331 SetupGetStringFieldW( &file_ctx, 2, src_path, MAX_PATH, NULL ); 332 params->SourcePath = src_path; 333 } 334 } --- snip --- Microsoft docs: https://docs.microsoft.com/en-us/windows-hardware/drivers/install/inf-sourc… --- quote ---- ... To support distribution of driver files on multiple system architectures, you can specify an architecture-specific SourceDisksFiles section by adding an .x86, .ia64, .amd64, .arm, or .arm64 extension to SourceDisksFiles. Be aware that, unlike other sections such as a DDInstall section, the platform extensions for a SourceDisksFiles section are not .ntx86, .ntia64, or .ntamd64. For example, to specify a source disk names section for an x86-based system, use a SourceDisksFiles.x86 section, not a SourceDisksFiles.ntx86 section. Similarly, use a SourceDisksFiles.ia64 section to specify an Itanium-based system and a SourceDisksFiles.amd64 section to specify an x64-based system. During installation, SetupAPI functions look for architecture-specific SourceDisksFiles sections before using the generic section. For example, if, during installation on an x86-based platform, Windows is copying a file that is named driver.sys, it will look for the file's description in [SourceDisksFiles.x86] before looking in [SourceDisksFiles]. --- quote ---- In contrast, 'get_source_id' does it properly: https://source.winehq.org/git/wine.git/blob/f1b94dc16c35a5c477b6df8aa94c6d3… --- snip --- 372 static LPWSTR get_source_id( HINF hinf, PINFCONTEXT context, PCWSTR filename ) 373 { 374 DWORD size; 375 LPWSTR source_id; 376 377 if (!SetupFindFirstLineW( hinf, source_disks_files_platform, filename, context ) && 378 !SetupFindFirstLineW( hinf, source_disks_files, filename, context )) 379 return NULL; 380 381 if (!SetupGetStringFieldW( context, 1, NULL, 0, &size )) 382 return NULL; 383 384 if (!(source_id = HeapAlloc( GetProcessHeap(), 0, size * sizeof(WCHAR) ))) 385 return NULL; 386 387 if (!SetupGetStringFieldW( context, 1, source_id, size, NULL )) 388 { 389 HeapFree( GetProcessHeap(), 0, source_id ); 390 return NULL; 391 } 392 393 if (!SetupFindFirstLineW( hinf, source_disks_names_platform, source_id, context ) && 394 !SetupFindFirstLineW( hinf, source_disks_names, source_id, context )) 395 { 396 HeapFree( GetProcessHeap(), 0, source_id ); 397 return NULL; 398 } 399 return source_id; 400 } --- snip --- $ sha1sum Native* 374f62fb373ceb02527b8a179c7e305268bab25c Native Access 1.9.1 Setup PC.exe 5a78d5850267d0ef6701bc5da7dc25e5b62b6031 Native_Access_Installer.zip $ du -sh Native* 70M Native Access 1.9.1 Setup PC.exe 69M Native_Access_Installer.zip $ wine --version wine-5.0-rc5 Regards -- 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 12

[Bug 56977] New: accept()-ed socket fds are never marked as cacheable
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56977 Bug ID: 56977 Summary: accept()-ed socket fds are never marked as cacheable Product: Wine Version: 9.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com CC: ishitatsuyuki(a)gmail.com, z.figura12(a)gmail.com Regression SHA1: 89f77a93a6c96896d90c943bc3e82139114cf58c Distribution: --- allow_fd_caching() is not called for accept()-ed sockets, causing severe performance degradation due to extra server_get_unix_fd() call overhead per every socket I/O operation. Affected applications: - DJMAX RESPECT V creates a loopback TCP socket pair. The "server" side ESTABLISHED socket is affected. -- 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 3

[Bug 56954] New: after commit 3f87436670d8a9c87e00825b71ed6995afd870a1 wine will generate ntlm_auth <defunct> process.
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56954 Bug ID: 56954 Summary: after commit 3f87436670d8a9c87e00825b71ed6995afd870a1 wine will generate ntlm_auth <defunct> process. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l12436.tw(a)gmail.com Distribution: --- Created attachment 76771 --> https://bugs.winehq.org/attachment.cgi?id=76771 ntlm_auth defunct process After commit 3f87436670d8a9c87e00825b71ed6995afd870a1 wine will generate lots of ntlm defunct process. before this commit, it will return to normal. -- 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 12

[Bug 56969] New: Act of War (Direct Action, High Treason) crashes in wined3d when loading the mission
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56969 Bug ID: 56969 Summary: Act of War (Direct Action, High Treason) crashes in wined3d when loading the mission Product: Wine Version: unspecified Hardware: x86-64 URL: https://store.steampowered.com/app/2710/Act_of_War_Dir ect_Action/ OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: 65165cf8520f85ac327115536749cda1aabef77b Distribution: --- Created attachment 76792 --> https://bugs.winehq.org/attachment.cgi?id=76792 terminal output The game works properly in Wine-9.12, the issue is present in the current git version of Wine. The intro videos are playing fine, the menu works correctly. However the game crashes when loading a mission. I can't get a proper backtrace because the game's own debugger/exception handler kicks in as soon as the game crashes. The original demo version is not affected, I reproduced the problem with both the GOG and the Steam versions. Reverting commit 65165cf8520f85ac327115536749cda1aabef77b fixes the crash for me. (wined3d: Feed the FFP color key through a push constant buffer.) wine-9.12-332-g34b16060199 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 550.40.65 OpenGL core profile shading language version string: 4.60 NVIDIA -- 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 7

[Bug 56994] New: mbstowcs for UTF8, with an exact (not overallocated) output buffer size fails
by WineHQ Bugzilla 28 Jul '24

28 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=56994 Bug ID: 56994 Summary: mbstowcs for UTF8, with an exact (not overallocated) output buffer size fails Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: martin(a)martin.st CC: piotr(a)codeweavers.com Distribution: --- This issue can be illustrated with the following test snippet: #include <stdio.h> #include <locale.h> #include <stdlib.h> #include <wchar.h> int main() { const char *locname = "en_US.UTF-8"; if (!setlocale(LC_ALL, locname)) { fprintf(stderr, "locale %s failed\n", locname); return 1; } wchar_t wcsbuf[10] = { 0xe9, 0 }; // LATIN SMALL LETTER E WITH ACUTE char mbsbuf[10] = { 0 }; size_t ret; ret = wcstombs(NULL, wcsbuf, 0); printf("initial wcstombs returned %d bytes\n", (int) ret); ret = wcstombs(mbsbuf, wcsbuf, ret); printf("wcstombs returned %d bytes\n", (int) ret); if (ret == -1) return 1; for (size_t i = 0; i < ret; i++) printf("%02x ", (unsigned char)mbsbuf[i]); printf("\n"); ret = mbstowcs(NULL, mbsbuf, 0); printf("initial mbstowcs returned %d wchars\n", (int) ret); if (ret > sizeof(wcsbuf)/sizeof(wcsbuf[0])) return 1; ret = mbstowcs(wcsbuf, mbsbuf, ret); printf("mbstowcs returned %d wchars\n", (int) ret); if (ret == -1) return 1; for (size_t i = 0; i < ret; i++) printf("%02x ", (unsigned int)wcsbuf[i]); printf("\n"); return 0; } Compiled with mingw tools targeting UCRT. On native Windows, this outputs: initial wcstombs returned 2 bytes wcstombs returned 2 bytes c3 a9 initial mbstowcs returned 1 wchars mbstowcs returned 1 wchars e9 With Wine, it outputs: initial wcstombs returned 2 bytes wcstombs returned 2 bytes c3 a9 initial mbstowcs returned 1 wchars mbstowcs returned -1 wchars Thus, the actual mbstowcs conversion fails, whereas it succeds on native Windows. The problem here is that the output buffer size, given to mbstowcs, is a tightly allocated 1. When scanning the (null terminated) input buffer, to calculate the input size, at https://gitlab.winehq.org/wine/wine/-/blob/wine-9.13/dlls/msvcrt/mbcs.c?ref…, we limit the loop to "i<count". As we've passed count=1, as we know the output is going to be 1 wchar, this loop terminates after one iteration. The check "_isleadbyte_l((unsigned char)mbstr[size], locale)" seems to fail for the leading UTF8 byte, which probably is a bug in itself. But if mbstowcs is given an overallocated output size (passing a larger count parameter), that issue isn't visible here. -- 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 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs July 2024