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

[Bug 54717] dbghelp:dbghelp - SymRefreshModuleList() sometimes returns STATUS_INFO_LENGTH_MISMATCH on Windows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54717 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |0f98972fe2165d5eca52de48d8a | |6130de7e61a30 Keywords| |regression, source, | |testcase -- 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.

March 22, 2023

[Bug 54717] New: dbghelp:dbghelp - SymRefreshModuleList() sometimes returns STATUS_INFO_LENGTH_MISMATCH on Windows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54717 Bug ID: 54717 Summary: dbghelp:dbghelp - SymRefreshModuleList() sometimes returns STATUS_INFO_LENGTH_MISMATCH on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dbghelp:dbghelp - SymRefreshModuleList() sometimes returns STATUS_INFO_LENGTH_MISMATCH on Windows: dbghelp.c:738: Test failed: SymRefreshModuleList failed: 3221225476 See https://test.winehq.org/data/patterns.html#dbghelp:dbghelp Where 3221225476 == 0xc0000004 == STATUS_INFO_LENGTH_MISMATCH So far the failure has only happened on the w10pro64 VM, and only in the non-English locales. However it's rare enough that it's too early to draw conclusions. This failure first happened on 2023-03-8 which corresponds to the day this test was added: commit 0f98972fe2165d5eca52de48d8a6130de7e61a30 Author: Eric Pouech <eric.pouech(a)gmail.com> AuthorDate: Wed Mar 8 11:43:22 2023 +0100 dbghelp/tests: Add tests for SymRefreshModuleList() on non-live target. Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> -- 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.

March 22, 2023

[Bug 53456] kernel32:debugger - load_blackbox() sometimes fails for crash_and_debug() on Windows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53456 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW --- Comment #3 from François Gouget <fgouget(a)codeweavers.com> --- I believe I identified a new variant. First the original issue seems to always happen in the dbg,attach,process,event,detach test. So a more complete trace is: debugger.c:610: running dbg,attach,process,event,detach... debugger.c:621: waiting for child exit... debugger.c:198: child: crashing... debugger.c:659: waiting for the debugger... debugger.c:155: Test failed: unable to open 'C:\Users\winetest\AppData\Local\Temp\wt681E.tmp' debugger.c:155: Test failed: failed to open: C:\Users\winetest\AppData\Local\Temp\wt681E.tmp debugger.c:676: Test failed: the child and debugged pids don't match: 8052 != 8236 The new variant happens in the same test but corresponds to a case where the blackbox file is... almost empty? debugger.c:631: running dbg,attach,process,event,detach... debugger.c:642: waiting for child exit... debugger.c:205: child: crashing... debugger.c:680: waiting for the debugger... debugger.c:168: Test failed: wrong size for 'C:\Users\winetest\AppData\Local\Temp\wt5B67.tmp': read=0 debugger.c:173: debugger traces:>>> <<< Done. debugger.c:697: Test failed: the child and debugged pids don't match: 3388 != 3508 So the first ReadFile() call in load_blackbox() returns 0 but the second one returns a single byte (0x06) for the debugger traces. This corresponds to the expected blackbox.argc value. Race condition? Also the pid mismatch failure message looks like the blackbox file contained a 8236 pid. However when load_blackbox() fails, in either case, the content of the blackbox structure is uninitialized. Maybe it would be clearer to do a memset(0). There are 3 known instances of this variant so far: * 2023-02-21 on w1064v1507 32-bit * 2023-03-13 on w10pro64-hi 64-bit * 2023-03-21 on w10pro64-pt-BR 64-bit -- 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.

March 22, 2023

[Bug 54707] adsldp:ldap - test_DirectorySearch() fails on Windows and Linux

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54707 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |42fbc50b66d6d0b7e48840e9d30 | |761ef98df8b3d --- Comment #1 from François Gouget <fgouget(a)codeweavers.com> --- This is fixed: commit 42fbc50b66d6d0b7e48840e9d30761ef98df8b3d Author: Hans Leidekker <hans(a)codeweavers.com> AuthorDate: Sun Mar 19 21:32:27 2023 +0100 adsldp/tests: Fix test failures. The server is back online now and apparently its contents changed, causing test failures. -- 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.

March 22, 2023

[Bug 54594] dinput:device8 - test_dik_codes() sometimes gets timeouts on the GitLab CI

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54594 --- Comment #2 from Rémi Bernon <rbernon(a)codeweavers.com> --- I can finally reproduce it locally, and I believe that it is a race condition in fvwm. The WM sends WM_TAKE_FOCUS messages to us, with some timestamp to use for the reply, but quickly after calls XSetInputFocus on its own desktop window with CurrentTime. Depending on how quickly we reply to the WM_TAKE_FOCUS message, this ends up with fvwm stealing our focus and we get a FocusOut even right after the FocusIn event. We then set focus to desktop, as we should, and wineserver stops sending input to the dinput messages window. -- 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.

March 22, 2023

[Bug 54711] imm32:imm32 - test_ImmGetProperty() fails in the Korean locale on Windows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54711 Rémi Bernon <rbernon(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |067b81fcfa82cd442b0c2542ff4 | |e902fe19869a2 --- Comment #1 from Rémi Bernon <rbernon(a)codeweavers.com> --- Fixed with 067b81fcfa82cd442b0c2542ff4e902fe19869a2 -- 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.

March 22, 2023

[Bug 54710] imm32:imm32 - test_ImmEscape() fails in the Korean locale on Windows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54710 Rémi Bernon <rbernon(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |rbernon(a)codeweavers.com Fixed by SHA1| |9ab5fb591fcfbe53bab16754ada | |cc2adf0d27b24 Status|NEW |RESOLVED --- Comment #1 from Rémi Bernon <rbernon(a)codeweavers.com> --- Fixed with 9ab5fb591fcfbe53bab16754adacc2adf0d27b24 -- 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.

March 22, 2023

[Bug 54713] dinput:device8 - test_mouse_keyboard() fails on some Window 7 locales

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54713 --- Comment #1 from Rémi Bernon <rbernon(a)codeweavers.com> --- I whacked the mole on W7 with 01e4c4335a981f420218b5fb68fb405f289e7b67, but not it seems to pop up on linux_newtb-debian11-win32-ar-MA and linux_newtb-debian11-win32-zh-CN... -- 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.

March 22, 2023

[Bug 54716] Hard Time (2007): incorrect text rendering caused by font anti-aliasing

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54716 Liam Stevens <liamstevens2287(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux -- 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.

March 22, 2023

[Bug 54716] New: Hard Time (2007): incorrect text rendering caused by font anti-aliasing

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54716 Bug ID: 54716 Summary: Hard Time (2007): incorrect text rendering caused by font anti-aliasing Product: Wine Version: 4.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: liamstevens2287(a)gmail.com Distribution: --- Created attachment 74224 --> https://bugs.winehq.org/attachment.cgi?id=74224 A screenshot of 2007's 'Hard Time' showing incorrect font rendering on the left, with the intended appearance on the right. Distros tested: Arch Linux, EndeavourOS, SteamOS Versions tested: Wine 4.21, 7.2, 8.3, 8.4, and all versions of Valve Proton 2007 indie game 'Hard Time' incorrectly displays white outlines around all text, caused by font anti-aliasing being forced. On Windows, the game correctly runs with no AA without tweaking required by the user. Disabling font anti-aliasing at the Xorg level or by using your DE's options works around this, as there is no way to disable font AA in Wine itself (that I can tell). The game is free, and the official download is located at http://www.mdickie.com/downloads.htm (direct link at http://www.mdickie.com/downloads/new/hardtime_setup.exe) Attached is an image of two screenshots with font anti-aliasing enabled on the left, and disabled on the right to show the intended appearance. As this is my first Wine bug, please do tell me if there is any other information which is needed. Many 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.

March 22, 2023