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

[Bug 54751] New: The 64-bit advapi32:registry breaks test_CoGetPSClsid() in ole32:compobj in Wine
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=54751 Bug ID: 54751 Summary: The 64-bit advapi32:registry breaks test_CoGetPSClsid() in ole32:compobj in Wine 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: --- The 64-bit advapi32:registry breaks test_CoGetPSClsid() in ole32:compobj in Wine: compobj.c:1449: Test failed: CoGetPSClsid failed with error 0x80040155 compobj.c:1450: Test failed: got clsid {52222222-1234-1234-1234-56789abcdef0} See https://test.winehq.org/data/patterns.html#ole32:compobj A bisect shows that this started with the commit below: commit 3f82f6ff59f4024f67e2d646883cbea223fba84a Author: Sven Baars <sbaars(a)codeweavers.com> Date: Fri Mar 17 16:52:51 2023 +0100 kernelbase: Use open_key() to obtain any existing Wow6432node in create_key(). -- 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 54738] New: msi:action - The 64-bit test_register_class_info() fails in Wine
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=54738 Bug ID: 54738 Summary: msi:action - The 64-bit test_register_class_info() fails in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- msi:action - The 64-bit test_register_class_info() fails in Wine: action.c:6025: Test failed: key not created action.c:6147: Test failed: key not created See https://test.winehq.org/data/patterns.html#msi:action -- 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 48811] New: StarCraft II fails to load in staging, crashes after trying to start a game in stable
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=48811 Bug ID: 48811 Summary: StarCraft II fails to load in staging, crashes after trying to start a game in stable Product: Wine Version: 5.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: wschmrdr(a)gmail.com Distribution: --- Created attachment 66725 --> https://bugs.winehq.org/attachment.cgi?id=66725 Output occurring when the application crashes. Ever since upgrading from 5.3 to 5.4, StarCraft II has ceased working. On staging, this occurs during the loading screen. I am able to get through the Battle.net app OK, but cannot get to my login authenticating. I have tried switching to stable, but when trying to load up a game, I see the same output issue. Selected the dbghelp component because that's the line that comes up in the output at the time of the crash. -- 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 15

[Bug 55088] New: Program crashes when Common Dialog File open function is called
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=55088 Bug ID: 55088 Summary: Program crashes when Common Dialog File open function is called Product: Wine Version: 6.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: schicktmireurescheisse(a)gmail.com Distribution: --- Created attachment 74644 --> https://bugs.winehq.org/attachment.cgi?id=74644 This is the contents of the error message when the program crashes. When the open file button (the blue button with the folder icon in the upper left corner) of "Entgenderer" is clicked, the software instantly crashes. The program does not get as far to display the open file common dialog. Actually, the program is expected to show the file open dialog in order to enable the user to select a text file. The program was written by me. It is a 16 Bit NE binary (therefore, it actually does not use the comdlg32 DLL, but probably its predecessor - but this category fitted best). The sample program can be retrieved via the link https://github.com/Waldwatz/Wine-reveals-the-truth/releases/ and then the Entgenderer2.zip file has to be downloaded. The terminal output after the program has crashed is: wine: Unhandled page fault on read access to FFFFFFFF at address 00003FD6 (thread 0104), 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 7

[Bug 55055] New: Japanese IME fails to clear composition string when deleting the only remaining character
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=55055 Bug ID: 55055 Summary: Japanese IME fails to clear composition string when deleting the only remaining character Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: imm32 Assignee: wine-bugs(a)winehq.org Reporter: achurch+wine(a)achurch.org Distribution: --- Created attachment 74617 --> https://bugs.winehq.org/attachment.cgi?id=74617 PoC patch Environment: Linux, LANG=ja_JP.UTF-8, ATOK X3 (XIM) Since Wine 8.9 (and possibly 8.8, but not in 8.7), if XIM input results in a composition string being reduced to zero length, the previous composition string remains displayed until further input. For example, using Japanese: 1) Press 'A' -> composition string "あ" -> program displays "あ" 2) Press backspace -> composition string empty -> program still displays "あ" 3) Press 'I' -> composition string "I" -> program displays "い" In step 2, the program should no longer display a composition string, but the "あ" from step 1 remains displayed until further input in step 3 (at which point the displayed composition string is correct again). I first observed this in Final Fantasy XIV, but it reproduces in Notepad as well. Changing dlls/imm32/ime.c:ImeToAsciiEx() to send WM_IME_ENDCOMPOSITION when compstr->dwCompStrLen is zero (see attached patch) seems to fix the bug without any side effects in FFXIV and Notepad, but I have no idea what other effects this might have, or if there needs to be some sort of deeper state tracking for a proper fix. -- 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 55050] New: Wine stucks when creating prefix
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=55050 Bug ID: 55050 Summary: Wine stucks when creating prefix Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: loader Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: julliard(a)winehq.org Regression SHA1: cc2cfb9b792bee681b96c5859084fd6d4d0bbed7 Distribution: --- wine: created the configuration directory '/home/andrey/.wine' 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 002c:err:wineboot:start_services_process Couldn't start services.exe: error 998 -- 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 54993] New: Framemaker 8 crashes in internal search operation
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=54993 Bug ID: 54993 Summary: Framemaker 8 crashes in internal search operation Product: Wine Version: 8.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineps.drv Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- Framemaker 8 crashes in an search operation (which seems to be not related to printing) with an internal error which in the past was a sign of memory corruption. A Bisect shows this commit: a6cb10bba2d05ceca6ba5b1411c450d38defdbb4 is the first bad commit commit a6cb10bba2d05ceca6ba5b1411c450d38defdbb4 Author: Piotr Caban <piotr(a)codeweavers.com> Date: Mon May 15 17:34:23 2023 +0200 wineps: Don't pass PRINTERINFO structure to unixlib. dlls/wineps.drv/init.c | 5 +- dlls/wineps.drv/unixlib.c | 310 +++++----------------------------------------- dlls/wineps.drv/unixlib.h | 5 +- 3 files changed, 35 insertions(+), 285 deletions(-) Please tell me when you need more info (log file for which component?). I understand thats its not easy to narrow this bug from the given information. Thanks! -- 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 26

[Bug 54742] New: The 64-bit advapi32:registry breaks the 32-bit test_redirection() in Wine
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=54742 Bug ID: 54742 Summary: The 64-bit advapi32:registry breaks the 32-bit test_redirection() in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 64-bit advapi32:registry breaks the 32-bit test_redirection() in Wine. To reproduce run the following commands: $ rm -rf ~/.wine # start from a fresh wineprefix $ ./wow64/wine64 wow64/dlls/advapi32/tests/x86_64-windows/advapi32_test.exe registry 2>&1 | grep -E '(Test failed|tests executed)' 0020:registry: 6309 tests executed (156 marked as todo, 0 as flaky, 0 failures), 2 skipped. $ ./wow32/wine wow32/dlls/advapi32/tests/i386-windows/advapi32_test.exe registry 2>&1 | grep -E '(Test failed|tests executed)' registry.c:2837: Test failed: RegOpenKeyExA failed: 2 registry.c:2842: Test failed: RegOpenKeyExA failed: 2 registry.c:2861: Test failed: 00000000: wrong value 32/64 registry.c:2863: Test failed: 00000200: wrong value 32/64 registry.c:2868: Test failed: 00000000: wrong value 64/0 registry.c:2869: Test failed: 00000100: wrong value 64/0 registry.c:2870: Test failed: 00000200: wrong value 64/0 registry.c:3168: Test failed: RegOpenKeyExA failed: 2 registry.c:3174: Test failed: RegOpenKeyExA failed: 2 registry.c:3180: Test failed: RegOpenKeyExA failed: 2 registry.c:3206: Test failed: found equals 0 registry.c:3208: Test failed: found equals 0 registry.c:3210: Test failed: found equals 0 registry.c:3212: Test failed: found equals 1 registry.c:3214: Test failed: wrong number of subkeys: 10 registry.c:3216: Test failed: found equals 1 registry.c:3218: Test failed: found equals 0 registry.c:3220: Test failed: wrong number of subkeys: 10 registry.c:3222: Test failed: found equals 0 0128:registry: 7658 tests executed (74 marked as todo, 0 as flaky, 19 failures), 2 skipped. See https://test.winehq.org/data/patterns.html#advapi32:registry The reason why this failure is only visible with the fg-deb64-wow32 is because this is the only test configuration that runs the 32-bit tests in the same wineprefix as the 64-bit tests. What this shows is that advapi32:registry does not correctly cleans up after itself which has the potential for breaking any test that follows (not just 32-bit ones). -- 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 55051] New: Build regression in wine 8.10 using clang on aarch64 (error in backend: Invalid register name "x18")
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=55051 Bug ID: 55051 Summary: Build regression in wine 8.10 using clang on aarch64 (error in backend: Invalid register name "x18") Product: Wine Version: 8.10 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: pierrick.bouvier(a)linaro.org Distribution: --- When compiling wine for aarch64, a build regression appeared in Wine 8.10 when using clang (any version). This is only present when performing make install, which compiles some DLL. Error is that register x18 is used, and clang reports it as an hard error. gcc reports a warning but does not produce an error (warning: call-clobbered register used for global register variable). --- Reproduction steps (from linux-aarch64, debian bookworm): # download llvm-mingw and add to PATH $ ./configure CC="clang" --without-x --without-freetype --prefix=/usr $ make # works $ make install # fails clang -c -o dlls/msvcr110/onexit.o ... fatal error: error in backend: Invalid register name "x18". ... 3. Running pass 'Function Pass Manager' on module 'dlls/msvcrt/onexit.c'. 4. Running pass 'AArch64 Instruction Selection' on function '@_register_onexit_function' --- Bisect pointed this commit: https://github.com/wine-mirror/wine/commit/56cfbf6b860b46768eeae60eef7dfe0a… include: Only enable the non-inline NtCurrentTeb() on the Unix side. This previous commit introduced register x18 for TEB on arm64 (but commit above makes it active): https://github.com/wine-mirror/wine/commit/7f088b0b1387a3b54c438b839046afad… This previous bug already discussed this topic (https://bugs.winehq.org/show_bug.cgi?id=38780) but I'm not sure what the conclusion would be. --- Compiling with CLAGS=-ffixed-x18 silences clang, but I'm not sure it's the right thing to do. gcc works only because it's a warning and not an error. -- 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 55047] New: d3d test_cursor_clipping() fails
by WineHQ Bugzilla June 23, 2023

June 23, 2023

https://bugs.winehq.org/show_bug.cgi?id=55047 Bug ID: 55047 Summary: d3d test_cursor_clipping() fails Product: Wine Version: 7.21 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression, testcase Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: af902c188ebaf7d6dda3b628409d8c390ab410d5 Distribution: --- I can observe this on two different machines, with at least ddraw and d3d8 tests. It happens regardless of whether the virtual desktop is used. The failure looks like this: ddraw:ddraw1: ddraw1.c:14352: Test failed: SetDis.layMode failed, hr 0x80004001 d3d8:device: device.c:10815: Test failed: Adapter 0: Expect clip rect (0,0)-(640,480), got (1,1)-(639,479). It's not quite consistent, though. One machine can reproduce the ddraw1 failure pretty consistently, enough for me to be able to bisect, but the other seems to fail only intermittently. As a result I can't be 100% sure of the bisect result, but it seems to make sense. -- 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