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

[Bug 54797] New: Lunar Magic 3.33: Crashes with BadWindow unless WINEDEBUG=+all
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54797 Bug ID: 54797 Summary: Lunar Magic 3.33: Crashes with BadWindow unless WINEDEBUG=+all Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xhsdf.misc(a)googlemail.com Distribution: --- Created attachment 74294 --> https://bugs.winehq.org/attachment.cgi?id=74294 warn+all output Starting with Wine 8.4 Lunar Magic crashes on startup with X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 12 (X_ConfigureWindow) Resource id in failed request: 0x60001e8 Serial number of failed request: 600 Current serial number in output stream: 601 It works when WINEDEBUG=+all or trace+all is used, but then it runs very, very slowly. Lunar Magic can be found here: https://fusoya.eludevisibility.org/lm/program.html I'm using up-to-date Archlinux on a Ryzen 7 5700X and Radeon RX 6650 XT running Openbox. -- 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 54848] New: dnsapi:query - test_DnsQuery() fails on Rémi's Wine test machines
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54848 Bug ID: 54848 Summary: dnsapi:query - test_DnsQuery() fails on Rémi's Wine test machines Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dnsapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- dnsapi:query - test_DnsQuery() fails on Rémi's Wine test machines: query.c:66: Test failed: expected record name L"winehq.org", got L"." query.c:67: Test failed: expected record type 1, got 41 query.c:96: Test failed: unexpected CNAME chain See https://test.winehq.org/data/patterns.html#dnsapi:query test_DnsQuery() also has failures on the TestBot's VMs (see bug 54847) but the failures on Rémi's machines are different and not easily explained by the CDN used by winehq.org. They may instead be caused by the cloud environment these machines are running on. These failures happen in new tests that were introduced by this commit: commit 6e2efe54f17e72415b790edf6c9c1f9de5acb9f7 Author: François Gouget <fgouget(a)codeweavers.com> Date: Thu Apr 13 05:51:20 2023 +0200 dnsapi/tests: Test how DnsQuery() handles CNAMEs. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54819 -- 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 48811] New: StarCraft II fails to load in staging, crashes after trying to start a game in stable
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

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 54742] New: The 64-bit advapi32:registry breaks the 32-bit test_redirection() in Wine
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

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 54993] New: Framemaker 8 crashes in internal search operation
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

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 55050] New: Wine stucks when creating prefix
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

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 55055] New: Japanese IME fails to clear composition string when deleting the only remaining character
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

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 55088] New: Program crashes when Common Dialog File open function is called
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

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 55051] New: Build regression in wine 8.10 using clang on aarch64 (error in backend: Invalid register name "x18")
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

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 55027] New: Microsoft Office: IME result string may get doubled when edit is done
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55027 Bug ID: 55027 Summary: Microsoft Office: IME result string may get doubled when edit is done Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: firelzrd(a)gmail.com Distribution: --- Created attachment 74582 --> https://bugs.winehq.org/attachment.cgi?id=74582 Bad and Good cases in Excel 2003 The recent (v8.x) IMM32 progress is so remarkable that CJK users may finally think of replacing Windows for using Microsoft Office. However, in Microsoft Office apps (confirmed in 2003) having done editing IME preedit text by hitting Enter key may actually put the result text doubled (see in the attached video). My analysis showed that when: WM_IME_COMPOSITION which has GCS_RESULTREADSTR & GCS_RESULTSTR flags on is sent to complete the edit, and result text is sent, Only in case the problem occurs, right after that: WM_IME_COMPOSITION which has GCS_COMPSTR & GCS_COMPATTR & GCS_RESULTSTR flags on is sent. This behavior indicates that xic_preedit_done() and xim_set_result_string() which I found in xim.c are called sometimes in a wrong order. A: XICCallback preedit_done is called xic_preedit_done is called B: keyboard.c:X11DRV_KeyEvent xim_set_result_string is called A is supposed to be called first, and then B should follow. in the good case A happens, then B happens. in the bad case B happens, then A happens. So I think this problem occurs because XIC callback and X11DRV_KeyEvent are called asynchronously. I think the solution may be: * In xim_set_result_string(), check if XIC preedit context exists, and if so, ppostpone the sending of WM_IME_COMPOSITION until next xic_preedit_done() is called or * Ignore xic_preedit_done() if xim_set_result_string() was called very recently Let me hear what you guys think. Thank you -- 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