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

[Bug 44816] New: Cygwin/ MSYS2 `script -e` exit status forwarding randomly returns zero for non zero child process
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=44816 Bug ID: 44816 Summary: Cygwin/MSYS2 `script -e` exit status forwarding randomly returns zero for non zero child process Product: Wine Version: 3.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, to track https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-Deal… Mentioned here: https://wine-staging.com/news/2015-08-23-release-1.7.50.html --- quote --- Do not allow to deallocate thread stack for current thread (MSYS2, Wine Staging Bug #241) --- quote --- After some archaeology I found the Cygwin mailing list discussion here: https://cygwin.com/ml/cygwin/2015-09/msg00114.html --- quote --- > Ah, ok. What OS does Wine emulate here? Have a look at > https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/cygt… > > The terminate_thread_frees_stack flag is set to false for XP/2003 and to > true for any newer OS. I guess this is a double-free because Wine's > TerminateThread already freed the stack and Cygwin got the info it's > supposedly running under XP/2003, so it tries to workaround the fact > that TerminateThread on these systems didn't free the stack by themselves. > Wine emulates Windows XP here, I double checked Wine source code and I can confirm Wine doesn't free the stack: NtTerminateThread() -> abort_thread() -> terminate_thread() https://github.com/wine-compholio/wine-patched/blob/8b3a785e97a7e28ff58731b… Cygwin reports wincap as wincap_xpsp2 which is also correct here. > we need to know what address ret=61005767 is refering to. addr2line would help. As you point out, ret=61005767 is the call to VirtualFree() inside cygthread::terminate_thread () https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/cygt… After combine the information we have so far, I think the problem is clear now. It's not Cygwin's fault, it's Wine's fault. Wine's WaitForSingleObject() needs to wait long enough after the TerminateThread() call, so the target thread has enough time to finish the system cleanup and return correct exit_code before Cygwin call VirtualFree to free the stack. But in our current implementation Wine's WaitForSingleObject returns too early, it shouldn't return before the system thread cleanup done, as a result there is a race here. We are thinking of a solution in Wine. Thanks again for the great help! --- quote --- $ wine --version wine-3.4 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 9

[Bug 30655] New: GRID2: Low (1 - 3) FPS during race, but not in in-game menus.
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=30655 Bug #: 30655 Summary: GRID2: Low (1 - 3) FPS during race, but not in in-game menus. Product: Wine Version: 1.5.2 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: linards.liepins(a)gmail.com Classification: Unclassified Created attachment 40128 --> http://bugs.winehq.org/attachment.cgi?id=40128 in-game benchmark test #! Game itself installed with latest winetricks. -- 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 25

[Bug 28603] New: Winedbg sometimes receives invalid parameters
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=28603 Bug #: 28603 Summary: Winedbg sometimes receives invalid parameters Product: Wine Version: 1.3.29 Platform: x86 URL: http://www.winehq.org/pipermail/wine-patches/2011-Sept ember/106508.html OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com CC: julliard(a)winehq.org Classification: Unclassified Created attachment 36753 --> http://bugs.winehq.org/attachment.cgi?id=36753 relay,seh,tid,dbghelp,winedbg I sent a patch to eliminate this dialog: http://www.winehq.org/pipermail/wine-patches/2011-September/106508.html but Alexandre said this should never happen. I see it occasionally on various systems, but since I wrote the patch, haven't found a very reliable testcase. I've found a reliable testcase with make test on Alpine Linux (which uses uclibc). It may not be the best testcase, since it's not using glibc (and also use PaX), but AJ asked for a log, so here we go :). relay,seh,tid,dbghelp,winedbg attached the testcase used was oleaut32/tmarshal wine-1.3.29-217-g5432611 -- 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 6

[Bug 54720] New: Spider-Man: Shattered Dimensions - dialogue audio doesn't play
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54720 Bug ID: 54720 Summary: Spider-Man: Shattered Dimensions - dialogue audio doesn't play Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: tinozzo123(a)tutanota.com Distribution: --- Created attachment 74226 --> https://bugs.winehq.org/attachment.cgi?id=74226 Logs taken with a clean 32 bit prefix with 32 bit Wine devel 8.4, WINEDEBUG=+xactengine,+xaudio2,+x3daudio. In Spider-Man: Shattered Dimensions, the audio that is supposed to be played by the characters during in-game dialogues doesn't play. All the other kinds of audio work. A workaround to this is by installing xact with winetricks. -- 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 44546] New: The Settlers II: 10th Anniversary runs very slow when CSMT enabled
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=44546 Bug ID: 44546 Summary: The Settlers II: 10th Anniversary runs very slow when CSMT enabled Product: Wine Version: 3.2 Hardware: x86 URL: https://www.fileplanet.com/165168/160000/fileinfo/The- Settlers-II:-10th-Anniversary-Demo-v9801 OS: Linux Status: NEW Keywords: performance Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- The game is running painfully slow in Wine 3.2. Can be observed while it is playing the opening video, in the menus and during gameplay too. Loading times are also incredibly long when csmt is enabled. Disabling csmt makes the game run smoothly. There is nothing suspicious in the terminal. Can be reproduced with the demo version. I have native d3dcompiler_43 and d3dx9_29 installed. settlers2_demo2_multilang.exe (318M) md5sum: c738916e0f5f4c9b780898f66e50941f Wine 3.2 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 390.25 -- 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 54413] New: ws2_32:sock - DuplicateHandle(socket) sometimes look like a socket in test_WSAGetOverlappedResult() on Windows
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54413 Bug ID: 54413 Summary: ws2_32:sock - DuplicateHandle(socket) sometimes look like a socket in test_WSAGetOverlappedResult() on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ws2_32:sock - DuplicateHandle(socket) sometimes look like a socket in test_WSAGetOverlappedResult() on Windows: sock.c:12512: Test failed: got 1. sock.c:12513: Test failed: got 0. See https://test.winehq.org/data/patterns.html#ws2_32:sock This failure is pretty rare, there are only 4 known instances: * 2022-09-27 on w1064 64 bit (21h2) * 2022-11-15 on w10pro64-hi-u8 64 bit (21h1) * 2023-01-25 on w11pro64 64 bit (21h2) * 2023-01-25 on w1064v2009 64 bit The test creates a socket, treats it as a handle and duplicates it, then checks whether the duplicate handle behaves like a socket which it normally does not, causing WSAGetOverlappedResult() to fail (return 0) and WSAGetLastError() to be set to WSAENOTSOCK. But in these four cases WSAGetOverlappedResult() succeeded which would indicate the duplicate handle looked like a socket? -- 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 55258] New: steam: small window floating on top of all windows even in fullscreen mode
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55258 Bug ID: 55258 Summary: steam: small window floating on top of all windows even in fullscreen mode Product: Wine Version: 8.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: idarktemplar(a)mail.ru Distribution: --- Created attachment 74873 --> https://bugs.winehq.org/attachment.cgi?id=74873 steam_window_bug.png When running steam with new versions of wine, I'm getting a small square window which is always on top of all windows, even when I'm playing fullscreen game. It's usually located around center of screen for me, but during bisecting I also got a few builds when it appeared at top left corner. I've tested it with following wine versions: wine 7.0.2: win7 prefix: good wine 7.0.2: win10 prefix: does not start wine 8.0.1: win7 prefix: good wine 8.0.1: win10 prefix: good wine 8.9: win10 prefix: bad wine 8.12: win10 prefix: bad After that I ran git bisect with following build: mkdir build32 build64 cd build64 ../configure --with-mingw --enable-win64 --prefix=/tmp/wineinstall cd ../build32 ../configure --with-mingw --with-wine64=../build64 --prefix=/tmp/wineinstall cd ../build64 make $JOBS cd ../build32 make $JOBS make $JOBS install cd ../build64 make $JOBS install My results are: 2504a2d7bca47fc77bb523114d7b0b6e60213116 is the first bad commit commit 2504a2d7bca47fc77bb523114d7b0b6e60213116 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Mon Mar 27 11:58:50 2023 +0200 imm32: Keep the IME UI window on the default input context. dlls/imm32/imm.c | 61 ++++++++++++++++++++++++++++++++------------------------ 1 file changed, 35 insertions(+), 26 deletions(-) $ git bisect log # bad: [9ffeb2622d087a6189ca916553529824791010c3] Release 8.9. # good: [d8b2687760f7c07eaf481aba2835b820d3092b3e] Release 8.0.1. git bisect start 'wine-8.9' 'wine-8.0.1' # skip: [6677c044abb711f423fadfb61f2c9a37da6ff686] Release 8.0. git bisect skip 6677c044abb711f423fadfb61f2c9a37da6ff686 # good: [7771a9ae79930d112051cfe18b27dec1e5edd245] widl: Simplify attribute creation with either int or ptr value. git bisect good 7771a9ae79930d112051cfe18b27dec1e5edd245 # bad: [d1c317720ab6a92811c013408844ffd9e581b2a2] mfreadwrite: Fix an address of operator typo. git bisect bad d1c317720ab6a92811c013408844ffd9e581b2a2 # bad: [66bef6db20f72e88a38c4b264e13639015d7817d] msvcrt: Use the sinhf() implementation from the bundled musl library. git bisect bad 66bef6db20f72e88a38c4b264e13639015d7817d # bad: [17fbef91929af9c6ab98e53fb2a54942f0f1a0a5] wmvcore/tests: Don't cast NULL to another pointer type. git bisect bad 17fbef91929af9c6ab98e53fb2a54942f0f1a0a5 # skip: [83f0862b43f7b1b7bd23830b4339894c35febea7] wineps: Handle EMR_SETARCDIRECTION record in spool files. git bisect skip 83f0862b43f7b1b7bd23830b4339894c35febea7 # good: [6a88500af29b82040f0518eb87171ca047fb95aa] hidparse.sys: Include zero-count reports in cap count. git bisect good 6a88500af29b82040f0518eb87171ca047fb95aa # good: [62ef3c5be1d2c5374399984588a9daa75663d030] taskkill: Factor out get_task_pid(). git bisect good 62ef3c5be1d2c5374399984588a9daa75663d030 # bad: [956541c9c823fb6048047893545dcee4c108730e] d3d10/effect: Add support for umin/umax instructions. git bisect bad 956541c9c823fb6048047893545dcee4c108730e # good: [4b04d357739f261457316d55b79ecbcff9c0be84] imm32/tests: Add explicit ImmLoadIME / ImmFreeLayout calls. git bisect good 4b04d357739f261457316d55b79ecbcff9c0be84 # bad: [2504a2d7bca47fc77bb523114d7b0b6e60213116] imm32: Keep the IME UI window on the default input context. git bisect bad 2504a2d7bca47fc77bb523114d7b0b6e60213116 # good: [9117ce4185146a5edd47467d370b3e4dfa588191] imm32/tests: Test ImmProcessKey with the installed IME. git bisect good 9117ce4185146a5edd47467d370b3e4dfa588191 # good: [43e22eaa76a443e3053868df1bd8c5d4130a9fde] imm32/tests: Test IME UI window and IME window presence. git bisect good 43e22eaa76a443e3053868df1bd8c5d4130a9fde # good: [0ddad3564f3260f53e5a50b615f6aa6ba27e032b] imm32: Update existing input contexts on layout change. git bisect good 0ddad3564f3260f53e5a50b615f6aa6ba27e032b # first bad commit: [2504a2d7bca47fc77bb523114d7b0b6e60213116] imm32: Keep the IME UI window on the default input context. OS: Gentoo Linux Amd64 Kernel: 6.1.38-gentoo DE: KDE 5.27.5 glxinfo: OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon RX 7900 XTX (gfx1100, LLVM 16.0.6, DRM 3.49, 6.1.38-gentoo.65) OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.1.3 OpenGL core profile shading language version string: 4.60 -- 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 55291] New: gdi32:dc - print_something() gets a bad signature on fg-deb64-*
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55291 Bug ID: 55291 Summary: gdi32:dc - print_something() gets a bad signature on fg-deb64-* Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- gdi32:dc - print_something() gets a bad signature on fg-deb64-*: dc.c:1501: Test failed: wrong signature: See https://test.winehq.org/data/patterns.html#gdi32:dc This does not depend on bitness, happens systematically and a bisect shows that the failure started with the commit below: commit d5373ef6f92d36971859db0746600188ada22a7d Author: Piotr Caban <piotr(a)codeweavers.com> Date: Sun Jul 9 13:05:42 2023 +0200 wineps: Buffer data sent to printer port. -- 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 55231] New: Warframe: camera/mouse stuck in X-axis
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55231 Bug ID: 55231 Summary: Warframe: camera/mouse stuck in X-axis Product: Wine Version: 8.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pmargeti34(a)gmail.com Distribution: --- Wine 8.12 introduces a regression in Warframe: there seems to be a hard limit to how much camera can be turned on the X-axis. After spinning the camera in the same direction a few times, it gets stuck and it's no longer possible to turn in in that direction until it is first turned in the opposite direction. This happens when Warframe is either in full screen mode or borderless fullscreen mode. Windowed mode isn't affected. Warframe is a free to play game and the installer can be obtained here: https://www.warframe.com/download OS: Archlinux Linux 6.4.3 -- 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 55152] New: Crash in Notepad++ processing a WM_DRAWITEM message
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55152 Bug ID: 55152 Summary: Crash in Notepad++ processing a WM_DRAWITEM message Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: julliard(a)winehq.org Distribution: --- Running the 32-bit Notepad++ 8.5.4 in new wow64 mode crashes on startup when processing a WM_DRAWITEM message. The exception is swallowed by win32u so it still works, but we get a message: 0024:err:seh:KiUserCallbackDispatcher ignoring exception The root cause is that because Notepad++ added a WH_CALLWNDPROC hook, in win32u process_message(), instead of returning to SendMessageW and have it call the winproc, we call it ourselves through KeUserModeCallback. But at that point the message has been converted to 64-bit so we pass a (truncated) 64-bit lparam to the 32-bit winproc. The crash was revealed by a82238fad52761114ab2488d422fad3f70dbb854, which moves the 64-bit stack to high memory. Previously the lparam pointer would fit in 32-bit which avoided the crash, but it would still point to a 64-bit DRAWITEMSTRUCT. -- 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