- wine-bugs - winehq.org

[Bug 53023] New: MinecraftInstaller
by WineHQ Bugzilla 21 May '22

21 May '22

https://bugs.winehq.org/show_bug.cgi?id=53023 Bug ID: 53023 Summary: MinecraftInstaller Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jon9097(a)gmail.com Distribution: --- Created attachment 72394 --> https://bugs.winehq.org/attachment.cgi?id=72394 Log The Minecraft Installer doesn't work. It won't start. I'm attaching the logs. -- 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 52188] New: Could not load file or assembly 'Windows.Foundation.UniversalApiContract
by WineHQ Bugzilla 21 May '22

21 May '22

https://bugs.winehq.org/show_bug.cgi?id=52188 Bug ID: 52188 Summary: Could not load file or assembly 'Windows.Foundation.UniversalApiContract Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: julianhoyos94(a)gmail.com Distribution: --- hi everybody, i am creating scrpit for use xboxgamepass on linux, im very close but i have this error Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Windows.Foundation.UniversalApiContract, Version=7.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. file not found I would like to know if anyone has already experienced this problem, and if they have solved it since I looked on the internet, but I can't find the problem reported in wine. and I'm also looking for what it is, and I can't find anything about what program or what the error is based on, apparently it is part of Windows development libraries, I thought it was through .net but apparently it has nothing to do with it. -- 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 53011] New: Multithreaded compilation fails sometimes due to race conditions
by WineHQ Bugzilla 21 May '22

21 May '22

https://bugs.winehq.org/show_bug.cgi?id=53011 Bug ID: 53011 Summary: Multithreaded compilation fails sometimes due to race conditions Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 72380 --> https://bugs.winehq.org/attachment.cgi?id=72380 Sample of the two broken files Sometimes the compilation fails with a message like the following: /usr/bin/i686-w64-mingw32-dlltool: dlls/mfplat/libmfplat.cross.a: error reading mfplat_dll_t.o: No such file or directory /usr/bin/i686-w64-mingw32-dlltool: dlls/rpcrt4/librpcrt4.cross.a: error reading rpcrt4_dll_h.o: file truncated /usr/bin/i686-w64-mingw32-dlltool: dlls/rpcrt4/librpcrt4.delay.a: error reading rpcrt4_dll_t.o: No such file or directory /usr/bin/i686-w64-mingw32-dlltool: bfd_open failed reopen stub file: wintrust_dll_s00009.o: No such file or directory Or sometimes files are broken: /usr/lib/gcc/i686-w64-mingw32/11.2.0/../../../../i686-w64-mingw32/bin/ld: dlls/iphlpapi/libiphlpapi.delay.a: error adding symbols: file in wrong format /usr/lib/gcc/i686-w64-mingw32/11.2.0/../../../../i686-w64-mingw32/bin/ld: dlls/wintrust/libwintrust.cross.a: error adding symbols: file format not recognized If the file doesn't exist / is truncated, then trying again usually makes it work. For broken files, they need to be deleted and then you can try again. I usually compile wine like this: ALLFLAGS="-g -O0" PKG_CONFIG_PATH=/usr/lib32/pkgconfig CC="ccache gcc" CFLAGS="$ALLFLAGS" CROSSCC="ccache i686-w64-mingw32-gcc" CROSSCFLAGS="$ALLFLAGS" ../wine-git/configure --without-cups --enable-silent-rules make -j15 -sw I don't think ccache causes this, but possibly it exacerbates it.. -- 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 52969] New: mshtml:script fails on up-to-date Windows 8.1 machines
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52969 Bug ID: 52969 Summary: mshtml:script fails on up-to-date Windows 8.1 machines Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mshtml:script fails on up-to-date Windows 8.1 machines: script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [0] got 0.00" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [1] got 1,234.50" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [2] got -1,337.73" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [3] got -0.01" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [5] got 0.00" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [6] got 99.00" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [7] got 99.00" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [8] got 65,536.50" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: called on string threw 2148144009" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: called on undefined threw 2148144009" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: called on nullDisp threw 2148144009" https://test.winehq.org/data/patterns.html#mshtml:script These failures only happen on the cw-gtx560 and cw-rx460 Windows 8.1 machines. I suspect this is because these have more recent Windows updates than the TestBot's w8 and w864 machines (see bug 52858). More specifically cw-rx460 has had more recent updates than cw-gtx560 for quite some time and I further updated both on 2022-05-02. I further plan to update the TestBot's VM (the rationale being that Windows 8.1 is old and we really only care about the latest version) which should make it easier to debug. In the meantime this does seem like a regression. commit 8aefdf48f9846e05aeef3c7ce2374401982b98b4 Author: Gabriel Ivăncescu <gabrielopcode(a)gmail.com> Date: Tue May 3 18:17:06 2022 +0300 jscript: Implement Number.prototype.toLocaleString. Signed-off-by: Gabriel Ivăncescu <gabrielopcode(a)gmail.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 52892] New: The 64-bit ntdll:thread fails on w7pro64 and w864
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52892 Bug ID: 52892 Summary: The 64-bit ntdll:thread fails on w7pro64 and w864 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 64-bit ntdll:thread fails on w7pro64 and w864: thread.c:153: Test failed: Multiple threads have TEB 000007FFFFFDC000. https://test.winehq.org/data/patterns.html#ntdll:thread The failure is hard to reproduce but the test was introduced by this commit: commit 6d4ec1255acceec7152ed98764ee29991ac04f10 Author: Brendan Shanks <bshanks(a)codeweavers.com> AuthorDate: Mon Apr 18 11:25:10 2022 -0700 Commit: Alexandre Julliard <julliard(a)winehq.org> CommitDate: Mon Apr 18 21:48:15 2022 +0200 ntdll/tests: Test that threads have unique TEBs. Signed-off-by: Brendan Shanks <bshanks(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Specifically the issue is with the line below: + ok( teb1 != teb2, "Multiple threads have TEB %p.\n", teb1 ); I think the issue is that there is no guarantee that the two test threads are running at the same time. I suspect that sometimes what happens is this [1]: * status = pNtCreateThreadEx( &threads[0], ... &teb1, ... ); A new TEB is allocated, the first thread starts, sets teb1 and terminates at which time its TEB is freed. * status = pNtCreateThreadEx( &threads[1], ... &teb2, ... ); A new TEB is allocated, hey there's a fresh TEB that has just bee freed! [2]. The second thread starts and sets teb2. * WaitForMultipleObjects( 2, threads, TRUE, INFINITE ); Wait for both threads. * ok( teb1 != teb2, "Multiple threads have TEB %p.\n", teb1 ); Hey, both threads used the same TEB! But did they do so at the same time? One hacky fix would be to at a small sleep in the test threads but that's introducing race conditions. A better fix would be for the main thread to tell the test threads when they can exit through some synchronization object. [1] This may be tied to how the scheduler behaves which may limit the issue to specific Windows versions. [2] And that's probably tied to how the memory allocator behaves: more memory locality or less chance of overwriting (incorrectly) still in use memory. Again this could limit the issue to some Windows versions. -- 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 52761] New: mscoree:mscoree test fails without a display or console
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52761 Bug ID: 52761 Summary: mscoree:mscoree test fails without a display or console Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Distribution: --- The mscoree:mscoree test fails if you run it like this: $ DISPLAY= wine mscoree_test.exe mscoree </dev/null >log 2>&1 Without the DISPLAY=, it makes a bunch of console windows. That doesn't seem to happen on Windows, but that could be caused by our csc.exe. -- 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 46

[Bug 52937] New: msvcr110:msvcr110 fails on Windows with the UTF-8 codepage
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52937 Bug ID: 52937 Summary: msvcr110:msvcr110 fails on Windows with the UTF-8 codepage Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com msvcr110:msvcr110 fails on Windows with the UTF-8 codepage: msvcr110.c:135: Test failed: expected syr-SY, got LC_COLLATE=syr-SY;LC_CTYPE=EN-US;LC_MONETARY=syr-SY;LC_NUMERIC=syr-SY;LC_TIME=syr-SY https://test.winehq.org/data/patterns.html#msvcr110:msvcr110 Note that the LC_CTYPE value in the above string corresponds to the last value it was set to. So if one tests fr-FR right before syr-SY the string contains LC_CTYPE=fr-FR. This is also why the en-US case is weird. Furthermore with a non-UTF-8 codepage setlocale() does return "syr-SY". So it looks like: 1. msvcr110 returns a long string specifying the details of the locale settings whenever they have different values. 2. msvcr110 does not support setting LC_CTYPE to syr-SY, but only when the codepage is UTF-8 for whatever reason. -- 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 51298] New: d3d8:visual: lighting_test() fails on Windows 10 >= 2004
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51298 Bug ID: 51298 Summary: d3d8:visual: lighting_test() fails on Windows 10 >= 2004 Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d8:visual has a failure in lighting_test() on Windows 10 >= 2004: https://test.winehq.org/data/patterns.html#d3d8:visual visual.c:544: Test failed: Lit quad with singular world matrix has color 0x00000000. This happens on cw-rx460, cw-gtx560 and on those TestBot VMs that run the 32-bit tests. That means it's not a VM or graphics driver issue but a Windows version one. The test was introduced by this commit: commit 589f1072df9535104c074e5382ef7d8ce28f0f33 Author: Matteo Bruni <mbruni(a)codeweavers.com> AuthorDate: Tue Apr 21 15:11:19 2015 +0200 d3d8/tests: Add a lighting test with non-affine worldview matrix. -- 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 51104] New: mf:mf crashes on Windows + NVidia
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51104 Bug ID: 51104 Summary: mf:mf crashes on Windows + NVidia Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- mf:mf crashes on the cw-gtx560 and cw-rx460 machines but not on the TestBot VMs (except w7u-2qxl, but that's a different crash). https://test.winehq.org/data/patterns.html#mf:mf The crash happens on the same test_evr() line from Windows 8.1 to Windows 10 2009: hr = MFGetService((IUnknown *)stream_sink2, &MR_VIDEO_ACCELERATION_SERVICE, &IID_IMFVideoSampleAllocator, (void **)&allocator); A bisect shows that the commit causing the crash is not the one that added this line but the one below: commit 430c179fe86dd7f9b3ddfb6ef30f6359633ef0b8 Author: Nikolay Sivov <nsivov(a)codeweavers.com> Date: Fri Oct 9 13:54:38 2020 +0300 mf/evr: Set stream media type to the mixer. Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 34782] New: crypt32/chain tests crash with gcc-4.8.1 (win64)
by wine-bugs＠winehq.org 20 May '22

20 May '22

http://bugs.winehq.org/show_bug.cgi?id=34782 Bug #: 34782 Summary: crypt32/chain tests crash with gcc-4.8.1 (win64) Product: Wine Version: 1.7.4 Platform: x86 OS/Version: Linux Status: NEW Keywords: download, source, win64 Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Classification: Unclassified Running: crypt32:chain (3 of 15) fixme:crypt:CertVerifyCertificateChainPolicy unimplemented for 0 fixme:crypt:CRYPT_CriticalExtensionsSupported unsupported critical extension "1.2.3" fixme:crypt:CRYPT_CriticalExtensionsSupported unsupported critical extension "1.2.3" fixme:crypt:CRYPT_CriticalExtensionsSupported unsupported critical extension "1.2.3" wine: Unhandled page fault at address 0x7f579f85aa74 (thread 0043), starting debugger... fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported constant (parameter) pEncodePara in function fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported constant (parameter) dwFlags in function fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x15 at ctx(0x23aa10,L"kernel32<elf>"), for debug_info(abbrev:0x7b3c80,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x23aa10,L"kernel32<elf>"), for debug_info(abbrev:0x7b3c80,symt:(nil)) it works with gcc-4.7.3. I'll bisect gcc. -- 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 4

[Bug 28220] New: kernel32/process.ok: test fails when redirected
by wine-bugs＠winehq.org 20 May '22

20 May '22

http://bugs.winehq.org/show_bug.cgi?id=28220 Summary: kernel32/process.ok: test fails when redirected Product: Wine Version: 1.3.27 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com It's not uncommon to want to do make test > log 2>&1 but if you do this, kernel32/process.ok will fail with ../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p kernel32_test.exe.so process.c && touch process.ok wine: cannot find L"C:\\windows\\system32\\doesnotexist.exe" wine: cannot find L"C:\\windows\\system32\\does.exe" process.c:1344: Test failed: Opening ConOut process.c:1347: Test failed: Getting sb info process.c:1348: Test failed: Getting console modes -- 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 8

[Bug 53004] New: 63ce060 causes a white border line in winecfg
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=53004 Bug ID: 53004 Summary: 63ce060 causes a white border line in winecfg Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: 63ce060e5b33ca4b58d508be11af4d3c214fae33 Distribution: --- Created attachment 72372 --> https://bugs.winehq.org/attachment.cgi?id=72372 example As the title says. -- 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 52970] New: kernelbase:process breaks lz32:lzexpand_main on Windows 1809+
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52970 Bug ID: 52970 Summary: kernelbase:process breaks lz32:lzexpand_main on Windows 1809+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernelbase:process breaks lz32:lzexpand_main on Windows 1809+: lzexpand_main.c:148: Test failed: LZOpenFileA returned 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xxx', but was expected to return 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_' lzexpand_main.c:228: Test failed: LZOpenFileA succeeded on nonexistent file lzexpand_main.c:230: Test failed: GetLastError() returns 0 lzexpand_main.c:232: Test failed: LZOpenFileA set test.cBytes to 136 lzexpand_main.c:234: Test failed: LZOpenFileA set test.nErrCode to 0 lzexpand_main.c:236: Test failed: LZOpenFileA returned 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xxx', but was expected to return 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_' or '¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_' lzexpand_main.c:550: Test failed: LZOpenFileW returned 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xxx', but was expected to return 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_' lzexpand_main.c:628: Test failed: LZOpenFileW succeeded on nonexistent file lzexpand_main.c:630: Test failed: GetLastError() returns 0 lzexpand_main.c:632: Test failed: LZOpenFileW set test.cBytes to 136 lzexpand_main.c:634: Test failed: LZOpenFileW set test.nErrCode to 0 lzexpand_main.c:636: Test failed: LZOpenFileW returned 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xxx', but was expected to return 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_' or '¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥' https://test.winehq.org/data/patterns.html#lz32:lzexpand_main As mentioned before, lz32:lzexpand_main succeeds on its own. It's only when kernelbase:process is run before that this test fails. The simplest way to reproduce the failures is to run: winetest.exe -c -o - -t foo kernelbase:process lz32:lzexpand_main The failure happens because kernelbase:process leaves a "testfile.xxx" file behind, file which is also used by the lz32:lzexpand_main test unit. Finally a bisect shows that these failures started with the commit below. commit 9c40a80100febb9ac23dae1e51605ba4f2f46f6f Author: Nikolay Sivov <nsivov(a)codeweavers.com> Date: Wed May 4 14:55:36 2022 +0300 kernelbase: Implement MapViewOfFile3(). Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 51376] New: Wine causes PC to lock or crash wine when loading more than 1 VST addon into WaveLab 6
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51376 Bug ID: 51376 Summary: Wine causes PC to lock or crash wine when loading more than 1 VST addon into WaveLab 6 Product: Wine Version: 6.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Created attachment 70232 --> https://bugs.winehq.org/attachment.cgi?id=70232 backtrace I have a number of VST add-ons I use with Wavelab, they come from a number of different software houses and work differently, for example some require vcrun libraries to work while others do not. In the main, I can load any single add-on and it works as expected but as soon as I add/open a second add-on my PC will either crash wine or it will lock up altogether requiring a hard restart. This was not an issue in wine 5.0. Backtrace is attached. Possibly a duplicate of bug 51259 or is quite similar. -- 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 51283] New: d3d8:device breaks evr:evr on w7u-2qxl
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51283 Bug ID: 51283 Summary: d3d8:device breaks evr:evr on w7u-2qxl Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The WineTest reports show that evr:evr crashes on w7u-2qxl: https://test.winehq.org/data/patterns.html#evr:evr evr.c:1335: Test failed: Unexpected hr 0x80070057. evr.c:1335: this is the last test seen before the exception 07ac:evr: unhandled exception c0000005 at 0040CBD0 evr:evr:07ac done (-1073741819) in 0s Test failed: crash (c0000005) However when run on its own it succeeds consistently. It turns out that it is d3d8:device that causes evr:evr to crash. More specifically it is test_multi_adapter() that interferes with evr:evr. Also if d3d8:device succeeds then evr:evr crashes but if d3d8:device fails as shown below then evr:evr succeeds as can be seen by comparing the pattern below with the evr:evr one. https://test.winehq.org/data/patterns.html#d3d8:device device.c:4205: Test failed: Got a different mode. device.c:4208: Test failed: Got a different mode. -- 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 50462] New: Ulead Photo Explorer 8.5 Installed but failed on startup
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=50462 Bug ID: 50462 Summary: Ulead Photo Explorer 8.5 Installed but failed on startup Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wesley(a)merlin-eng.com Distribution: --- Created attachment 69087 --> https://bugs.winehq.org/attachment.cgi?id=69087 This is from the error window that came up when the program failed The program (Ulead Photo Explorer 8.5) appeared to install correctly. This program is designed to browse image files IE: .jpg. It installs with Ulead Photo Impact 10. I did not try to associate any files with either program (this should not be necessary). On startup Ulead Photo Explorer 8.5 failed, giving the attached back trace file. Photo Impact 10 installed at the same time and worked fine. -- 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 8

[Bug 45959] New: Editpad Lite 7 GUI not rendered correctly
by wine-bugs＠winehq.org 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=45959 Bug ID: 45959 Summary: Editpad Lite 7 GUI not rendered correctly Product: Wine Version: 3.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Created attachment 62506 --> https://bugs.winehq.org/attachment.cgi?id=62506 Screenshot of GUI The command menu line (top line) is not rendered correctly, please see the attachment. It should display buttons with the following descriptions: File, Edit, Search, Go, Block, Extra, Convert, Options, View, Help. By mousing over and clicking and resizing the window they will eventually be rendered correctly. The installer can be downloaded at https://www.editpadlite.com/download.html Problem exists in both 32 and 64 bit prefixes and different Windows versions. My system: Kubuntu 18.04.01 -- 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 4

[Bug 14841] New: ntdll: file.ok fails in OpenSolaris but not Linux
by wine-bugs＠winehq.org 20 May '22

20 May '22

http://bugs.winehq.org/show_bug.cgi?id=14841 Summary: ntdll: file.ok fails in OpenSolaris but not Linux Product: Wine Version: 1.1.2 Platform: PC OS/Version: Solaris Status: NEW Keywords: testcase Severity: enhancement Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=15384) --> (http://bugs.winehq.org/attachment.cgi?id=15384) +file in git, bzip2 -9'ed austin@opensolaris:~/wine-git/dlls/ntdll/tests$ make testclean ; rm -rf ~/.wine ; make file.ok rm -f atom.ok change.ok env.ok error.ok exception.ok generated.ok info.ok large_int.ok file.ok om.ok path.ok port.ok reg.ok rtl.ok rtlbitmap.ok rtlstr.ok string.ok time.ok ../../../tools/runtest -q -P wine -M ntdll.dll -T ../../.. -p ntdll_test.exe.so file.c && touch file.ok wine: created the configuration directory '/export/home/austin/.wine' err:iphlpapi:getNumWithOneHeader Unable to open '/proc/net/route' to count entries! err:iphlpapi:getRouteTable unimplemented! file.c:169: Test failed: wrong status deadbabe file.c:170: Test failed: wrong info 3735928559 file.c:194: Test failed: wrong status deadbabe file.c:195: Test failed: wrong info 3735928559 file.c:196: Test failed: read handle is signaled file.c:284: Test failed: wrong status deadbabe file.c:285: Test failed: wrong info 3735928559 file.c:286: Test failed: event is signaled make: *** [file.ok] Error 8 +file attached -- 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 11

[Bug 52874] New: win32u change prevents chromium from starting
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52874 Bug ID: 52874 Summary: win32u change prevents chromium from starting Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- The following commit breaks chromium: commit 0528f37fdd9b11cc95d074bb9e261d5127cb6ec3 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Tue Apr 19 15:34:44 2022 +0200 win32u: Move NtUserFindWindowEx implementation from user32. Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> chromium just prints a few fixmes and then hangs, using one thread fully. This only affects the sandbox, --no-sandbox is a workaround. Reverting fixes the issue. Download for testing (chrome-win.zip): https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.h… Please use this version for testing, since it's the newest version not affected by bug 52845. -- 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 9

[Bug 51827] New: d3dx10_34:d3dx10 crashes on all versions of Windows
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51827 Bug ID: 51827 Summary: d3dx10_34:d3dx10 crashes on all versions of Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3dx10_34:d3dx10 crashes on all versions of Windows: d3dx10.c:2377: this is the last test seen before the exception 00b8:d3dx10: unhandled exception c0000005 at 000000006C50064B https://test.winehq.org/data/patterns.html#d3dx10_34:d3dx10 The crash is random but pretty frequent and happens on AMD, NVidia and QEmu GPUs from Windows 8.1 to Windows 10. The other d3dx10_*:d3dx10 tests don't crash despite using the same source. So that means d3dx10_34 is different and the test fails to take that into account. This test was introduced by the following commit: commit a15527ff29d919b34ae1f599a5319a4b9678f4e2 Author: Nikolay Sivov <nsivov(a)codeweavers.com> Date: Tue Sep 21 08:52:10 2021 +0300 d3dx10_34/tests: Enable tests. Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> Signed-off-by: Matteo Bruni <mbruni(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 9

[Bug 51783] New: The ieframe:webbrowser output is too big in Wine
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51783 Bug ID: 51783 Summary: The ieframe:webbrowser output is too big in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ieframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ieframe:webbrowser outputs ~29kB of data. This is too much and contributes in pushing the WineTest reports above the 1.5MB limit. The traces break down as follows: 0kB failures 26kB todos 3kB traces 0kB test framework (summary lines, etc.) Time to fix Wine to reduce the number of todos! -- 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 19183] New: "make test" still fails on d3d9/tests/visual.c
by wine-bugs＠winehq.org 20 May '22

20 May '22

http://bugs.winehq.org/show_bug.cgi?id=19183 Summary: "make test" still fails on d3d9/tests/visual.c Product: Wine Version: 1.1.25 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com (This is a sequel to bug 10221; perhaps we closed that one too soon.) Running i=0 while test $i -lt 10 do ../../../tools/runtest -q -P wine -M d3d9.dll -T ../../.. -p d3d9_test.exe.so visual.c > visual-$i.log 2>&1 i=`expr $i + 1` sleep 1 done cat visual-*.log | grep "Test failed" | sort | uniq -c | sort -n produces 1 visual.c:9439: Test failed: stretchrect: Pixel 160,360 has color 0x00ff00ff, expected 0x00ff0000 1 visual.c:9441: Test failed: stretchrect: Pixel 480,360 has color 0x00ff00ff, expected 0x0000ff00 1 visual.c:9443: Test failed: stretchrect: Pixel 480,120 has color 0x00ff00ff, expected 0x000000ff 1 visual.c:9445: Test failed: stretchrect: Pixel 160,120 has color 0x00ff00ff, expected 0x00000000 2 visual.c:8978: Test failed: Offscreen failed for D3DFMT_A32B32G32R32F: expected no color blending but received it anyway. 3 visual.c:6883: Test failed: SRCALPHA on texture returned color 00000000, expected 0x00bf4000 3 visual.c:6887: Test failed: DSTALPHA on texture returned color 00000000, expected 0x000000ff 3 visual.c:8978: Test failed: Offscreen failed for D3DFMT_G32R32F: expected no color blending but received it anyway. 3 visual.c:8978: Test failed: Offscreen failed for D3DFMT_R32F: expected no color blending but received it anyway. 4 visual.c:8969: Test failed: Offscreen failed for D3DFMT_A16B16G16R16F: Got color 00000000, expected 0x181800. 4 visual.c:8978: Test failed: Offscreen failed for D3DFMT_G16R16F: expected no color blending but received it anyway. 5 visual.c:8326: Test failed: Pixel 14/18 has color 0x00000000, expected 0x0000ff00 5 visual.c:8329: Test failed: Pixel 18/14 has color 0x00000000, expected 0x000000ff 5 visual.c:8332: Test failed: Pixel 18/18 has color 0x00000000, expected 0x0000ffff 5 visual.c:8978: Test failed: Offscreen failed for D3DFMT_R16F: expected no color blending but received it anyway. 5 visual.c:9439: Test failed: stretchrect: Pixel 160,360 has color 0x00000000, expected 0x00ff0000 5 visual.c:9441: Test failed: stretchrect: Pixel 480,360 has color 0x00000000, expected 0x0000ff00 5 visual.c:9443: Test failed: stretchrect: Pixel 480,120 has color 0x00000000, expected 0x000000ff 7 visual.c:8800: Test failed: Texture 1(output color 1) has color 0x00000000, expected 0x0000ff00 7 visual.c:8802: Test failed: Texture 2(output color 2) has color 0x00000000, expected 0x000000ff lspci | grep -i vga says 00:10.0 VGA compatible controller: nVidia Corporation GeForce 7100/nForce 630i (rev a2) and this is on Jaunty x86-64 with the proprietary nvidia 180 driver. I'll attach the output of glxinfo. -- 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 13

[Bug 53015] New: winscp bookmark adding error
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=53015 Bug ID: 53015 Summary: winscp bookmark adding error Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gonghuiii(a)gmail.com Distribution: --- Created attachment 72382 --> https://bugs.winehq.org/attachment.cgi?id=72382 error message and then exit When using WinSCP to add a bookmark, it gives me errors when adding without checking the 'add to shared bookmark' option. -- 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 52914] New: mf:mf - The 64-bit test_h264_decoder() fails on 64-bit Debian 11 + Intel GPU
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52914 Bug ID: 52914 Summary: mf:mf - The 64-bit test_h264_decoder() fails on 64-bit Debian 11 + Intel GPU Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 64-bit test_h264_decoder() fails on my Debian 11 + Intel GPU machine (see fg-deb64-wow64): mf.c:6780: Test failed: SetOutputType returned 0x80004005. mf.c:6782: Test failed: Release returned 0 mf.c:6799: Test failed: got cbSize 0x3fc000 mf.c:6825: Test failed: ProcessOutput returned 0xc00d6d60 https://test.winehq.org/data/patterns.html#mf:mf configure does not mention any missing library (besides libhal) in either the 32- or the 64-bit builds. A bisect shows that the failures started with the commit below: commit 606505e5643d8df2a23a2cc074fa9b6b2ae8b05f Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Mon Mar 28 17:35:45 2022 +0200 winegstreamer: Try creating a wg_transform in the H264 decoder. Adding H264 format support in wg_format. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=45988 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=47084 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=49715 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52183 Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 52821] New: Missing support of C++20 Semaphores in built-in Wine C++ runtime
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52821 Bug ID: 52821 Summary: Missing support of C++20 Semaphores in built-in Wine C++ runtime Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: kle(a)bluewin.ch Distribution: --- Hi all Right at the beginning it should be noted that the following error may have been already described. There seems to exist currently no support of C++20 Semaphores in Wines built-in C++ library. I noticed this limitation with two applications. The following "msvcp140_atomic_wait.dll" related error message is shown when this issue occurs. Both apps crash right after. CXBX-R Xbox emulator (starting with build 374ba5e): wine: Call from 7B011586 to unimplemented function msvcp140_atomic_wait.dll.__std_atomic_wait_direct, aborting wine: Call from 7B011586 to unimplemented function msvcp140_atomic_wait.dll.__std_atomic_notify_one_direct, aborting PCSX-Redux PSX emulator (all newer builds since 4317): wine: Call from 0000000000272B9E to unimplemented function msvcp140_atomic_wait.dll.__std_atomic_wait_direct, aborting wine: Unimplemented function msvcp140_atomic_wait.dll.__std_atomic_wait_direct called at address 0000000000272B9E (thread 010c), starting debugger... wine: Call from 0000000000272B9E to unimplemented function msvcp140_atomic_wait.dll.__std_atomic_notify_one_direct, aborting Both applications worked before the "std::binary_semaphore" C++20 type was introduced. It is confirmed for Wine 7.0 that it can handle this situation when vcrun2019 (native MS Visual C++ 2019) is installed via winetricks. But for whatever reason this stopped to work in later Wine 7.x devel versions. A further workaround was to put a native "msvcp140_atomic_wait.dll" into the program folder. I can confirm that this helped at least for a while in conjunction with the PCSX-Redux emulator. But also here this tweak stopped to work in later Wine 7.x devel versions. More information can be found at the CXBX-R GitHub issue page: https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/issues/2347 -- 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 11

[Bug 52751] New: `winetricks nocrashdialog` no longer works properly with Wine 7.5(but works with 7.4)
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52751 Bug ID: 52751 Summary: `winetricks nocrashdialog` no longer works properly with Wine 7.5(but works with 7.4) Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- In Wine 7.4 I disabled crash dialog by `winetricks nocrashdialog` command and when app crashed, then silently it just exit. In Wine 7.5 I see that now is visible console window which exit after while Screenshoot of this window https://user-images.githubusercontent.com/41945903/160272294-dd272f8b-710d-… Steps to reproduce: - Download https://github.com/qarmin/Win32Fuzzer/releases/download/1.1.0/reproducer_64 (require at least Ubuntu 21.10 or similar) - Download https://github.com/qarmin/Win32Fuzzer/releases/download/1.1.0/win_project_6… - Run command `./reproducer win_project_64.exe linux` For now I'm unable to found exact commit with regression, due problem with compilation of Wine. Related winetricks issue - https://github.com/Winetricks/winetricks/issues/1897 -- 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 51680] New: nsi:nsi test_ip_neighbour() fails on unreachable link local entry
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51680 Bug ID: 51680 Summary: nsi:nsi test_ip_neighbour() fails on unreachable link local entry Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com nsi:nsi has a failure on cw-rx460 from Windows 1709 to 21H1: nsi.c:680: Test failed: AF_INET: 0 vs 1 https://test.winehq.org/data/patterns.html#nsi:nsi The failing test has been introduced by the commit below and failed from the start: commit c09c65f65c188a1870d279ca793c5ad1fc15440d Author: Huw Davies <huw(a)codeweavers.com> AuthorDate: Tue Aug 10 09:20:47 2021 +0100 nsiproxy: Implement IPv4 neighbour enumerate_all. Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Adding some traces shows that the failure happens on a link local entry: AF_INET: 5 InterfaceIndex=10 state=0/0 s_addr=169.254.169.254 I have not identified the corresponding network interface. Also, given that cw-rx460 ad cw-gtx560 are very similar I would expect both to have this issue and I don't know why that's not the case. However what is interesting is that in both cases the state is NlnsUnreachable so I suspect the is_unreachable / IsUnreachable flags are not necessarily meaningful. -- 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 8

[Bug 51612] New: Stellaris launcher (Paradox) does not launch
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51612 Bug ID: 51612 Summary: Stellaris launcher (Paradox) does not launch Product: Wine Version: 6.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- The game Stellaris installs and works using the stellaris.exe file but the launcher (dowser.exe) fails to launch. I am using Kubuntu 21.04 and this is a fresh installation as it does work on a 2nd PC I have, also Kubuntu 21.04. The only difference of note between the machines is this machine has an AMD 5800X CPU. The terminal returns (duplicated lines removed): scott@scottubuntu:~/.winestella1/drive_c/GOG Games/Stellaris$ WINEPREFIX=~/.winestella1 wine dowser.exe 002c:fixme:winediag:LdrInitializeThunk wine-staging 6.15 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 0034:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 006c:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 006c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0034:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 007c:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 007c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0090:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0090:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 002c:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 002c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 00f8:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 00f8:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0024:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0024:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0100:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0100:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0100:fixme:process:SetProcessPriorityBoost (FFFFFFFFFFFFFFFF,1): stub 0118:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0118:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0120:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0120:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0128:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0128:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. scott@scottubuntu:~/.winestella1/drive_c/GOG Games/Stellaris$ wine: Unhandled page fault on write access to 0000000000000000 at address 00007F756DC2CF91 (thread 0070), starting debugger... 0070:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 96 72" (1115) Read the Wine Developers Guide on how to set up winedbg or another debugger I attach the output of this system request. -- 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 28508] New: user32/monitor.ok fails rarely?
by wine-bugs＠winehq.org 20 May '22

20 May '22

http://bugs.winehq.org/show_bug.cgi?id=28508 Bug #: 28508 Summary: user32/monitor.ok fails rarely? Product: Wine Version: 1.3.29 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified Saw this once in a month of runs: ../../../tools/runtest -q -P wine -M user32.dll -T ../../.. -p user32_test.exe.so monitor.c && touch monitor.ok fixme:win:EnumDisplayDevicesW ((null),0,0x22f4d0,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),1,0x22f4d0,0x00000000), stub! monitor.c:269: Test failed: Invalid clip rect: (0 0) x (800 600) err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 0x480x0 @0! (desktop) err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 640x0x0 @0! (desktop) The tests were run in a virtual desktop on os: Ubuntu 11.04, 2.6.38-11-generic, pulseaudio 0.9.22-24-g67d18, Advanced Linux Sound Architecture Driver Version 1.0.23. ram: 3963 MB cpu: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz gpu: GeForce 8500 GT/PCI/SSE2 3.3.0 NVIDIA 270.41.06 -- 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 8

[Bug 52961] New: crypt32:str - test_CertGetNameString() fails on Windows 7
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52961 Bug ID: 52961 Summary: crypt32:str - test_CertGetNameString() fails on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com crypt32:str - test_CertGetNameString() fails on Windows 7: str.c:867: Test failed: line 951: unexpected length 10, expected 11. str.c:871: Test failed: line 951: unexpected value "localhost\x00e". str.c:885: Test failed: line 951: unexpected len 10, expected 11. str.c:894: Test failed: line 951: string is not zero terminated. str.c:867: Test failed: line 952: unexpected length 21, expected 1. str.c:871: Test failed: line 952: unexpected value "a". str.c:877: Test failed: line 952: unexpected str[1] 0x72. str.c:878: Test failed: line 952: str "ric(a)codeweavers.com", string data mismatch. str.c:885: Test failed: line 952: unexpected len 21, expected 1. str.c:886: Test failed: line 952: unexpected value L"aric(a)codeweavers.com\0000". str.c:892: Test failed: line 952: str L"aric(a)codeweavers.c", string data mismatch. str.c:894: Test failed: line 952: string is not zero terminated. str.c:867: Test failed: line 953: unexpected length 10, expected 1. str.c:871: Test failed: line 953: unexpected value "l". str.c:877: Test failed: line 953: unexpected str[1] 0x6f. str.c:878: Test failed: line 953: str "ocalhost", string data mismatch. str.c:885: Test failed: line 953: unexpected len 10, expected 1. str.c:886: Test failed: line 953: unexpected value L"localhost\0000". str.c:892: Test failed: line 953: str L"localho", string data mismatch. str.c:894: Test failed: line 953: string is not zero terminated. str.c:867: Test failed: line 976: unexpected length 8, expected 19. str.c:871: Test failed: line 976: unexpected value "ex1.org\x00n.org\x00rs.co". str.c:885: Test failed: line 976: unexpected len 8, expected 19. str.c:894: Test failed: line 976: string is not zero terminated. str.c:867: Test failed: line 978: unexpected length 8, expected 19. str.c:871: Test failed: line 978: unexpected value "ex3.org\x00n.org\x00rs.co". str.c:885: Test failed: line 978: unexpected len 8, expected 19. str.c:894: Test failed: line 978: string is not zero terminated. https://test.winehq.org/data/patterns.html#crypt32:str A bisect shows that the failures started with the commit below: commit 0c35a851cd73247cb95187acc2e22074f9ca09a3 Author: Paul Gofman <pgofman(a)codeweavers.com> Date: Fri Apr 15 14:44:32 2022 +0300 crypt32: Support CERT_NAME_SEARCH_ALL_NAMES_FLAG in CertGetNameStringW(). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 52908] New: mf:mf - The 64-bit test_wma_decoder() fails on 64-bit Debian 11 + Intel
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52908 Bug ID: 52908 Summary: mf:mf - The 64-bit test_wma_decoder() fails on 64-bit Debian 11 + Intel Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 64-bit test_wma_decoder() fails on my Debian 11 + Intel machine (see fg-deb64-wow64): mf.c:6282: Test failed: ProcessOutput returned 0xd0000001 mf.c:6328: Test failed: ProcessOutput returned 0xd0000001 mf.c:6340: Test failed: ProcessOutput returned 0xd0000001 mf.c:6352: Test failed: ProcessInput returned 0xc00d36b5 https://test.winehq.org/data/patterns.html#mf:mf The last two failures are gone now but the first two are still present. configure does not mention any missing library (besides libhal) in either the 32- or the 64-bit builds. A bisect shows that the failures started with this commit: commit 651e4002ceeb9a15b11a184b5f47a732e26b7e00 Author: Rémi Bernon <rbernon(a)codeweavers.com> AuthorDate: Mon Mar 14 14:43:22 2022 +0100 winegstreamer: Introduce new wg_transform_(push|read)_data functions. And use it to implement WMA decoder Process(Input|Output). The test output is different because ffmpeg WMA decoder outputs data in a different way as native. The data seems valid audio nonetheless, and it shouldn't matter too much. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51931 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52391 Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 10

[Bug 51297] New: d3d8:visual: test_sample_mask() fails on Nvidia (cw-gtx560)
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51297 Bug ID: 51297 Summary: d3d8:visual: test_sample_mask() fails on Nvidia (cw-gtx560) Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d8:visual has a failure in test_sample_mask() on cw-gtx560 (Nvidia): https://test.winehq.org/data/patterns.html#d3d8:visual visual.c:11146: Test failed: Got unexpected colour ffffbcbc. This happens on all Windows versions available on that machine (from Windows 8.1 to Windows 10 2009). This failure also does not happen on any other machine which makes it specific to Nvidia or this graphics card or this driver version (391.35, the latest available at this date). The test was introduced by this commit: commit 30fe080965409e68cc86a04af1935e4944f4b049 Author: Zebediah Figura <z.figura12(a)gmail.com> Date: Fri Apr 30 11:08:26 2021 -0500 d3d8/tests: Port test_sample_mask() from d3d9. Signed-off-by: Zebediah Figura <z.figura12(a)gmail.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 45960] New: Editpad Lite 7 siaplay empty boxes instead of text in some menus
by wine-bugs＠winehq.org 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=45960 Bug ID: 45960 Summary: Editpad Lite 7 siaplay empty boxes instead of text in some menus Product: Wine Version: 3.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Created attachment 62507 --> https://bugs.winehq.org/attachment.cgi?id=62507 screenshot of problem When trying to set the default font, the drop-down screen offers many selections of empty boxes rather than text, see the attachment. This screen is accessed by: 1/ Options>Configure File Type 2/ On the Editor Options tab click the Edit button next to the "Default text layout" drop-down box 3/ in the Text Layout Configuration Window click the down arrow to the right of of the large drop down box to select fonts in the 2nd-from-last left hand window pane called Main Font. The installer is here: https://www.editpadlite.com/download.html This may be the same issue as bug 45959 which I also submitted, I do not have sufficient knowledge to make that judgement. My system: Kubuntu 18.04.01 Wine version 3.17 -- 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 51755] New: Crash in DeepSkyStacker when stacking images.
by WineHQ Bugzilla 19 May '22

19 May '22

https://bugs.winehq.org/show_bug.cgi?id=51755 Bug ID: 51755 Summary: Crash in DeepSkyStacker when stacking images. Product: Wine Version: 6.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dawid.krol(a)gmail.com Distribution: --- Created attachment 70650 --> https://bugs.winehq.org/attachment.cgi?id=70650 crash log When astrophotography images are processed the program crashes. I looked in the wine log but i didn't noticed anythinh suspicous. The program on Windows is working properly. The program requres GDI+ and I installed but it didn't helped. The problem was reported in Wine's AppDB. Steps to reproduce crash 1. Open Deep Sky Stacker 2. Click Open picture files and select DSC_6524.NEF 3. Select dark files and select DSC_6525.NEF 4. Select bias files and select DSC_6538.NEF 5. Click Stack checked pictures 6. Click OK in the popup. Application is crashing when processing dialog is shown. Files for crash reproduction are in these links. https://www.dropbox.com/s/7lv7encmhwvmn7d/DSC_6524.NEF?dl=0 https://www.dropbox.com/s/17q40uq17d8ar7k/DSC_6525.NEF?dl=0 https://www.dropbox.com/s/o9mn1wd3l4kv1sx/DSC_6538.NEF?dl=0 -- 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 44503] New: Failed install of Corel PSP X6
by wine-bugs＠winehq.org 19 May '22

19 May '22

https://bugs.winehq.org/show_bug.cgi?id=44503 Bug ID: 44503 Summary: Failed install of Corel PSP X6 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: neil.ray(a)usa.com Distribution: --- Created attachment 60460 --> https://bugs.winehq.org/attachment.cgi?id=60460 Failed install of Corel PSP X6 Attempted to install, via wine, Corel Paint Shop Pro X6. Encountered a fatal error and was unable to continue. Backtrace log attached. My OS is Linux Mint 18.3 on a 32bit machine. -- 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 4

[Bug 52938] New: Nitro Family
by WineHQ Bugzilla 15 May '22

15 May '22

https://bugs.winehq.org/show_bug.cgi?id=52938 Bug ID: 52938 Summary: Nitro Family Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jon9097(a)gmail.com Distribution: --- Created attachment 72311 --> https://bugs.winehq.org/attachment.cgi?id=72311 Log In the game Nitro Family when you start just a black screen and game sounds. I can hear the cursor moving in the menu, but you can only see a black screen. The problem has been lingering since 2015, and it's about time it was solved. Surely fixing the bug will make it possible to run quite a few games! -- 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 52416] New: Metatogger 7.2: Wine crashes upon launching the software
by WineHQ Bugzilla 15 May '22

15 May '22

https://bugs.winehq.org/show_bug.cgi?id=52416 Bug ID: 52416 Summary: Metatogger 7.2: Wine crashes upon launching the software Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: p10qjuhh(a)duck.com Distribution: --- Created attachment 71672 --> https://bugs.winehq.org/attachment.cgi?id=71672 The backtrace generated by Wine Launching Metatogger at all causes a crash. Download: https://www.luminescence-software.org/download/metatogger/Metatogger-Instal… Name: Metatogger-Installer.exe MD5: 4fc5a6f1c39a95bb754c25207fe2bb9a (This installer is updated semi-regularly by the software maintainer, so determining the version is on you) At the time of writing, 7.2 is the latest release, but this problem is likely to still exist in later versions. -- 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 52407] New: dotnet-sdk-5.0.100-win-x64 simple example fails: error MSB4018: The "AssignCulture" task failed unexpectedly.
by WineHQ Bugzilla 15 May '22

15 May '22

https://bugs.winehq.org/show_bug.cgi?id=52407 Bug ID: 52407 Summary: dotnet-sdk-5.0.100-win-x64 simple example fails: error MSB4018: The "AssignCulture" task failed unexpectedly. Product: Wine Version: 7.0-rc6 Hardware: x86-64 URL: https://download.visualstudio.microsoft.com/download/p r/2892493e-df43-409e-af68-8b14aa75c029/53156c889fc08f0 1b7ed8d7135badede/dotnet-sdk-5.0.100-win-x64.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Note: this happens on version 5.0.100 of the downloadlink, another tested version like dotnet-sdk-5.0.100-rc.2.20479.15-win-x64.exe doesn`t show this, guess something has changed in the code (?) Steps: wget https://download.visualstudio.microsoft.com/download/pr/2892493e-df43-409e-… wine dotnet-sdk-5.0.100-win-x64.exe wine dotnet new wpf -o myapp && cd myapp && wine dotnet run Output: 027c:fixme:nls:ResolveLocaleName stub: L"eo", 0000000028CCC000, 85 C:\Program Files\dotnet\sdk\5.0.100\Microsoft.Common.CurrentVersion.targets(2943,5): error MSB4018: The "AssignCulture" task f ailed unexpectedly. [Z:\home\louis\ramdisk\myapp\myapp.csproj] C:\Program Files\dotnet\sdk\5.0.100\Microsoft.Common.CurrentVersion.targets(2943,5): error MSB4018: System.TypeInitializationE xception: The type initializer for 'Microsoft.Build.Tasks.CultureInfoCache' threw an exception. [Z:\home\louis\ramdisk\myapp\m yapp.csproj] I did a bit of testing and in fact ResolveLocaleName _never_ returns 0, so i guess we could just improve stub a bit to return 1 and get away with it. I`ll attach improved stub that fixes the bug -- 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 8

[Bug 52940] New: [Regression]Assassin's Creed Origins crashes after intro videos with vulkan backend on wine-git
by WineHQ Bugzilla 15 May '22

15 May '22

https://bugs.winehq.org/show_bug.cgi?id=52940 Bug ID: 52940 Summary: [Regression]Assassin's Creed Origins crashes after intro videos with vulkan backend on wine-git Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: e7d86d9c6e58e8e133c606099615b0d9e7940132 Distribution: Debian Hi, When you launch the game from UbisoftConnect, there are 3 intro video (Epilepsy.bk2, pc_warningSaving.bk2 and warning_disclaimer.bk2) and then a splash-screen (screenshot : https://ibb.co/fSC33zX) to access to the main menu. This screenshot has been taken with DXVK, the game has an issue with wined3d opengl/vulkan backend with with wine <= 7.7 (see bug #45358) (https://bugs.winehq.org/attachment.cgi?id=72313) With wine-git the game crashes after the 3 intro video when the splash-screen must appears. I did a regression test and the 1st bad commit is : ###### e7d86d9c6e58e8e133c606099615b0d9e7940132 is the first bad commit commit e7d86d9c6e58e8e133c606099615b0d9e7940132 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Fri Apr 22 15:42:56 2022 -0500 wined3d: Clear Vulkan textures on the GPU in wined3d_texture_vk_load_texture(). Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/wined3d/texture.c | 61 ++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 52 insertions(+), 9 deletions(-) ###### After to revert it, i confirm that the broken splash-screen appears. VKD3D_DEBUG=trace VKD3D_SHADER_DEBUG=trace WINEDEBUG=+d3d,+d3d11,+d3d_shader,+seh log here : https://www.mediafire.com/file/n8gnbe5949mr4rs/AC_Origins_d3d_wine_git.7z/f… -- 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 52827] New: .NET 6 / .NET6 Application "Reloaded II" Fails to Run
by WineHQ Bugzilla 14 May '22

14 May '22

https://bugs.winehq.org/show_bug.cgi?id=52827 Bug ID: 52827 Summary: .NET 6 / .NET6 Application "Reloaded II" Fails to Run Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nekoNexus(a)protonmail.ch Distribution: --- Created attachment 72215 --> https://bugs.winehq.org/attachment.cgi?id=72215 Reloaded-II Vanilla Wine 7.6 Log SHA256 Checksum of Setup.exe: 9f2c200d9049aa2a7729f17b2628f8ff152d10b5d6efbebee4c642b6a37a08db Program version: 1.17.5 Open-source on Github; web archive download link: https://web.archive.org/web/20220416193511/https://objects.githubuserconten… Supposedly requires both .NET 6.x.x runtime x86 and x64 bits ----- Installing the .NET 6 runtime prerequisites and attempting run the application doesn't enable the application to run; it crashes on launch with various errors, one of which mentioning XAML. This application not working also prevents several other applications (namely mod tools) from working as well. (The ones that currently come to mind are Persona 4 Golden PC modding tools.) -- 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 14

[Bug 28126] New: Big Race USA Demo: menu animations and music too fast
by wine-bugs＠winehq.org 14 May '22

14 May '22

http://bugs.winehq.org/show_bug.cgi?id=28126 Summary: Big Race USA Demo: menu animations and music too fast Product: Wine Version: 1.3.26 Platform: x86-64 URL: http://games.softpedia.com/get/Games-Demo/Pro-Pinball- Big-Race-USA-Demo.shtml OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: asb(a)asbradbury.org Created an attachment (id=36038) --> (http://bugs.winehq.org/attachment.cgi?id=36038) bigraceusademo.exe on wine 1.3.26 (no debug channels) In the Big Race USA Demo (or the full Big Race USA game as sold by gog.com), the menu animations (blinking of text and spinning of icons) move far too fast. Additionally, the game music and sound effects are incredibly fast and 'crackly'. I mention both issues as it seems likely they have the same root cause. My CPU is an i5-750 at 2.67Ghz (presumably this problem may not occur on something much slower like an Atom). Workaround: Use cpulimit on the bigraceusademo.exe process. Turning on a noisy enough debug channel will also slow the process down enough that the sound problem will go away. To reproduce, just install the linked demo, run bigraceusademo.exe and observe the rapidly spinning menu items and corrupted audio output. $ sha1sum bigrace.zip fd5cbfc5da9dd29a010cb02a1f847a753a65c2b2 bigrace.zip The demo and full game both work perfectly in Win 7 x64 on the same hardware. I tested in wine 1.0.1, 1.2.3, 1.3.26 and some versions in between. The problem was less pronounced in 1.0.1 (likely due to worse overall performance). I'll attach the output from 1.3.26, though the only relevant line appears to be the following, which seems to be a likely culprit for the problem: fixme:ddraw:ddraw7_WaitForVerticalBlank iface 0x1557b0, flags 0x1, event (nil) stub! -- 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 11

[Bug 47229] New: gog.com - The Void: crashes when entering two game locations
by wine-bugs＠winehq.org 14 May '22

14 May '22

https://bugs.winehq.org/show_bug.cgi?id=47229 Bug ID: 47229 Summary: gog.com - The Void: crashes when entering two game locations Product: Wine Version: 4.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dron2065(a)rambler.ru Distribution: --- Created attachment 64501 --> https://bugs.winehq.org/attachment.cgi?id=64501 Output log of wine before crashing Video game The Void (GOG edittion) crashes with "Unhandled page fault on read access to 0x00000000 at address 0x1953eb7" in the same locations every time. It's make finish game impossible. There are at least two problem places at game. See more in attachment log. -- 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 29

[Bug 47720] New: eac3to performance issues
by wine-bugs＠winehq.org 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=47720 Bug ID: 47720 Summary: eac3to performance issues Product: Wine Version: 4.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Created attachment 65192 --> https://bugs.winehq.org/attachment.cgi?id=65192 wine version eac3to used to work well a year ago but now has a few issues which need to be addressed not least of which is it takes 4 times longer to demux than it does when run under windows. Also the lossless check seems not to be done and certainly is not reported. A number of warnings which are generated apparently needlessly. I have attached screen shots from under wine and under windows which will show clearly the issues. -- 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 8

[Bug 51312] New: dxgi:dxgi: Wrong screen mode order on AMD GPUs (cw-rx460)
by WineHQ Bugzilla 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=51312 Bug ID: 51312 Summary: dxgi:dxgi: Wrong screen mode order on AMD GPUs (cw-rx460) Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dxgi:dxgi gets failures of the form: https://test.winehq.org/data/patterns.html#dxgi:dxgi dxgi.c:1460: Test failed: Mode 3: Modes should have been sorted, refresh rate 59.940060 < 85.000000. dxgi.c:1460: Test failed: Mode 22: Modes should have been sorted, refresh rate 59.940060 < 85.000000. dxgi.c:1460: Test failed: Mode 55: Modes should have been sorted, refresh rate 59.940060 < 75.000000. * These failures happen on all available Windows versions (8.1 to 10 2009). * They also happen regardless of the Radeon driver version: 19.11.3 to 21.4.1. * They don't happen on machines with any other GPU (cw-gtx560 and QEmu VMs). * They also happen systematically so are not probably caused by a threading issue. * So this really looks like a Radeon-specific behavior. The failing test was introduced by the following commit: commit eb2028fa90c41d3b7b8b4f924cd86059c5ba1e0d Author: Andrew Eikum <aeikum(a)codeweavers.com> AuthorDate: Mon Oct 28 16:59:18 2019 +0330 dxgi: Sort reported output modes. Sekiro: Shadows Die Twice depends on this for its mode switching. Signed-off-by: Andrew Eikum <aeikum(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Does the application crash on Windows machines with an AMD GPU? Or does the Radeon driver return the wrong order only on some GPUs? If the application does not crash maybe our order specification is a bit too strict? Given that an application depends on this we probably want Wine to respect the ordering. Just add a broken()? -- 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 52996] New: comdlg32:printdlg fails when OneNote is installed
by WineHQ Bugzilla 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=52996 Bug ID: 52996 Summary: comdlg32:printdlg fails when OneNote is installed Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comdlg32:printdlg fails on cw-gtx560 and cw-rx460 when running Windows 1809 and 1909: printdlg.c:198: driver 'winspool' device 'OneNote' port 'Microsoft.Office.OneNote_16001.11629.20028.0_x64__8wekyb3d8bbwe_microsoft.onenoteim_S-1-5-21-2735375161-1667520140-535807745-1002' printdlg.c:215: Test failed: got 0 with 2 and 00000000 for '' (expected '>1' and '!= NULL') printdlg.c:220: Test failed: got driver 'winspool' (expected '') https://test.winehq.org/data/tests/comdlg32:printdlg.html It turns out these test configurations are the only ones that have this 'OneNote' line. All the others have the following trace instead: printdlg.c:198: driver 'winspool' device 'Microsoft Print to PDF' port 'PORTPROMPT:' So my understanding is that 'Microsoft Print to PDF' is the default printer for all the machines except for these four where "OneNote" is the default instead. I don't know how "OneNote" came to be the default on these machines. I don't think it was intentional on my part. Rather I suspect there was some randomness in the order in which some Windows updates were installed or something like that. For reference the cw-rx460-1909 machine has the following printers: * Fax * Microsoft Print to PDF --> This seems to be the default printer on all other machines. * Microsoft XPS Document Writer * OneNote --> This is the one that's selected by default in notepad, so presumably the default printer. (The Windows 10 1909 GUI does not make that really clear anywhere else that I could find) So it seems like the test should be adjusted to not fail with the OneNote printer. That or that check should be skipped? -- 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 1

[Bug 50368] New: DragonAge Origins Launcher doesn't toggle music status
by WineHQ Bugzilla 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=50368 Bug ID: 50368 Summary: DragonAge Origins Launcher doesn't toggle music status Product: Wine Version: 6.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it Distribution: ArchLinux Until recently the Dragon Age Origins Launcher didn't work at all becouse bug #44185 that was recently fixed. However now, the laucnehr start, it play correctly the music but the toggle button to disable/enable the music doesn't work. This is the flow of what seems the issue: 0164:trace:mci:mciSendStringW (L"pause all", 0074EE48, 100, 00000000) 0164:trace:mci:mciSendStringW verb=L"pause" on dev=L"all"; offset=4 0164:trace:mci:mciSendStringW [-1, MCI_PAUSE, 00000000, 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000] 0164:fixme:mci:MCI_SendCommand unhandled MCI_ALL_DEVICE_ID 0164:trace:mci:mciSendStringW => 117 wine isn't handling correctly the MCI_ALL_DEVICE_ID case in cases others then closing the device. This affect just the launcher (the game should work properly if not regressed recently, still didn't try) so low priority, but other programs may be 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 1

[Bug 52990] New: MFMEv20 Emulator needs user32.RegisterTouchWindow implementation
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=52990 Bug ID: 52990 Summary: MFMEv20 Emulator needs user32.RegisterTouchWindow implementation Product: Wine Version: 6.14 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian With wine-7.8, the application pops up an error dialog on start: RegisterTouchWindow Failed. If the function is hacked to return TRUE instead of FALSE, the application then starts fine. -- 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 1

[Bug 51217] New: RtlWow64IsWowGuestMachineSupported() check fails on w1064v1607 for the 32-bit ntdll:info
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=51217 Bug ID: 51217 Summary: RtlWow64IsWowGuestMachineSupported() check fails on w1064v1607 for the 32-bit ntdll:info Product: Wine Version: 6.8 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:info has a failure on w1064v1607 (Windows 10 64-bit version 1607 running the 32-bit tests): https://test.winehq.org/data/patterns.html#ntdll:info info.c:3024: Test failed: wrong result 0 This is a check of the RtlWow64IsWowGuestMachineSupported() result. The commit that introduced this check is: commit 4f8ede8e7665328a2a3ccd303875e239bf443512 Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Thu Apr 29 17:15:15 2021 +0200 ntdll: Implement RtlWow64IsWowGuestMachineSupported(). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 51078] New: mshtml:events hangs on Windows 10 1709
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=51078 Bug ID: 51078 Summary: mshtml:events hangs on Windows 10 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 69941 --> https://bugs.winehq.org/attachment.cgi?id=69941 Patch to more reliably reproduce the hang mshtml:events sometimes hangs on Windows 10 1709: http://winetest.dolphin/data/patterns.html#mshtml:events For some reason this only happens on Windows 1709 (the reports say this is mshtml 11.0.16299.309). The test proceeds all the way to the end but then does not exit because the mshtml component still has threads running: VSyncHelper Internet Explorer_Hidden MSCTFIME UI Commenting out the test_focus() run gets rid of the hangs. Also running the test with WINETEST_INTERACTIVE=1 greatly increases the probability of getting a hang. I attached a patch that does that and can be used to reproduce the hang on the TestBot's w1064v1709 VM. So this is clearly related to focus. -- 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 52988] New: comctl32:monthcal fails on Windows in Korean because of unexpected IME messages
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=52988 Bug ID: 52988 Summary: comctl32:monthcal fails on Windows in Korean because of unexpected IME messages Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:monthcal fails on Windows in Korean because of unexpected IME messages: monthcal.c:631: Test failed: create parent window: the msg 0x0007 was expected, but got msg 0x0282 instead monthcal.c:631: Test failed: create parent window: the msg 0x0047 was expected, but got msg 0x0024 instead monthcal.c:631: Test failed: create parent window: the msg 0x0005 was expected, but got msg 0x0282 instead monthcal.c:631: Test failed: create parent window: the msg 0x0003 was expected, but got msg 0x0281 instead monthcal.c:631: Test failed: create parent window: the msg sequence is not complete: expected 0000 - actual 0282 monthcal.c:631: Failed sequence create parent window: monthcal.c:631: 0: expected: 0024 - actual: 0024 wp 00000000 lp 0072f630 monthcal.c:631: 1: expected: 0081 - actual: 0081 wp 00000000 lp 0072f5e0 monthcal.c:631: 2: expected: 0083 - actual: 0083 wp 00000000 lp 0072f650 monthcal.c:631: 3: expected: 0001 - actual: 0001 wp 00000000 lp 0072f590 monthcal.c:631: 4: expected: 0018 - actual: 0018 wp 00000001 lp 00000000 monthcal.c:631: 5: expected: 0046 - actual: 0046 wp 00000000 lp 0072f630 monthcal.c:631: 6: expected: 030f - actual: 0046 wp 00000000 lp 0072f630 monthcal.c:631: 7: expected: 0046 - actual: 001c wp 00000001 lp 0000095c monthcal.c:631: 8: expected: 0047 - actual: 0086 wp 00000001 lp 00000000 monthcal.c:631: 9: expected: 001c - actual: 0006 wp 00000001 lp 00000000 monthcal.c:631: 10: expected: 0086 - actual: 0282 wp 00000006 lp 00000000 monthcal.c:631: 11: expected: 0006 - actual: 0282 wp 00000006 lp 00000000 monthcal.c:631: 12: expected: 0281 - actual: 0024 wp 00000000 lp 0072d650 monthcal.c:631: 13: expected: 0282 - actual: 0282 wp 00000006 lp 00000000 monthcal.c:631: 14: expected: 0007 - actual: 0281 wp 00000001 lp c000000f monthcal.c:631: 15: expected: 0047 - actual: 0282 wp 00000002 lp 00000000 monthcal.c:631: 16: expected: 0083 - actual: 0007 wp 00000000 lp 00000000 monthcal.c:631: 17: expected: 0005 - actual: 0047 wp 00000000 lp 0072f630 monthcal.c:631: 18: expected: 0003 - actual: 0005 wp 00000000 lp 01d701ee monthcal.c:631: 19: expected: nothing - actual: 0003 wp 00000000 lp 001a0003 monthcal.c:655: old style: 0x50800000, new style: 0x50800002 monthcal.c:655: old style: 0x50800000, new style: 0x50800000 monthcal.c:655: old style: 0x50800002, new style: 0x50800000 monthcal.c:655: old style: 0x50800002, new style: 0x50800002 monthcal.c:655: old style: 0x50800000, new style: 0x50800001 monthcal.c:655: old style: 0x50800000, new style: 0x50800000 monthcal.c:655: old style: 0x50800001, new style: 0x50800000 monthcal.c:655: old style: 0x50800001, new style: 0x50800001 https://test.winehq.org/data/patterns.html#comctl32:monthcal WM_GETMINMAXINFO == 0x0024 WM_IME_SETCONTEXT == 0x0281 WM_IME_NOTIFY == 0x0282 create_parent_window_seq[] already has some optional IME messages so it looks like more need to be added / moved to another place. The WM_GETMINMAXINFO is new 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.

1 1

[Bug 39659] New: comctl32:button test gets unexpected WM_CANCELMODE on my Windows 8 laptop
by wine-bugs＠winehq.org 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=39659 Bug ID: 39659 Summary: comctl32:button test gets unexpected WM_CANCELMODE on my Windows 8 laptop Product: Wine Version: 1.8-rc1 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Created attachment 52866 --> https://bugs.winehq.org/attachment.cgi?id=52866 log of test failure Test report: https://test.winehq.org/data/1d19eb15d4abfdd14dccc5ac05b83c0ee1a1ace1/win8_… Message tests calling SetFocus() on a button fail on my Windows 8 machine, because they get a WM_CANCELMODE message they weren't expecting. I have no idea what's special about my setup. It doesn't matter if I run the test stand-alone or with the full test suite, or if I run it as a dedicated user with a default configuration. -- 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 30875] New: Unable to deselect character blocks in BMFont
by wine-bugs＠winehq.org 12 May '22

12 May '22

http://bugs.winehq.org/show_bug.cgi?id=30875 Bug #: 30875 Summary: Unable to deselect character blocks in BMFont Product: Wine Version: 1.5.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dav75uk(a)yahoo.co.uk Classification: Unclassified Run BMFont (http://www.angelcode.com/products/bmfont/) and click on some of the checkboxes to the right to select characters to be included. It is not possible to uncheck the checkboxes. Workaround is to unselect one of the characters (click on a character in that range) which changes the full checked box to a part check box. The part check box can be unselected. -- 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 7

[Bug 52911] New: ole32:moniker fails on Windows in the UTF-8 codepage
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=52911 Bug ID: 52911 Summary: ole32:moniker fails on Windows in the UTF-8 codepage Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ole32:moniker fails on Windows in the UTF-8 codepage: moniker.c:2189: Test failed: IsEqual failed with error 0x000001 [...] https://test.winehq.org/data/patterns.html#ole32:moniker So the failures happen because moniker1 and moniker2 are always different. Adding a call to winetest_push_context() shows that the failures all happen for string 2 which ole32:moniker uses to skip tests on code pages where there are round-trip issues: {0xc0, 0xc1, 0xc2, 0xc3, 0xc4, 0xc5, 0xc6, 0xc7, 0xc8, 0xc9, 0xca, 0xcb, 0xcc, 0xcd, 0xce, 0xcf, 0xd0, 0}, [...] skip("string 2 doesn't round trip in codepage %u\n", GetACP() ); So it looks like the skip fails to trigger for the UTF-8 codepage (or that we should do something else to make the UTF-8 case work). -- 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 52986] New: d3d9:device - In Wine test_vertex_buffer_read_write() fails on on cw-rx460
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52986 Bug ID: 52986 Summary: d3d9:device - In Wine test_vertex_buffer_read_write() fails on on cw-rx460 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d9:device - In Wine test_vertex_buffer_read_write() only succeeds on cw-rx460: device.c:13967: Test failed: Got unexpected value 3.00000000e+000, i 0. device.c:13967: Test failed: Got unexpected value 3.00000000e+000, i 1. device.c:13967: Test failed: Got unexpected value 3.00000000e+000, i 2. https://test.winehq.org/data/patterns.html#d3d9:device This is specific to this machine so it seems likely that this is related to the graphics card / driver. -- 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 0

[Bug 52985] New: d3d9:device - test_reset_fullscreen() gets an unexpected WM_SIZE message with fvwm
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52985 Bug ID: 52985 Summary: d3d9:device - test_reset_fullscreen() gets an unexpected WM_SIZE message with fvwm Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Created attachment 72354 --> https://bugs.winehq.org/attachment.cgi?id=72354 The TestBot's fvwm configuration d3d9:device - test_reset_fullscreen() gets an unexpected WM_SIZE message with fvwm: device.c:4822: Test failed: Received unexpected WM_SIZE message. https://test.winehq.org/data/patterns.html#d3d9:device This failure happens on cw-gtx560, cw-rx460 and debian11 VM which all run Debian 11 with fvwm, and on debiant VM which runs Debian Testing with fvwm. But it does not happen on fg-deb64 which runs Debian 11 too, but with KDE's window manager. So it is pretty likely that this failure only happens when running fvwm. -- 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 1

[Bug 52984] New: d3d8:device - test_cursor_pos() missing a MOUSEMOVE on cw-gtx560 and cw-rx460
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52984 Bug ID: 52984 Summary: d3d8:device - test_cursor_pos() missing a MOUSEMOVE on cw-gtx560 and cw-rx460 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d8:device - test_cursor_pos() is missing a MOUSEMOVE most of the time on cw-gtx560 and cw-rx460: device.c:1324: Test failed: Didn't receive MOUSEMOVE 0 (50, 50). https://test.winehq.org/data/patterns.html#d3d8:device This happens almost systematically on cw-gtx560 and cw-rx460 with Windows 10 1709 to 1909 but happens much less frequently with more recent Windows versions. Also it never happens in the TestBot VMs running the same Windows versions and also does not happen on fgtb-w10pro64-rx550. So it may be related to the set of display modes that the monitor supports which would explain why the KVM-connected machines are impacted and not the others. Or it could be related to the GPU drivers and fgtb-w10pro64-rx550 just got lucky because it's on a more recent Windows 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.

1 1

[Bug 52935] New: comctl32:tab - test_tab(-1&-3) fails on Windows with the UTF-8 codepage
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52935 Bug ID: 52935 Summary: comctl32:tab - test_tab(-1&-3) fails on Windows with the UTF-8 codepage Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:tab's test_tab(-1&-3) fails on Windows with the UTF-8 codepage: tab.c:591: Testing with default MinWidth tab.c:579: Test failed: with icon, set size > icon: Expected [51,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [51,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [51,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [54,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [54,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [54,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [57,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [57,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [57,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [60,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [60,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [60,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [63,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [63,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [63,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [66,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [66,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [66,1] got [48,1] tab.c:593: Testing with MinWidth set to -3 tab.c:579: Test failed: with icon, set size > icon: Expected [51,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [51,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [51,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [54,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [54,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [54,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [57,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [57,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [57,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [60,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [60,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [60,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [63,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [63,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [63,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [66,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [66,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [66,1] got [48,1] https://test.winehq.org/data/patterns.html#comctl32:tab Hindi + UTF-8 is the only locale where this test fails on Windows at this time. In particular there is no failure on the standard Hindi locale (English system locale) so this appears to be specific to UTF-8. -- 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 52939] New: advapi32:registry - test_RegNotifyChangeKeyValue() has an intermittent failure on all Windows versions
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52939 Bug ID: 52939 Summary: advapi32:registry - test_RegNotifyChangeKeyValue() has an intermittent failure on all Windows versions Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 72312 --> https://bugs.winehq.org/attachment.cgi?id=72312 Loop on test_RegNotifyChangeKeyValue() to reproduce the event failures advapi32:registry's test_RegNotifyChangeKeyValue() has an intermittent failure on all Windows versions: registry.c:3471: Test failed: expected ERROR_SUCCESS, got 6 registry.c:3599: Test failed: expected WAIT_OBJECT_0, got 258 https://test.winehq.org/data/patterns.html#advapi32:registry The failure is pretty rare so it is likely to cause false positives. The attached patch makes it possible to systematically reproduce the issue, at least on my test VM. With the 10000 loops I get 4 to 5 cases with the failure (so a rate of 0.05%) and a test run still takes under 8 seconds. -- 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 52925] New: usp10:usp10 The wgDefault check fails on Windows in non-basic locales (Hebrew, Japanese, etc)
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52925 Bug ID: 52925 Summary: usp10:usp10 The wgDefault check fails on Windows in non-basic locales (Hebrew, Japanese, etc) Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: usp10 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com usp10:usp10's wgDefault check in test_ScriptGetFontProperties() fails on some bitmap fonts in a number of locales: * Arabic usp10.c:2591: Test failed: bitmap font System wgDefault 0126, tmDefaultChar 0085 usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 0126, tmDefaultChar 0085 usp10.c:2591: Test failed: bitmap font MS Serif wgDefault 0126, tmDefaultChar 0085 usp10.c:2591: Test failed: bitmap font MS Sans Serif wgDefault 0126, tmDefaultChar 0085 * Hebrew usp10.c:2591: Test failed: bitmap font Small Fonts wgDefault 01ac, tmDefaultChar 0080 * Hindi + UTF-8 (no failure for plain Hindi) usp10.c:2591: Test failed: bitmap font System wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Courier wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font MS Serif wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font MS Sans Serif wgDefault 00fd, tmDefaultChar 0081 usp10.c:2591: Test failed: bitmap font Small Fonts wgDefault 00fd, tmDefaultChar 0080 * Japanese usp10.c:2591: Test failed: bitmap font FixedSys wgDefault 00f0, tmDefaultChar 00a0 usp10.c:2591: Test failed: bitmap font @FixedSys wgDefault 00f0, tmDefaultChar 00a0 * Chinese usp10.c:2591: Test failed: bitmap font System wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font @System wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Terminal wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font @Terminal wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font @Fixedsys wgDefault 00ac, tmDefaultChar 0080 https://test.winehq.org/data/patterns.html#usp10:usp10 In each case we get the expected value on Windows with a number of fonts but there are some exceptions that cause the failures. For a given locale the exceptions all have the same wgDefault value which means there is probably some logic to it. So we either need to come up with a better way to find the expected wgDefault value, or to radically loosen the test, or to restrict the test to some 'safe' fonts, or to remove the test entirely. -- 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 52981] New: windows.media.speech:speech - SpeechRecognizer fails to initializes with elevated privileges
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52981 Bug ID: 52981 Summary: windows.media.speech:speech - SpeechRecognizer fails to initializes with elevated privileges Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Most of test_SpeechRecognizer() is skipped when run with elevated privileges: speech.c:896: SpeechRecognizer default language L"fr-FR". speech.c:1172: Tests skipped: Could not init SpeechRecognizer with default language! https://test.winehq.org/data/patterns.html#windows.media.speech:speech The involved lines are: 919 hr = RoActivateInstance(hstr, &inspectable); 922 if (hr == S_OK) ... 1170 else if (hr == SPERR_WINRT_INTERNAL_ERROR) /* Not sure when this triggers. Probably if a language pack is not installed. */ 1171 { 1172 win_skip("Could not init SpeechRecognizer with default language!\n"); An analysis of the test results across Windows versions shows that we see this SPERR_WINRT_INTERNAL_ERROR on Windows 10 >= 1809: cw-gtx560-1507 S_OK cw-rx460-1507 S_OK w1064v1507 S_OK w1064v1607 S_OK cw-gtx560-1709 S_OK cw-rx460-1709 S_OK w1064v1709 S_OK cw-gtx560-1809 skipped cw-rx460-1809 skipped w1064v1809 skipped cw-gtx560-1909 skipped cw-rx460-1909 skipped w1064v1909 skipped w1064v2004 skipped cw-gtx560-2009 skipped cw-rx460-2009 skipped w1064v2009 skipped cw-gtx560-21h1 skipped cw-rx460-21h1 skipped w10pro64-21h1 skipped cw-gtx560-21h2 skipped cw-rx460-21h2 skipped w1064-21h2 skipped w10pro64-21h2 skipped So far that looks pretty clear cut: Microsoft changed things around 1809 such that processes running with elevated privileges cannot / are not allowed to perform speech recognition. That would mean the test should drop the privileges so it can run on any platform. However the test was not skipped in the w10pro64v2004 and w10pro64 (21H1) test configurations... until they were upgraded. So this indicates that there may be a way to get this test to work even while retaining elevated privileges. But how? To help debug the issue I added two test configurations: * w10pro64restored The w10pro64 VM restored from a backup of the pre-2022-05 upgrade VM. Surprisingly the test still ends up being skipped! * w10pro64old Luckily before the upgrade I moved the old VM out of the way. It is now available as w10pro64old with the exact same live snapshots. Comfortingly the test is still not skipped, even after waiting some time and rebooting. That last part indicates there may be something either in the way the TestBot creates the live snapshots, or in the "WineTestBot VMs" checklist I go through when preparing the VMs and the cw-* machines (but then the clear 1809 cutoff point is quite a coincidence). -- 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 0

[Bug 33621] New: [UWIN] ksh93 from UWIN generates a lot of fixme warnings
by wine-bugs＠winehq.org 11 May '22

11 May '22

http://bugs.winehq.org/show_bug.cgi?id=33621 Bug #: 33621 Summary: [UWIN] ksh93 from UWIN generates a lot of fixme warnings Product: Wine Version: 1.5.30 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: simon.toedt(a)gmail.com Classification: Unclassified Running ksh93 (Korn Shell 93) from the UWIN (Unix emulation on Windows) toolkit generates a lot of "fixme" warnings and the shell is generally not useable. The goal is to use WINE for automated testing without having to fire up a full blown Windows system each time in VMware or real iron. Steps to test: 1. Install UWIN: > wget --http-user="I accept www.opensource.org/licenses/eclipse" --http-passwd="." 'http://www2.research.att.com/~gsf/download/beta/uwin-base.2013-02-08.win32.…' > wine uwin-base.2013-02-08.win32.i386.exe 2. Run Windows/UWIN version of ksh93: wine64 'C:\Program Files/UWIN/usr/bin/ksh.exe' fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:process:SetProcessShutdownParameters (00000000, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:advapi:LsaOpenPolicy ((null),0x23f980,0x00000001,0x23f950) stub fixme:advapi:LsaClose (0xcafe) stub fixme:netbios:NetServerEnum Stub ((null) 100 0x23f440 -1 0x23fbb8 0x23fbc8 24 (null) (nil)) fixme:netapi32:NetGetDCName ((null), (null), 0x23f448) stub! fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0xf70850,symt:0xfce150) fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 -> r8/336) fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 -> r8/336) fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x20e2370,symt:0x2140480) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2914e98,symt:0x2970264) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2943cb0,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2914e90,symt:(nil)) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x36b3448,symt:0x378fa1c) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743718,symt:0x37781b4) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743658,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x37425a0,symt:0x3754e38) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x15 at ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil)) fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented wine version is wine-1.5.30. Wine versions older than wine-1.5.30 may not work as described in bug 33619. IMO the most pressing problems are: 1. fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. 2. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented 3. fixme:netapi32:NetUserGetInfo Level 3 is not implemented 4. fixme:ntdll:NtSetInformationToken unimplemented class 4 5. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented -- 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 10

[Bug 52968] New: CPU BoostTester manages to run only on real cores in Windows, but not with wine
by WineHQ Bugzilla 09 May '22

09 May '22

https://bugs.winehq.org/show_bug.cgi?id=52968 Bug ID: 52968 Summary: CPU BoostTester manages to run only on real cores in Windows, but not with wine Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christian.frank(a)gmx.de Distribution: --- Hi, the following tiny porgram is used to test the boost capability of cpus. It detects real cores and only tests those, not the smt siblings. On windows it manages to run on the real cores only. On Linux it runs on the cores 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30 I am using a 5950x. The real cores are 0-15. The siblings ar 16-31. 0+16 is a pair, 1+17, 2+18 etc.. So instead of testing the 16 real cores, it is testing only 8 + siblings. The software is availible here, including source. I don't know if the software is doing some strange things to detect the real cores or if the issue is on the wine side. As the source is just a handful of c++ code, someone with experience might take a look and judge where the problem is, wine or the program. Here is the link: https://github.com/jedi95/BoostTester Many thx ! -- 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 52976] New: Daagon Map Maker on itch.io crash
by WineHQ Bugzilla 08 May '22

08 May '22

https://bugs.winehq.org/show_bug.cgi?id=52976 Bug ID: 52976 Summary: Daagon Map Maker on itch.io crash Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: registry Assignee: wine-bugs(a)winehq.org Reporter: ildaniel999(a)hotmail.com Distribution: --- Created attachment 72346 --> https://bugs.winehq.org/attachment.cgi?id=72346 wine file loads up to 100%, changes screen settings, but 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.

1 0

[Bug 52684] New: Command and Conquer Generals (and C&C Zero Hour) have no ground textures
by WineHQ Bugzilla 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=52684 Bug ID: 52684 Summary: Command and Conquer Generals (and C&C Zero Hour) have no ground textures Product: Wine Version: 7.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: bender647(a)yahoo.com Regression SHA1: 1632b8e7a419ebf256c4a356a58d505ef918f2fe Distribution: Slackware Introduced in wine-7.3 with commit 1632b8e7a419ebf256c4a356a58d505ef918f2fe, the C&C Generals game engine does not draw ground textures. The ground (or water) area is black. Reverting to wine-7.2, or applying this commit as a reverse-patch on wine-7.4 will fix the issue. The commit was found by bisecting the git tree. This symptom appears in older bug reports but the fixes there do not appear to work now. Tested on two platforms, but both were Intel i915 graphics. If necessary, I can get access to an Nvidia platform. To reproduce: 1. A free demo is available for download to run the game: https://www.moddb.com/downloads/start/111369 (https://www.moddb.com/games/cc-generals/downloads/command-conquer-generals-…). 2. Install in 32-bit prefix. 3. Run with `wine start generals.exe -nologo` and the game engine will be seen running behind the main menu. The ground will be blank if the bug is present. Verified to affect: https://appdb.winehq.org/objectManager.php?sClass=version&iId=4881 https://appdb.winehq.org/objectManager.php?sClass=version&iId=35407 Likely also: https://appdb.winehq.org/objectManager.php?sClass=version&iId=1717 -- 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 24

[Bug 45098] New: FrostPunk: multiple graphical glitches
by wine-bugs＠winehq.org 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=45098 Bug ID: 45098 Summary: FrostPunk: multiple graphical glitches Product: Wine Version: 3.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)embed.me.uk Distribution: --- Created attachment 61268 --> https://bugs.winehq.org/attachment.cgi?id=61268 FrostPunk log With patch posted in https://bugs.winehq.org/show_bug.cgi?id=45080 the game sucessfully starts however there are severe graphical glitches which render it unplayable. 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 15

[Bug 2155] Failure of SetFocus, SetActiveWindow and SetForegroundWindow
by WineHQ Bugzilla 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=2155 Ker noa <blue-t(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t(a)web.de -- 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 0

[Bug 52771] New: Wine console creation breaks comctl32:button, dinput:keyboard, user32:dialog, user32:input, user32:monitor and user32:win
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52771 Bug ID: 52771 Summary: Wine console creation breaks comctl32:button, dinput:keyboard, user32:dialog, user32:input, user32:monitor and user32:win Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The way Wine creates the window for console applications breaks comctl32:button, dinput:keyboard, user32:dialog, user32:input, user32:monitor and user32:win. https://test.winehq.org/data/patterns.html#comctl32:button https://test.winehq.org/data/patterns.html#dinput:keyboard https://test.winehq.org/data/patterns.html#user32:dialog https://test.winehq.org/data/patterns.html#user32:input https://test.winehq.org/data/patterns.html#user32:monitor https://test.winehq.org/data/patterns.html#user32:win These all started failing in Wine on 2022-03-17 with the commit below (also referenced in bug 52761): commit f034084d49b354811096524d472ae5172ac1cebf Author: Eric Pouech <eric.pouech(a)gmail.com> Date: Thu Mar 17 08:27:28 2022 +0100 kernelbase: Handle corner case in CreateProcess. In CreateProcess, if: - parent isn't attached to a console - CreateProcess's flag isn't set with DETACHED_PROCESS nor CREATE_NEW_CONSOLE - child is a CUI program then a console must be allocated for the child. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52048 Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The way the TestBot starts the tests in Wine is this [1]: testagentd (Unix, no terminal) \- shell script (sh Unix, no terminal) \- WineTest.pl (perl Unix, no terminal) \- ./wine TestLauncher (Windows CUI, no console) \- unit test (Windows CUI) -> creates a console \- unit test can recurse upon itself (CUI) I will now try to summarize the current understanding of the issue from the wine-devel discussion [2], using the above figure as a reference: 1. testagentd is a daemon so it does not have an associated terminal. 2. When ./wine does not have a terminal it does not create a console window, even when starting a console application. This is so wine can be used for background (batch) tasks without requiring a X session or popping up windows all over the place. 3. But when a Windows application calls CreateProcess() without DETACHED_PROCESS, a console does get created. This is what happens when TestLauncher starts a unit test. 4. While the console object is created synchronously in the wineserver process, the actual window is created asynchronously (by wineconsole). This causes it to pop up while the unit test as already started, which confuses the tests that check the window hierarchy, the focus, etc. There are two ways the above differ from Windows: 1. I believe Windows creates both the console object and the matching window synchronously. So even if the console was created when starting the test unit there should be no failure. 2. On Windows the shell script is replaced by a batch script which triggers the console creation. So the console creation happens a bit earlier which could also mask any window creation delay. The reason why f034084d49b3 made a difference is that before Wine was not creating console windows. [1] More details on the different ways the TestBot starts the tests: https://www.winehq.org/pipermail/wine-devel/2022-April/212550.html [2] March: https://www.winehq.org/pipermail/wine-devel/2022-March/212330.html April: https://www.winehq.org/pipermail/wine-devel/2022-April/212513.html -- 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 14

[Bug 45388] New: user32: edit fails on Traditional Chinese and Korean locales
by wine-bugs＠winehq.org 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=45388 Bug ID: 45388 Summary: user32:edit fails on Traditional Chinese and Korean locales Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:edit fails with the following errors on Traditional Chinese and Korean locales: edit.c:1489: Test failed: 0: got 1, 1 edit.c:1510: Test failed: 0: got 1, 1 edit.c:1524: Test failed: 0: got 1, 1 edit.c:1538: Test failed: 0: got 1, 1 See: * Source matching the above https://source.winehq.org/git/wine.git/?a=blob;f=dlls/user32/tests/edit.c;h… * user32:edit WineTest failures https://test.winehq.org/data/tests/user32:edit.html The errors can be reproduced on the newtb-wvistau64-zh-cn TestBot VM, and also happen on fg-win7u64-1spie9-ko. -- 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 3

[Bug 52869] New: kernel32:locale - test_CompareStringA() fails in Wine in Hindi
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52869 Bug ID: 52869 Summary: kernel32:locale - test_CompareStringA() fails in Wine in Hindi Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- test_CompareStringA() started failing in Wine in Hindi recently: locale.c:1884: Test failed: expected CSTR_LESS_THAN, got 2 locale.c:1886: Test failed: expected CSTR_GREATER_THAN, got 2 https://test.winehq.org/data/patterns.html#kernel32:locale A bisect shows this failure started with the commit below: commit 8993e15cfa5b77ac2487239354ffe63bbc5e562d Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Apr 11 17:21:47 2022 +0200 kernelbase: Support UTF-7/8 codepages in get_codepage_table(). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 52743] New: regression cannot write to _fdopen'ed stdout
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52743 Bug ID: 52743 Summary: regression cannot write to _fdopen'ed stdout Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xantares09(a)hotmail.com Distribution: --- since wine 7.2, opening stdout with _fdopen and printing into it crashes ``` #include <stdio.h> #include <io.h> #include <fcntl.h> int main() { FILE * m_stdout = _fdopen(_fileno(stdout), "wb"); fprintf(m_stdout, "foo\n"); fclose(m_stdout); return 0; } $ x86_64-w64-mingw32-gcc main.c $ wine a.exe ... wine: Unhandled page fault on read access to 0000000000000050 at address 0000000170059685 (thread 0128), starting debugger... ... ``` For context, this is what qt-xmlpatterns does: https://github.com/qt/qtxmlpatterns/blob/dev/tools/xmlpatterns/main.cpp#L184 -- 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 17

[Bug 52362] New: Powershell Core 7 installer hangs forever on Chinese locale (LC_ALL=zh_Han.UTF-8)
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52362 Bug ID: 52362 Summary: Powershell Core 7 installer hangs forever on Chinese locale (LC_ALL=zh_Han.UTF-8) Product: Wine Version: 7.0-rc3 Hardware: x86-64 URL: https://github.com/PowerShell/PowerShell/releases/down load/v7.1.5/PowerShell-7.1.5-win-x64.msi OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Hi, someone i was trying to help someone to get this installed and he reported this to me (I couldn`t reproduce it), that the installer hung for him, and in fact he found that it was due to the fact he was running with LC_ALL=zh_Han.UTF-8 I don`t know anything about these chinese locales, but report anyway as could be a bug in wine (?). reproduce: LC_ALL=zh_Han.UTF-8 5ine msiexec /i PowerShell-7.1.5-win-x64.msi A +relay shows it`s looking for files in directory zh-CN which is not there, though there is zn-Han(s) directories. But just copying zh-Han to zh-CN didn`t help either. Anyway, I guess someone with more knowledge about (Chinese) locales would have lots more clues than i have... -- 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 9

[Bug 52149] New: user32:dialog fails in test_DialogBoxParam() on current Windows 10 21H1
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52149 Bug ID: 52149 Summary: user32:dialog fails in test_DialogBoxParam() on current Windows 10 21H1 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:dialog fails in test_DialogBoxParam() on current Windows 10 21H1: dialog.c:1854: Test failed: got 1407 https://test.winehq.org/data/patterns.html#user32:dialog So instead of failing with an error code of 0, the call below fails with ERROR_CANNOT_FIND_WND_CLASS... which makes sense? ret = DialogBoxParamA(GetModuleHandleA(NULL), "TEST_DIALOG_INVALID_CLASS", 0, DestroyDlgWinProc, 0); It's interesting to note that this failure did not happen on the initial Windows 10 21H1 test configurations (2021-08-23). As far as I can tell it's only after KB5006670 was applied (on 2021-10-21) that the test started failing. Unfortunately this is a cumulative update so it may not help narrow down the cause very much. -- 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 52922] New: The Evil Within crashes before entering the main menu using Vulkan renderer
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52922 Bug ID: 52922 Summary: The Evil Within crashes before entering the main menu using Vulkan renderer Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: e7d86d9c6e58e8e133c606099615b0d9e7940132 Distribution: --- wine: Unhandled page fault on read access to 00007F3B54255B28 at address 00007F32CDDE5A09 (thread 0740), starting debugger... -- 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 52887] New: Get-Computerinfo from NoPowershell crashes
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52887 Bug ID: 52887 Summary: Get-Computerinfo from NoPowershell crashes Product: Wine Version: 7.7 Hardware: x86-64 URL: https://github.com/bitsadmin/nopowershell/releases/tag /1.23 OS: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Created attachment 72275 --> https://bugs.winehq.org/attachment.cgi?id=72275 patch NoPowershell.exe provides a number of commandlets without the need to install it(https://github.com/bitsadmin/nopowershell/releases/tag/1.23). Prerequisite: winetricks -q dotnet48 The commandlet Get-Computerinfo acts as replacement of systeminfo.exe Source: https://github.com/bitsadmin/nopowershell/blob/master/Source/NoPowerShell/C… Currently fails with: Get-ComputerInfo : System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource) at NoPowerShell.Commands.Management.GetComputerInfo.Execute(CommandResult pipeIn) at NoPowerShell.Program.Main(String[] args) Attached patch fixes it, to run into next bug . Next bugs are some missing props from various classes. After adding them (albeit quickly with some hacks) the cmdlet runs. I attach first three patches, rest follows later. -- 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 52847] New: GetACP() returns CP_UTF8 on some debian VM
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52847 Bug ID: 52847 Summary: GetACP() returns CP_UTF8 on some debian VM Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: eric.pouech(a)orange.fr Distribution: --- wine's tests in kernel32/tests/process.c fail on some Debian VM (Dhivehi:Maldives and Hindi:India) debugging it shows: - conhost (in window.c) aborts at startup because TranslateCharsetInfo( GetACP() ...) fails in Wine - both locale return CP_UTF8 from GetACP() - testing on windows vm (Hindi), show that GetACP() returns 1252 CP - moreover, testing on Win11 TranslateCharsetInfo( CP_UTF8 ) succeeds returning the Win11 values for CP_UTF8 in TranslateCharsetInfo let the kernel32:process run "correctly" (ie no longer showing the specific errors related to TranslateCharsetInfo) -- 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 48045] New: comdlg32:filedlg crashes or times out randomly
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=48045 Bug ID: 48045 Summary: comdlg32:filedlg crashes or times out randomly Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 65586 --> https://bugs.winehq.org/attachment.cgi?id=65586 comdlg32:filedlg: Traces to debug random crash / timeouts. comdlg32:filedlg crashes randomly on all Windows versions from Vista to Windows 8 while Windows 10 (at least 1507, 1709 and 1809) gets random timeouts. https://test.winehq.org/data/tests/comdlg32:filedlg.html When successful comdlg32:filedlg does not print much so the standard reports are pretty much useless to spot the place where the test gets stuck on Windows 10, assuming it gets stuck in a specific place rather than just being slow. As for the crashes, they don't trigger the tests exc_filter() so there is no indication of the last successful ok() call. Turning on 'Report successful tests' may be preventing the crash (or these runs just got lucky). It's possible to reproduce the crash while adding the traces in the attached patch. This is not entirely fruitful as the crashes don't seem to always happen in the same place. test_extension() is the place where most issues happen though: https://testbot.winehq.org/JobDetails.pl?Key=59060 -> wvistau64: Crash in test_extension(). Based on the test_extension_helper() traces, it happened in the loop with i=1 so for "TestFilter (*.abc;)\0*.abc;\0". https://testbot.winehq.org/JobDetails.pl?Key=59086 -> w2008s64+exe: Crash on or after test_extension() return https://testbot.winehq.org/JobDetails.pl?Key=59088 -> wvistau64+exe: Crash in test_DialogCancel() https://testbot.winehq.org/JobDetails.pl?Key=59091 -> wvistau64_fr: Spent 39s in test_null_filename() but no timeout https://testbot.winehq.org/JobDetails.pl?Key=59139 -> wvistau64: Crash in test_null_filename() -> wvistau64_fr: Timeout in test_extension() filedlg.c:1048: filter=[TestFilter (*.ab?) lpstrDefExt=NULL] https://testbot.winehq.org/JobDetails.pl?Key=59151 -> wvistau64: Crash in test_extension() filedlg.c:1048: filter=[TestFilter (*.abc.def)] -> wvistau64_fr: Timeout in or after test_mru() filedlg.c:637: 19 test_ok filedlg.c:904: 29 test_getfolderpath filedlg.c:986: 30 test_mru -> w1064v1809_zh_CN: Two failures in test_extension() filedlg.c:1053: Test failed: TestFilter (*.pt*;*.abc): expected TRUE filedlg.c:1059: Test failed: TestFilter (*.pt*;*.abc): Filename is deadbeef, expected deadbeef.xyz Memory corruption, maybe happening quite early in the test? -- 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 52924] New: Guilty Gear XX #Reload: black screen since wine 5.0
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52924 Bug ID: 52924 Summary: Guilty Gear XX #Reload: black screen since wine 5.0 Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: s.guidoni(a)tin.it Distribution: --- Since wine 5.0 the game "Guilty Gear XX ♯Reload" shows a black screen while running. The game starts, the introductory videos are displayed correctly, then the game runs, but the screen is just black, with some blocky piece of graphics flashing now and then across the screen. The sound plays, so one can browse the menu, start a game and so on, but the screen stays black with some bright rectangular shape flashing around. The game is based on DirectX 8.1 and the last wine version that works is 4.21. With wine 4.21, the console output is: 002d:fixme:win:EnumDisplayDevicesW ((null),0,0x33f798,0x00000000), stub! 002f:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts. 002d:err:quartz:GetClassMediaFile Media class not found 002d:err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't work. With wine 5.0.5, it is: 0033:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0033:fixme:d3d:wined3d_swapchain_init Unimplemented swap effect 0x5. 0035:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts. 0033:err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't work. With wine 7.6, it is: 012c:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0x3. 012c:err:winediag:wined3d_dll_init Using the OpenGL renderer. 012c:fixme:imm:ImeSetActiveContext (0x266c88, 1): stub 012c:fixme:imm:ImmReleaseContext (0002010C, 00266C88): stub 012c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 012c:err:d3d_sync:wined3d_cs_create Forcing serialization of all command streams. 012c:err:d3d_sync:wined3d_cs_create Forcing serialization of all command streams. 012c:err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't work. -- 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 52871] New: oleaut32:vartest has failures in Wine in the Arabic and Hebrew locales
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52871 Bug ID: 52871 Summary: oleaut32:vartest has failures in Wine in the Arabic and Hebrew locales Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- oleaut32:vartest has failures in Wine in the Arabic and Hebrew locales: vartest.c:3130: Test failed: VarAbs: expected 0x0,5,1.1, got 0x80020005,8,-1.#IND vartest.c:4073: Test failed: wrong result 80020005 vartest.c:4188: Test failed: wrong result 80020005 vartest.c:4312: Test failed: wrong result 80020005 vartest.c:4444: Test failed: wrong result 80020005 vartest.c:7785: Test failed: VarCmp: 2|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 3|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 4|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 5|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 6|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 7|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 2|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 3|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 4|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 5|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 6|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 7|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 11|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 14|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 17|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 8|0x8000, 20|0x8000: Expected 0x0, got 0x2 vartest.c:7785: Test failed: VarCmp: 11|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 14|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 17|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 20|0x8000, 8|0x8000: Expected 0x2, got 0x0 vartest.c:7785: Test failed: VarCmp: 22|0x8000, 8|0x8000: Expected 0x2, got 0x0 https://test.winehq.org/data/patterns.html#oleaut32:vartest These failures happen in test_VarAbs(), test_VarFix(), test_VarInt(), test_VarNeg(), test_VarRound() and test_VarCmp() but a bisect shows that they all start with this commit: commit ba43e4cfca97a9bba3e6575af82acbf011685862 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Mar 29 22:11:32 2022 +0200 kernelbase: Reimplement number formatting values in GetLocaleInfoW/Ex using the locale.nls data. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> It should be noted that this commit did fix another set of oleaut32:vartest failures (which were likely introduced by 2cd33e6b0fd6). -- 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 52865] New: windows.media.speech:speech has a Windows 10 1507-specific failure
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52865 Bug ID: 52865 Summary: windows.media.speech:speech has a Windows 10 1507-specific failure Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com IAsyncOperation_SpeechRecognitionCompilationResult_get_Completed() unexpectedly returns a handle on Windows 10 1507: speech.c:979: Test failed: Handler had value 0029FC20. https://test.winehq.org/data/patterns.html#windows.media.speech:speech Unsurprisingly a bisect shows that the failures started with the commit that introduced this new test: commit 4926bb148b049f1b60e57091f4aa87a3957aa69e Author: Bernhard Kölbl <besentv(a)gmail.com> Date: Wed Apr 6 18:28:41 2022 +0200 windows.media.speech: Add tests for IAsyncOperation. Signed-off-by: Bernhard Kölbl <besentv(a)gmail.com> Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 52845] New: Recent versions of chromium have broken sandbox again
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52845 Bug ID: 52845 Summary: Recent versions of chromium have broken sandbox again Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Somewhere between chromium-946247 (commit 4e7609b62147866fb7b226fd6efbe1ae4d2f1aca and chromium-946263 (commit 1bd694702105072e57b980512130a3212675ec19) the sandbox got changes so it doesn't work under wine anymore. Result is a black screen and soon a crash. This affects both 32bit and 64bit chromium. Note: chromium should be located inside the WINEPREFIX, it won't run outside! Nightly versions to test with (chrome-win.zip) https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.h… https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.h… I tried to build from source on my Win11 machine, but those versions don't run under wine at all, even if compiling the same commit as the nightly versions. -- 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 9

[Bug 52554] New: Serbian locale mapping cause crash on multiple installshield wizards
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52554 Bug ID: 52554 Summary: Serbian locale mapping cause crash on multiple installshield wizards Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: lei.pero(a)gmail.com Distribution: --- Since commits: kernelbase: Map LANG_SERBIAN_NEUTRAL in ConvertDefaultLocale(). f51e44c1802338cdd41b38efe2757b642b619d6f ntdll: Map LANG_SERBIAN_NEUTRAL in RtlLocaleNameToLcid(). db3e08770fe9bfb6f06a71761e48a40fe9764058 starting with wine-6.2 - when using locale sr_RS.UTF-8, some (specifically older) installers do crash, for example 3DMark03, preventing installation, passing LANG=en_US.UTF-8 EV works as expected with no crash. Reverting those two specific commits solves the issue. Or changing line in: dlls/ntdll/locale.c from: case MAKELANGID( LANG_SERBIAN, SUBLANG_NEUTRAL ): *lcid = LANG_SERBIAN_NEUTRAL; to: case MAKELANGID( LANG_SERBIAN, SUBLANG_NEUTRAL ): *lcid = MAKELCID( 0x02, SORT_DEFAULT ); solves the issue as well, but that basically renders all those commits useless I assume? On the topic, but unrelated to this bug, I can see changes in dlls/kernel32/nls/srl.nls, with commit: kernel32: Update sr-Latn locale definition. 3b3dfda59951b0f42e297f2b9a31ded04a98d4b4 that doesn't seem right to me, srl.nls should stand for Serbian Latin I assume, srm.nls probably stands for m as Montenegro. So, if I'm correct, addition of srm.nls with commit: kernel32: Add sr-Latn-RS locale definition. db2666e9d20f80968ff6b4b0ea1deae20c3c368b should have changes made to srl.lns. I don't know how this is solved for English for example, since neutral should have a specific code not related to any country where language is used (e.g. US, UK, CA etc.), and the code it seems to be sr_CS as it is changed for sr_RS latin locale, where it shouldn't be changed I assume. -- 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 8

[Bug 51181] New: d3d10core:d3d10core fails systematically on AMD GPUs
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=51181 Bug ID: 51181 Summary: d3d10core:d3d10core fails systematically on AMD GPUs Product: Wine Version: 6.8 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com test_instanced_draw() fails systematically in d3d10core:d3d10core on AMD GPUs (and sometimes there is a crash that follows): d3d10core.c:9275: Test failed: Got 0xfff0f010, expected 0xff80f010 at (160, 0), sub-resource 0. d3d10core.c:9275: Test failed: Got 0xfff0f040, expected 0xff80f040 at (240, 0), sub-resource 0. d3d10core.c:9275: Test failed: Got 0xffaaaacc, expected 0xffbbaacc at (480, 0), sub-resource 0. d3d10core.c:9275: Test failed: Got 0xffaaaa90, expected 0xffbbaa90 at (560, 0), sub-resource 0. Notice how this failure does not happen on the machines that have other GPUs such as cw-gtx560 or QEmu VMs, and how this does not depend on the Windows version or Radeon driver version for that matter: https://test.winehq.org/data/patterns.html#d3d10core:d3d10core So it looks like the test expects fails to account for the Radeon driver results for some reason. The commit that introduced this test is: commit fcd549345d96109179b125d31baf9e9073ecf643 Author: Józef Kucia <jkucia(a)codeweavers.com> AuthorDate: Mon Nov 6 10:55:20 2017 +0100 Commit: Alexandre Julliard <julliard(a)winehq.org> CommitDate: Mon Nov 6 19:37:09 2017 +0100 d3d10core/tests: Add test for SV_InstanceID. Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 8

[Bug 43995] New: Uplay - Assassin's Creed 4 Black Flag won't start
by wine-bugs＠winehq.org 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=43995 Bug ID: 43995 Summary: Uplay - Assassin's Creed 4 Black Flag won't start Product: Wine-staging Version: 2.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mi.bar.2001(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59652 --> https://bugs.winehq.org/attachment.cgi?id=59652 Terminal log from `wine AC4BFSP.exe` After clicking the "Play" button in Ubisoft Game Launcher (or launching `wine AC4BFSP.exe`), a window pops up informing, that the game is starting, but it disappears and the game doesn't launch. I don't have the Steam version, just the Uplay one. I've set Windows version to XP, wineprefix is 32-bit. Wine version will probably be visible when I post this, but I'm going to mention it just to be safe. Using Wine 2.20 staging -- 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 38

[Bug 52856] New: kernel32:process fails when Wine has no Unix terminal
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52856 Bug ID: 52856 Summary: kernel32:process fails when Wine has no Unix terminal Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:console fails on the TestBot Wine machines: process.c:1552: Test failed: Opening ConIn process.c:1553: Test failed: Opening ConOut process.c:1556: Test failed: Getting sb info process.c:1557: Test failed: Getting console in mode process.c:1558: Test failed: Getting console out mode process.c:212: 5 failures in child process process.c:1569: Test failed: Getting sb info process.c:1570: Test failed: Getting console in mode process.c:1571: Test failed: Getting console out mode process.c:1582: Test failed: GetLastError: expecting 87 got 12 process.c:1592: Test failed: GetLastError: expecting 87 got 12 process.c:1621: Test failed: Console:SizeX expected 30870, but got 0 process.c:1622: Test failed: Console:SizeY expected 31489, but got 0 process.c:1623: Test failed: Console:CursorX expected 32644, but got 0 process.c:1624: Test failed: Console:CursorY expected 94, but got 0 process.c:1625: Test failed: Console:Attributes expected 0, but got 1 process.c:1626: Test failed: Console:winLeft expected 0, but got 1 process.c:1627: Test failed: Console:winTop expected 4294964424, but got 0 process.c:1628: Test failed: Console:winRight expected 49, but got 0 process.c:1629: Test failed: Console:winBottom expected 30870, but got 0 process.c:1630: Test failed: Console:maxWinWidth expected 31489, but got 0 process.c:1631: Test failed: Console:maxWinHeight expected 11256, but got 0 process.c:1634: Test failed: Console:InputMode expected 0, but got 1 process.c:1635: Test failed: Console:OutputMode expected 7211040, but got 0 process.c:1639: Test failed: Wrong console CP (expected 1252 got 0/0) process.c:1640: Test failed: Wrong console-SB CP (expected 1252 got 0/0) process.c:1645: Test failed: Wrong console mode process.c:1646: Test failed: Wrong console-SB mode https://test.winehq.org/data/patterns.html#kernel32:process The reason is that the TestBot starts Wine from a daemon process which does not have an associated xterm / Konsole / GNOME terminal. This causes Wine to have to allocate a Wine console and that's when things go wrong. A bisect shows that the TestBot is only impacted by this bug since the commit below: commit eff83cd4e00e8ccd4daad05bdd6d76e77664ddd1 Author: Eric Pouech <eric.pouech(a)gmail.com> Date: Mon Apr 11 15:05:09 2022 +0200 kernelbase: Provide a pseudo console environment for initial CUI processes not tied to a Unix tty. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52771 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52761 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52743 Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> But as the commit entry shows this commit also fixed a lot of other issues in the TestBot results (not least of which is getting the wow64 WineTest results in an acceptable shape for test.winehq.org). Also this issue has happened before as evidenced by bugs 25284 and 28220. However those bugs are very old (~2014) so the issue may have been fixed and reappeared (the TestBot has not used a Unix terminal to run the Wine tests since at least 2018-06 (date on local-testagentd.service) and probably 2017 or more (f1d368722b65 tools commit)). Bug 28220 does have a more recent and interesting comment by Esme with regards to handle inheritance: https://bugs.winehq.org/show_bug.cgi?id=28220#c3 -- 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 52559] New: kernel32:resource times out since 2021-12-29 at two win10 testbot systems.
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52559 Bug ID: 52559 Summary: kernel32:resource times out since 2021-12-29 at two win10 testbot systems. Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- I wondered because the windows test patterns showed timeouts for the kernel32:resource [1] since some days. I tried a run with verbose timestamps and got [2]. There it shows gaps of ~6 seconds, and it looks like the delay originates from an execution of EndUpdateResourceA [3]. Unfortunately there are a lot calls for this function and therefore the test times out. Searching the net led me to the autohotkey forums where this function was associated with windows defender. Is windows defender active at these VMs? [1] https://test.winehq.org/data/tests/kernel32:resource.html [2] https://testbot.winehq.org/JobDetails.pl?Key=108231&f201=exe32.report#k201 [3] https://source.winehq.org/git/wine.git/blob/781277de62822c2bac23dc892a99665… -- 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 52079] New: oleacc:main crashes randomly on Windows 10 1709+
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52079 Bug ID: 52079 Summary: oleacc:main crashes randomly on Windows 10 1709+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: oleacc Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com oleacc:main crashes randomly on Windows 10 1709+ in both 32- and 64-bit: main.c:1041: Test failed: V_VT(&v) = 0 main.c:1048: Test failed: V_VT(&v) = 0 main.c:1049: Test failed: V_DISPATCH(&v) = 0000000000000000 main.c:1049: this is the last test seen before the exception 1050:main: unhandled exception c0000005 at 0000000000401597 oleacc:main:1050 done (-1073741819) in 0s Test failed: crash (c0000005) https://test.winehq.org/data/patterns.html#oleacc:main Unsurprisingly a bisect shows that the tests started failing with the commit that introduced the test: commit 1a3db363c6b4065af532a8db1e6309be753b1781 Author: Connor McAdams <cmcadams(a)codeweavers.com> Date: Mon Sep 20 18:03:31 2021 +0200 oleacc: Add Client_get_accFocus tests. Signed-off-by: Connor McAdams <cmcadams(a)codeweavers.com> Signed-off-by: Piotr Caban <piotr(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> At the time the crash happened after line 1037 which points to line 1039 as a likely culprit: 1032 /* Set focus to each child window. */ 1033 SetFocus(btn); 1034 hr = IAccessible_get_accFocus(acc, &v); 1035 ok(hr == S_OK, "hr %#x\n", hr); 1036 ok(V_VT(&v) == VT_DISPATCH, "V_VT(&v) = %d\n", V_VT(&v)); 1037 ok(V_DISPATCH(&v) != NULL, "V_DISPATCH(&v) = %p\n", V_DISPATCH(&v)); 1038 1039 hr = IDispatch_QueryInterface(V_DISPATCH(&v), &IID_IOleWindow, (void**)&ow); 1040 ok(hr == S_OK, "got %x\n", hr); That call has been moved to _check_acc_hwnd() and so the crash now happens in the first QueryInterface() call in that function: hr = IUnknown_QueryInterface(unk, &IID_IOleWindow, (void**)&ow); called from check_acc_hwnd((IUnknown*)V_DISPATCH(&v), btn); -- 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 52904] New: kernel32:locale breaks oleaut32:varformat on Wine in the French locale
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52904 Bug ID: 52904 Summary: kernel32:locale breaks oleaut32:varformat on Wine in the French locale Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:locale breaks oleaut32:varformat on Wine in the French locale: varformat.c:642: Test failed: Unexpected hr 0x80020005 for L"0,000 EUR" varformat.c:649: Test failed: Unexpected hr 0x80020005 for L"0,000 EUR" https://test.winehq.org/data/patterns.html#oleaut32:varformat When starting from a clean wineprefix one would normally get "0,000 €" for this test. But if one runs kernel32:locale before the Euro symbol is replaced with "EUR" which is then not recognized as a currency symbol. A bisect shows that the failures started with this commit: commit 78a33f968461fa3a01d3eec837b4c24f353bc00b Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Tue Mar 29 22:12:25 2022 +0200 kernelbase: Reimplement SetLocaleInfoW(). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The commit modifies both kernel32 and kernel32:locale, and both parts of the patch are needed to reproduce the failure. -- 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 52867] New: System.Globalization.CultureInfo.GetCultureInfo fails for 'en' value
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52867 Bug ID: 52867 Summary: System.Globalization.CultureInfo.GetCultureInfo fails for 'en' value Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Created attachment 72261 --> https://bugs.winehq.org/attachment.cgi?id=72261 stacktrace (filing under ntdll, as that where relevant files were before the commit series that most likely broke it) After upgrading to 7.6, still occurring in 7.7, a regression was made - the last published dnSpy version had been running relatively well in its basic functionality (I'm actually not any good with it), other than minor display glitches; now it stacktraces immediately. I believe the stacktrace makes it clear what happens and why I suspect that locale commit series are at fault here. That release of dnSpy embeds its mono environment, so it's not a wine-mono problem. -- 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 9

[Bug 52858] New: kernel32:file fails in Windows 8.1 on the cw-rx460 machine
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52858 Bug ID: 52858 Summary: kernel32:file fails in Windows 8.1 on the cw-rx460 machine Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:file and msvcp140:msvcp140 fail on the cw-rx460 machine: file.c:905: Test failed: Unexpected error 87. file.c:910: Test failed: Unexpected error 87. https://test.winehq.org/data/patterns.html#kernel32:file These are new tests so unsurprisingly the failures are caused by the commit that introduced them: commit 02faaea93b78d5d53976b2955bef7beffa780d02 Author: Paul Gofman <pgofman(a)codeweavers.com> Date: Mon Apr 11 21:44:36 2022 +0300 kernelbase: Reset last error on success in CopyFileExW(). Signed-off-by: Paul Gofman <pgofman(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> It's unclear why the test only fails on this configuration. Also note that msvcp140:msvcp140 fails in a very similar way in the exact same test configuration: see bug 52857. -- 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 51407] New: kernel32:time's test_GetCalendarInfo() fails in Hindi
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=51407 Bug ID: 51407 Summary: kernel32:time's test_GetCalendarInfo() fails in Hindi Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Created attachment 70263 --> https://bugs.winehq.org/attachment.cgi?id=70263 Broken fix and traces Three GetCalendarInfo() checks fail in Hindi: https://test.winehq.org/data/patterns.html#kernel32:time time.c:728: Test failed: GetCalendarInfoA failed err 87 time.c:731: Test failed: GetCalendarInfoA failed err 87 time.c:738: Test failed: got 0, expected 7 The immediate cause for the failure is that Hindi is one of the few languages for which NLS_IsUnicodeOnlyLcid() returns true. In turn this causes the ANSI GetCalendarInfoA() to return ERROR_INVALID_PARAMETER. The last failure just reflects the fact that the two calls to GetCalendarInfoA() should not have failed. Only Hindi fails and only in Wine. But before declaring this a Wine bug we need to look at Windows. * For some reason probably related to SetWinLocale [1] the system locale of w10pro64_hi is still English. * This causes both the ANSI and Unicode GetCalendarInfo() to return English names (Monday). * Manually setting the system locale to Hindi is possible on Windows 10 2004. What's interesting is the disabled and checked-by-default checkbox in that dialog: [X] Beta: Use Unicode UTF-8 for worldwide language support * And indeed doing that and running the test again results in GetCalendarInfoA() returning UTF-8 strings on Windows! time.c:730: ret=19 sdayname1="\xe0\xa4\xb8\xe0\xa5\x8b\xe0\xa4\xae\xe0\xa4\xb5\xe0\xa4\xbe\xe0\xa4\xb0" सोमवार time.c:735: ret2=19 sdayname1="\xe0\xa4\xb8\xe0\xa5\x8b\xe0\xa4\xae\xe0\xa4\xb5\xe0\xa4\xbe\xe0\xa4\xb0" सोमवार time.c:742: ret2=19 sdayname1=L"\0938\094b\092e\0935\093e\0930" * The beta moniker strongly suggests that this is a new option. Indeed selecting Hindi as the system locale was not possible in Windows 8.1 for instance. * This is probably also why SetWinLocale has trouble setting the system locale to Hindi. So the Windows behavior can be summarized as such: * Return localized values for non-Unicode-only locales. * In older Windows versions setting the system locale to a Unicode-only locale is impossible. * In newer Windows versions setting the system locale to a Unicode-only locale is possible and then it uses UTF-8. Commenting out the Hindi line in NLS_IsUnicodeOnlyLcid() fixes the failures in Wine (see attached patch). But this fix is wrong because it causes GetCalendarInfoA() to return question marks instead of intelligible strings. (it also impacts many APIs but that's probably ok based on the Windows behavior) So Wine should do one of the following: 1. Stick to a 'safe' system locale when $LANG is set to a Unicode-only locale. Typically this would be English. 2. Or use UTF-8 when the system locale is a Unicode-only locale. Option 2 would actually make a lot of sense on Unix systems but it is also more likely to break Windows applications. So option 1 may be the safer (and simpler?) option (for now). [1] https://source.winehq.org/git/tools.git/blob/HEAD:/testbot/bin/SetWinLocale… -- 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 43208] New: Assassin's Creed IV - Black Flag Hangs tightly
by wine-bugs＠winehq.org 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=43208 Bug ID: 43208 Summary: Assassin's Creed IV - Black Flag Hangs tightly Product: Wine-staging Version: 2.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tall89(a)mail.ru CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- When you switch to the Big Inagua location, the game hangs tight, you have to do Cntrl + Atl + Delete to remove the task, then the game closes, then you receive an error message, the program ACBF.exe has a serious error, the application will be closed, we apologize for the inconvenience WINEDEBUG=fixme-all,err+loaddll,err+dll,err+file,err+reg ------ Program AC4BFSP.exe ------ err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733 err:winedevice:async_create_driver failed to create driver L"ps6ajtsb": c0000135 err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from 192.168.0.102:5353 16 aspire89-P55A-UD4.local. AAAA FE80:0000:0000:0000:0A12:F0CA:1A84:437A" err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: ProbeCount 2; will deregister 4 aspire89-P55A-UD4.local. Addr 192.168.0.102" err:eventlog:ReportEventW L"Local Hostname aspire89-P55A-UD4.local already in use; will try aspire89-P55A-UD4-2.local instead" err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from 192.168.0.102:5353 25 102.0.168.192.in-addr.arpa. PTR aspire89-P55A-UD4.local." err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Unexpected conflict discarding 27 102.0.168.192.in-addr.arpa. PTR aspire89-P55A-UD4-2.local." err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error generated. <program> has not been linked, or is not a program object.". err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error generated. <program> object is not successfully linked, or is not a program object.". err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error generated. <program> has not been linked, or is not a program object.". err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error generated. <program> object is not successfully linked, or is not a program object.". err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error generated. <program> has not been linked, or is not a program object.". err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error generated. <program> object is not successfully linked, or is not a program object.". wine: Unhandled page fault on read access to 0x00000063 at address 0x8cfb7f (thread 0047), starting debugger... wine: Unhandled page fault at address 0x7bc5d590 (thread 0012), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 14 168") (1115) Read the Wine Developers Guide on how to set up winedbg or another debugger -- 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 14

[Bug 52864] New: windows.media.speech:speech has a refcount failure on all Windows 10 versions
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52864 Bug ID: 52864 Summary: windows.media.speech:speech has a refcount failure on all Windows 10 versions Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com windows.media.speech:speech fails on all Windows 10 versions: speech.c:968: Test failed: Unexpected refcount 2, expected 1 https://test.winehq.org/data/patterns.html#windows.media.speech:speech This failure is present on all Windows 10 versions except the 1809 and 1909 ones, but probably just because these turn out not to have speech support for English for some reason. So they just skip the test: speech.c:877: SpeechRecognizer default language L"en-US". speech.c:1110: Tests skipped: Could not init SpeechRecognizer with default language! Unsurprisingly a bisect shows that the failures started with the commit that introduced this new test: commit 4926bb148b049f1b60e57091f4aa87a3957aa69e Author: Bernhard Kölbl <besentv(a)gmail.com> Date: Wed Apr 6 18:28:41 2022 +0200 windows.media.speech: Add tests for IAsyncOperation. Signed-off-by: Bernhard Kölbl <besentv(a)gmail.com> Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 52861] New: kernel32:locale fails on Windows 10 1709
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52861 Bug ID: 52861 Summary: kernel32:locale fails on Windows 10 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:locale fails on Windows 10 1709: locale.c:4216: Test failed: failed 0 https://test.winehq.org/data/patterns.html#kernel32:locale This impacts all the Windows 1709 machines but no other Windows version. This is also a new test which was introduced by the commit below: commit b5561c8bba9a613c53ae4669c4adb7450e5f458d Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Wed Mar 23 11:02:57 2022 +0100 ntdll: Support UTF-8 codepage in RtlInitCodePageTable(). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 51460] New: oleaut32:vartest has a todo because Wine uses an outdated currency symbol for Swiss Francs
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=51460 Bug ID: 51460 Summary: oleaut32:vartest has a todo because Wine uses an outdated currency symbol for Swiss Francs Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Wine uses uses "SFr." as the currency symbol for Swiss francs instead of "CHF". According to Wikipedia: "The use of SFr. for Swiss Franc and fr.sv. are outdated" and are not recognized as correct by the "Secrétariat d'État à l'économie". https://en.wikipedia.org/wiki/Swiss_franc This forces the use of a todo in oleaut32:vartest: lcid = MAKELCID(MAKELANGID(LANG_FRENCH,SUBLANG_FRENCH_SWISS),SORT_DEFAULT); WCONVERT(L"3CHF", NUMPRS_CURRENCY|NUMPRS_USE_ALL); todo_wine EXPECT(1,NUMPRS_CURRENCY|NUMPRS_USE_ALL,NUMPRS_CURRENCY,4,0,0); And it may cause oleaut32:varformat to fail when run in a Swiss locale. The "SFr." currency symbol comes from nls/(de|fr|it)s.nls which are generated from Unicode tables by tools/make_unicode so it's not clear how to fix 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.

1 3

[Bug 52866] New: vbscript:run fails in Wine in Arabic and Hebrew
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52866 Bug ID: 52866 Summary: vbscript:run fails in Wine in Arabic and Hebrew Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- vbscript:run fails in Wine in Arabic and Hebrew: run.c:1888: Test failed: unexpected call OnScriptError run.c:2933: Test failed: expected global_success_d run.c:2934: Test failed: expected global_success_i run.c:2936: Test failed: parse_script failed: 800a000d run.c:1204: Test failed: api.vbs: L"Err.number = 13" run.c:1204: Test failed: api.vbs: L"Err.number = 13" run.c:1874: Error in line 1162: 0 L"Type mismatch" run.c:1888: Test failed: unexpected call OnScriptError run.c:2933: Test failed: expected global_success_d run.c:2934: Test failed: expected global_success_i run.c:2936: Test failed: parse_script failed: 800a000d https://test.winehq.org/data/patterns.html#vbscript:run Incidentally these are our two right-to-left test locales so this may be related. A bisect shows that the failures started with this commit: commit ba43e4cfca97a9bba3e6575af82acbf011685862 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Mar 29 22:11:32 2022 +0200 kernelbase: Reimplement number formatting values in GetLocaleInfoW/Ex using the locale.nls data. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 8

[Bug 52857] New: msvcp140:msvcp140 fails in Windows 8.1 on the cw-rx460 machine
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52857 Bug ID: 52857 Summary: msvcp140:msvcp140 fails in Windows 8.1 on the cw-rx460 machine Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com msvcp140:msvcp140 fails in Windows 8.1 on the cw-rx460 machine msvcp140.c:1617: Test failed: Got unexpected err 87. msvcp140.c:1622: Test failed: Got unexpected err 87. https://test.winehq.org/data/patterns.html#msvcp140:msvcp140 These are new tests so unsurprisingly the failures are caused by the commit that introduced them: commit d72d596070eb28fd5f747fb6120d36f66ff93bec Author: Paul Gofman <pgofman(a)codeweavers.com> Date: Mon Apr 11 21:44:35 2022 +0300 msvcp140: Implement _Copy_file(). Signed-off-by: Paul Gofman <pgofman(a)codeweavers.com> Signed-off-by: Piotr Caban <piotr(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The fact that only this specific Windows 8.1 configuration fails makes sense because it is the only one to have msvcp140 and it is a relatively old version: it is installed by the Radeon driver. However: * The w7u VM does have (a much newer) msvcp140 and has no failure. * The w1064v1607 VM has the same msvcp140 version and has no failure either. Furthermore kernel32:file also fails in the same way in the same configuration and shouldn't depend on msvcp140. So it's possible the issue is not related to msvcp140 at all. Here is a summary of the msvcp140 versions on the Windows 7, 8.1 and older Windows 10 machines: Win Machine msvcp140 win7 w7u 14.29.30037.0 win7 w7pro64 missing (at least for 64-bit) win81 cw-gtx560 missing win81 cw-rx460 14.0.23026.0 win81 w8 missing win81 w864 missing win1507 cw-gtx560 missing win1507 cw-rx460 missing win1507 w1064v1507 missing win1607 w1064v1607 14.0.23026.0 -- 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 52828] New: Incorrect instruments in MIDI playback over ALSA
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52828 Bug ID: 52828 Summary: Incorrect instruments in MIDI playback over ALSA Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark(a)darkok.xyz Distribution: --- Created attachment 72216 --> https://bugs.winehq.org/attachment.cgi?id=72216 MIDI file that is played noticably wrong Starting from Wine 7.5, some MIDIs aren't played back properly as they have the incorrect instruments, at least when I've tried playing them using aplaymidi on a VST using SAVIHost. Downloads: https://www.hermannseib.com/programs/savihostx64.zip https://cdn.roland.com/assets/media/zip/scva_win_trial.zip Steps to reproduce: 1. Execute "winetricks mfc90" to get a required DLL 2. Extract scva_win_trial.zip and install the Roland Sound Canvas VA VST 3. Extract savihostx64.zip, and move savihost.exe to "C:\Program Files\Roland\Sound Canvas VA" 4. Rename savihost.exe to "Sound Canvas VA.exe" 5. Run the renamed executable 6. Go to Devices>MIDI, and set Input Port 1 to "Midi Through Port-0" 7. Run "aplaymidi -p 14:0 smr_101.mid" to start playing the MIDI 8. In the VST, click "PART", and the correct instruments should be Vibraphone for the first three, and "KICK&SNARE" for the 11th. However, starting from Wine 7.5, these instruments are incorrectly set to "Piano 1" for the first three, and "Syn. Strings 1" for the 11th. -- 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 14

[Bug 48048] New: urlmon:protocol - The ftp test fail on Vista to Windows 8
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=48048 Bug ID: 48048 Summary: urlmon:protocol - The ftp test fail on Vista to Windows 8 Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: urlmon Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The ftp protocol test in urlmon:protocol fails frequently on Windows from Vista to Windows 8: protocol.c:1188: Test failed: hrResult = 800c0006, expected E_PENDING or S_OK protocol.c:1193: Test failed: dwError = 12111, expected ERROR_SUCCESS protocol.c:3656: Test failed: wait timed out urlmon:protocol:0700 done (258) in 120s Test failed: timed out Note: 800c0006 is INET_E_OBJECT_NOT_FOUND See https://test.winehq.org/data/tests/urlmon:protocol.html -- 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 18635] New: Menu bar is hidden in Adobe Lightroom 2.3
by wine-bugs＠winehq.org 06 May '22

06 May '22

http://bugs.winehq.org/show_bug.cgi?id=18635 Summary: Menu bar is hidden in Adobe Lightroom 2.3 Product: Wine Version: 1.1.22 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: thomas+wine(a)stromberg.org With the Adobe Lightroom 2.3 demo, the menu bar titles (File, etc.) do not display. If you click on the area that they should be, the menu does appear however. Lightroom 2.3 can be downloaded from https://www.adobe.com/cfusion/tdrc/index.cfm?product=photoshop_lightroom (free Adobe login required) I'm not sure where to go about tracing the issue down to, but I did notice the following calls that show that it is calling DrawMenuBar(). 0009:Call user32.GetMenu(0002003c) ret=60030cbe 0009:Ret user32.GetMenu() retval=000000f0 ret=60030cbe 0009:Call user32.GetMenuBarInfo(0002003c,fffffffd,00000000,0032e1a4) ret=60030cec fixme:menu:GetMenuBarInfo (0x2003c,0xfffffffd,0x00000000,0x32e1a4) 0009:Ret user32.GetMenuBarInfo() retval=00000000 ret=60030cec 0009:Call user32.GetSystemMenu(0002003c,00000000) ret=60030beb 0009:Ret user32.GetSystemMenu() retval=00000280 ret=60030beb 0009:Call user32.GetSystemMenu(0002003c,00000000) ret=60030c06 0009:Ret user32.GetSystemMenu() retval=00000280 ret=60030c06 0009:Call user32.GetMenuItemInfoW(00000280,0000f060,00000000,0032e08c) ret=60030c22 0009:Ret user32.GetMenuItemInfoW() retval=00000001 ret=60030c22 0009:Call user32.DrawMenuBar(0002003c) ret=6008d171 -- 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 21

[Bug 52967] New: gdi32:font - test_text_metrics() fails on Windows with en-AE-u8 and plain Hindi
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52967 Bug ID: 52967 Summary: gdi32:font - test_text_metrics() fails on Windows with en-AE-u8 and plain Hindi Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com gdi32:font - test_text_metrics() has a set of failures on Windows that only happen with the English Arab Emirates + UTF-8 locale (en-AE-u8), and in Hindi but without UTF-8 (hi): font.c:3441: Test failed: BIZ UDGothic: expected family 30 got 26. panose 2-11-4-0-... font.c:3441: Test failed: BIZ UDGothic: expected family 30 got 26. panose 2-11-4-0-... font.c:3441: Test failed: @BIZ UDGothic: expected family 30 got 26. panose 2-11-4-0-... font.c:3441: Test failed: @BIZ UDGothic: expected family 30 got 26. panose 2-11-4-0-... font.c:3441: Test failed: BIZ UDMincho Medium: expected family 30 got 16. panose 2-2-5-0-... font.c:3441: Test failed: BIZ UDMincho Medium: expected family 30 got 16. panose 2-2-5-0-... font.c:3441: Test failed: @BIZ UDMincho Medium: expected family 30 got 16. panose 2-2-5-0-... font.c:3441: Test failed: @BIZ UDMincho Medium: expected family 30 got 16. panose 2-2-5-0-... font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho N-B got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho N-B got ff65 expected 1f font.c:3441: Test failed: UD Digi Kyokasho N-B: expected family 30 got 16. panose 2-2-7-0-... font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho N-B got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho N-B got ff65 expected 1f font.c:3441: Test failed: @UD Digi Kyokasho N-B: expected family 30 got 16. panose 2-2-7-0-... font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho NP-B got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho NP-B got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho NP-B got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho NP-B got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho NK-B got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho NK-B got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho NK-B got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho NK-B got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho N-R got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho N-R got ff65 expected 1f font.c:3441: Test failed: UD Digi Kyokasho N-R: expected family 30 got 16. panose 2-2-4-0-... font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho N-R got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho N-R got ff65 expected 1f font.c:3441: Test failed: @UD Digi Kyokasho N-R: expected family 30 got 16. panose 2-2-4-0-... font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho NP-R got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho NP-R got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho NP-R got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho NP-R got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho NK-R got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho NK-R got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho NK-R got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho NK-R got ff65 expected 1f https://test.winehq.org/data/patterns.html#gdi32:font So it's not UTF-8 that causes the failures (still fails in Hindi). It seems to be something that English Arab Emirates and Hindi have in common and that goes away in Hindi + UTF-8. -- 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 1

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