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

[Bug 54122] New: Call of Juarez - Bound in Blood in-menu videos don't work
by WineHQ Bugzilla 16 Sep '23

16 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54122 Bug ID: 54122 Summary: Call of Juarez - Bound in Blood in-menu videos don't work Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: VladimirVSC(a)yandex.ru Distribution: --- Created attachment 73655 --> https://bugs.winehq.org/attachment.cgi?id=73655 The output of missing videos The video-animated background into the main menu doesn't work. The same for 7.0 and 8.0-rc1. The output included. -- 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 13

[Bug 54031] New: user32:msg - test_SendMessage_other_thread() broken by WM_WINDOWPOSCHANGING on Windows dual-monitor configs
by WineHQ Bugzilla 16 Sep '23

16 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54031 Bug ID: 54031 Summary: user32:msg - test_SendMessage_other_thread() broken by WM_WINDOWPOSCHANGING on Windows dual-monitor configs 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:msg - test_SendMessage_other_thread() sometimes gets an unexpected WM_WINDOWPOSCHANGING message: msg.c:19053: Test failed: wrong status 00480048 msg.c:19091: Test failed: SendMessage from other thread 5: 0: the msg sequence is not complete: expected 0000 - actual 0046 msg.c:19091: Failed sequence SendMessage from other thread 5: msg.c:19091: 0: expected: nothing - actual: MsgCheckProc: 006F025C WM_WINDOWPOSCHANGING wp 00000000 lp 0022fc40 after 00000000 x 100 y 100 cx 200 cy 200 flags SWP_NOACTIVATE|SWP_NOZORDER (flags 19) msg.c:19091: 1: expected: nothing - actual: MsgCheckProc: 006F025C 0024 wp 00000000 lp 0022f700 (flags 39) msg.c:19059: Failed sequence SendMessage from other thread 1: msg.c:19059: 0: expected: msg 0402 - actual: MsgCheckProc: 007102CA 0402 wp 00000000 lp 00000000 (flags 19) msg.c:19059: 1: expected: msg 0400 - actual: MsgCheckProc: 007102CA 0400 wp 00000000 lp 00000000 (flags 19) msg.c:19079: Failed sequence SendMessage from other thread 3: msg.c:19079: 0: expected: msg 0403 - actual: MsgCheckProc: 007102CA 0403 wp 00000000 lp 00000000 (flags 19) msg.c:19079: 1: expected: msg 0401 - actual: MsgCheckProc: 007102CA 0401 wp 00000000 lp 00000000 (flags 19) [53435] msg.c:19087: Test failed: wrong status 00400040 msg.c:19091: Failed sequence SendMessage from other thread 5: msg.c:18487: Failed sequence SetFocus on a desktop window: msg.c:18497: Failed sequence SetFocus on another thread window: msg.c:18517: Failed sequence SetActiveWindow on a desktop window: msg.c:18527: Failed sequence SetActiveWindow on another thread window: msg.c:18592: Failed sequence SetFocus on a child window: msg.c:18592: 0: expected: hook 0009 - actual: CBT: hook 9 (HCBT_SETFOCUS) wp 005e0252 lp 002f0278 msg.c:12896: QS_RAWINPUT not supported on this platform msg.c:12921: Test failed: wrong qstatus 00000000 See https://test.winehq.org/data/patterns.html#user32:msg This seems to only happen on dual-monitor configurations, most frequently on w1064-2qxl but also regularly on w7u-2qxl. -- 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 52571] New: batch token parsing regression
by WineHQ Bugzilla 16 Sep '23

16 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=52571 Bug ID: 52571 Summary: batch token parsing regression Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: dragonwarriorxtreme(a)gmail.com Distribution: --- This is easily demonstrated with vcvars script batch files in Visual Studio 2015, on amd64. >) >) >) >) >) >Can't recognize 'x86' as an internal or external command, or batch script. >Can't recognize '\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\x64\;C:\windows\system32;C:\win dows;C:\windows\system32\wbem;C:\windows\system32\WindowsPowershell\v1.0' as an internal or external command, or batch script. >Can't recognize 'x86' as an internal or external command, or batch script. >Can't recognize '\Windows Kits\NETFXSDK\4.6.1\include\um;' as an internal or external command, or bat ch script. >Can't recognize 'x86' as an internal or external command, or batch script. >Can't recognize '\Windows Kits\NETFXSDK\4.6.1\lib\um\x86;' as an internal or external command, or bat ch script. >Can't recognize 'x86' as an internal or external command, or batch script. >Can't recognize '\Microsoft Visual Studio 14.0\Team Tools\Performance Tools\x64;C:\Program Files ' as an internal or external command, or batch script. >Can't recognize 'x86' as an internal or external command, or batch script. ... etc ... 1. Install Visual Studio 2015 (latest Wine-git works around ncrypt limitations) or the v140/v141 build tools using 2017 (already works). What I did personally (was attempting to compile x86 programs on an x64 install before I hit this bug): 2. cd C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64_x86 3. wine cmd /K vcvarsamd64_x86.bat -- 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 55031] New: experimental wow64 mode: crashes in some 3d graphics code
by WineHQ Bugzilla 16 Sep '23

16 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55031 Bug ID: 55031 Summary: experimental wow64 mode: crashes in some 3d graphics code Product: Wine Version: 8.10 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 74591 --> https://bugs.winehq.org/attachment.cgi?id=74591 wine.crash.log When I'm trying to run Spellforce 2 with experimental wow64 wine mode, it crashes. When I'm running it using normal multilib setup, everything runs fine, at least until main menu, didn't check again further. Same happens when I'm trying to run Torchlight 2 from Steam. Demo available on: https://store.steampowered.com/app/200710/Torchlight_II/ Crashing wine build options: ./configure --with-mingw --enable-archs='i386,x86_64' --prefix=/tmp/wineinstall Suspicious log lines just before crash: 0114:fixme:opengl:wow64_map_buffer GL_MAP_PERSISTENT_BIT not supported! wine: Unhandled page fault on write access to 5BFFF000 at address 6AB23144 (thread 0114), starting debugger... OS: Gentoo Linux amd64 (64bit) Graphics: X11 Videocard information: OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro K1000M/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.182.03 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile -- 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 54331] New: Game "Antecrypt": Black screen after launch
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54331 Bug ID: 54331 Summary: Game "Antecrypt": Black screen after launch Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stabilergriller(a)gmail.com Distribution: --- Created attachment 73894 --> https://bugs.winehq.org/attachment.cgi?id=73894 Output when running "wine beam.exe" This shooting game from https://punkcake.itch.io/antecrypt just opens up a window which is completely black. I confirm that this game runs on Windows 10. My set up: OS: Arch 64-Bit GPU: Intel HD Graphics 610 Mesa: 22.3.3 Kernel version: 6.1.5 -- 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 42809] New: GPS Track Editor: arrows not shown
by wine-bugs＠winehq.org 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=42809 Bug ID: 42809 Summary: GPS Track Editor: arrows not shown Product: Wine Version: 1.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joao.eiras(a)gmail.com Distribution: --- Created attachment 57847 --> https://bugs.winehq.org/attachment.cgi?id=57847 Example GPX file 1. Please download and install "GPS Track Editor" from http://www.gpstrackeditor.com/download (7.6 MB isntaller) 2. Open the program 3. Open a GPX file (use the attached one, over the brooklyn bridge) 4. Notice how do don't see anything over the bridge but if you hover with the mouse you'll see some dots appearing. The dots also appear if you click the entries in the table on the right side. See attached screenshot. 5. Compare how it should look like on windows (another attached screenshot). -- 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 18

[Bug 51561] New: Wine's built-in gdiplus.dll lags in Paint.NET compared to native (Win 7) gdiplus.dll
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=51561 Bug ID: 51561 Summary: Wine's built-in gdiplus.dll lags in Paint.NET compared to native (Win 7) gdiplus.dll Product: Wine Version: 6.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: kle(a)bluewin.ch Distribution: --- After intensive testing I can confirm that the built-in gdiplus.dll "lags" in Paint.NET 3.5.11 and Wine 6.13 / 6.14. When the native gdiplus.dll from Windows 7 is used (through winetricks) the performance is clearly better, no lag is present. Unfortunately the native gdiplus.dll works not stable, Paint.NET 3.5.11 crashes reproducible after some time. So this is therefore not an usable alternative. Maybe this bug report here is related to bug 24653: https://bugs.winehq.org/show_bug.cgi?id=24653 -- 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 54945] New: ntdll:exception - test_virtual_unwind() fails on Windows 11
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54945 Bug ID: 54945 Summary: ntdll:exception - test_virtual_unwind() fails on Windows 11 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 ntdll:exception - test_virtual_unwind() fails on Windows 11: exception.c:2132: Test failed: 0/8: wrong frame 000000000076F598/000000000076F480 exception.c:2132: Test failed: 0/9: wrong frame 000000000076F478/000000000076F480 exception.c:2132: Test failed: 0/10: wrong frame 000000000076F470/000000000076F480 There are also a lot of possibly related traces. See https://test.winehq.org/data/patterns.html#ntdll:exception The addresses changes sometimes, thus causing false positives. These failures above are also not systematic and only happen in the 64-bit tests. They also seem to be unrelated to the ntdll:exception crashes (see bug 54944). -- 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 54683] New: shlwapi:ordinal - test_SHFormatDateTimeA() fails due to daylight saving time on Windows
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54683 Bug ID: 54683 Summary: shlwapi:ordinal - test_SHFormatDateTimeA() fails due to daylight saving time on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: shlwapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com shlwapi:ordinal - test_SHFormatDateTimeA() fails due to daylight saving time on Windows: ordinal.c:1734: Test failed: expected (12:00 PM), got (11:00 AM) ordinal.c:1741: Test failed: expected (12:00:00 PM), got (11:00:00 AM) ordinal.c:1749: Test failed: expected (12:00:00 PM), got (11:00:00 AM) ordinal.c:1779: Test failed: expected (12:00 PM), got (11:00 AM) for time part ordinal.c:1793: Test failed: expected (12:00:00 PM), got (11:00:00 AM) for time part ordinal.c:1811: Test failed: expected (2/14/2023 12:00 PM), got (2/14/2023 11:00 AM) ordinal.c:1822: Test failed: expected (2/14/2023 12:00:00 PM), got (2/14/2023 11:00:00 AM) See https://test.winehq.org/data/patterns.html#shlwapi:ordinal The AM/PM translations can change the failure messages slightly but it's always the same issue, on all Windows versions... except w10pro64v2004! This set of failures started on 2023-03-13 which, together with the 1 hour offset, clearly corresponds to the switch from CST to CDT (there was no WineTest run on Sunday). -- 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 53435] New: user32:msg - test_SendMessage_other_thread() sometimes fails on Windows 7
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=53435 Bug ID: 53435 Summary: user32:msg - test_SendMessage_other_thread() sometimes fails on Windows 7 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:msg - test_SendMessage_other_thread() sometimes fails on Windows 7: msg.c:18505: Test failed: wrong status 00400040 https://test.winehq.org/data/patterns.html#user32:msg Where 0x00400040 that there are still QS_SENDMESSAGE messages in the queue and that one was added since the last call. This is similar to the Windows 10-only bug 53434 but the status is different and this failure only happens on Windows 7. -- 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