wine-bugs November 2022

wine-bugs@winehq.org

1 participants
3338 discussions

[Bug 53977] New: amstream:amstream qedit:mediadet mf:transform mfmediaengine:mfmediaengine quartz:filtergraph winmm:mci wmp:media wmvcore:wmvcore mf:mf mfplay:mfplay qasf:asfreader broken on Debian Testing
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53977 Bug ID: 53977 Summary: amstream:amstream qedit:mediadet mf:transform mfmediaengine:mfmediaengine quartz:filtergraph winmm:mci wmp:media wmvcore:wmvcore mf:mf mfplay:mfplay qasf:asfreader broken on Debian Testing Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- amstream:amstream qedit:mediadet mf:transform mfmediaengine:mfmediaengine quartz:filtergraph winmm:mci wmp:media wmvcore:wmvcore mf:mf mfplay:mfplay qasf:asfreader all have failures on Debian Testing. The exact failures are not really important, see the corresponding entries on the failure patterns page if more details are needed: https://test.winehq.org/data/patterns.html What's important is that the detection of gst/gst.h now fails on Debian Testing, resulting in Wine being compiled without GStreamer support which is what broke all the tests above: configure:17099: gstreamer-1.0 gstreamer-video-1.0 gstreamer-audio-1.0 cflags: configure:17100: gstreamer-1.0 gstreamer-video-1.0 gstreamer-audio-1.0 libs: configure:17103: checking for gst/gst.h configure:17103: gcc -m32 -c -g -O2 conftest.c >&5 conftest.c:174:10: fatal error: gst/gst.h: No such file or directory 174 | #include <gst/gst.h> | ^~~~~~~~~~~ And this all started with the commit below, which means this issue is related to bug 53953 but for Debian Testing instead of Fedora: commit c7a97b5d5d56ef00a0061b75412c6e0e489fdc99 (HEAD, refs/bisect/bad) Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Thu Nov 17 19:32:39 2022 -0600 configure: Override PKG_CONFIG_LIBDIR instead of PKG_CONFIG_PATH for 32-bit builds on 64-bit hosts. This allows 32-bit packages to be found when the user has specified PKG_CONFIG_PATH for some other reason. This also mirrors the way e.g. i686-linux-gnu-pkg-config is implemented on Debian, and possibly other distributions as well. This also prevents 64-bit .pc files from being found. This was originally intended as a benefit [1], but can contribute to misdetection of headers which are not actually multiarch (e.g. GStreamer, although at the time that [1] was written that was a preëxisting problem). In general a distribution which provides .pc files for one architecture should be expected to provide them for any architecture that it actually provides libraries for; even if that was not true of Debian in 2017, it is now. I moreover assert it is better to fail to find a present library than to incorrectly find the wrong one. Note that we can't easily use i686-linux-gnu-pkg-config, as would otherwise be preferable, for reasons also described in [1]. [1] https://www.winehq.org/pipermail/wine-devel/2017-June/118002.html -- 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 53744] New: WM_SETTEXT between ANSI programs treating LPARAM as Unicode causing name corruption
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53744 Bug ID: 53744 Summary: WM_SETTEXT between ANSI programs treating LPARAM as Unicode causing name corruption Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: dark(a)darkok.xyz Distribution: --- When sending a WM_SETTEXT to and from a program expecting ANSI strings, it seems to be interpreting the string as Unicode, causing the window title to become corrupted. Sending a wide string over then makes it work on Wine, but not Windows. The issue was introduced in Wine 7.6, and still exists in the latest versions. -- 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 52564] New: dxgi:dxgi times out in test_find_closest_matching_mode() on cw-gtx560
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=52564 Bug ID: 52564 Summary: dxgi:dxgi times out in test_find_closest_matching_mode() on cw-gtx560 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- When run in Wine, dxgi:dxgi times out in test_find_closest_matching_mode() on cw-gtx560: $ WINETEST_NO_MT_D3D=1 WINETEST_TIME=1 ./wine dlls/dxgi/tests/dxgi_test.exe dxgi [...] dxgi.c:1582:1.778 mode_count=130 dxgi.c:1585:1.778 i=0 dxgi.c:1585:2.452 i=1 dxgi.c:1585:3.123 i=2 dxgi.c:1585:3.867 i=3 dxgi.c:1585:4.806 i=4 dxgi.c:1585:5.929 i=5 dxgi.c:1585:7.061 i=6 dxgi.c:1585:8.187 i=7 dxgi.c:1585:9.332 i=8 dxgi.c:1585:10.542 i=9 [...] dxgi.c:1656:139.600 [...] 0020:dxgi:188.618 12836 tests executed (203 marked as todo, 2 failures), 35 skipped. https://test.winehq.org/data/patterns.html#dxgi:dxgi The problem is that it slows down after the first few modes, taking 1060 ms on average. And there are 130 modes to test so the test hits the 120 second limit. This issue started with the commit below. commit 1f2c3e8538b088f678a588121fc0bf7811336efc Author: Jacek Caban <jacek(a)codeweavers.com> Date: Wed Dec 1 16:02:43 2021 +0100 win32u: Move NtUserEnumDisplaySettings implementation from user32. Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Before that commit test_find_closest_matching_mode() was much faster. dxgi.c:1582:1.558 mode_count=130 dxgi.c:1585:1.558 i=0 dxgi.c:1585:1.751 i=1 dxgi.c:1585:1.960 i=2 dxgi.c:1585:2.168 i=3 dxgi.c:1585:2.361 i=4 dxgi.c:1585:2.570 i=5 dxgi.c:1585:2.763 i=6 dxgi.c:1585:2.939 i=7 dxgi.c:1585:3.132 i=8 dxgi.c:1585:3.309 i=9 [...] dxgi.c:1656:25.519 [...] 0020:dxgi:63.668 12835 tests executed (203 marked as todo, 2 failures), 35 skipped. (184 ms on average) Note: cw-rx460 does not have this issue because it has fewer modes to test (20), and testing each mode is much faster too (28 ms on average). -- 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 50315] New: Silent Hill 2 failed to install -installshield extraction error
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=50315 Bug ID: 50315 Summary: Silent Hill 2 failed to install -installshield extraction error Product: Wine Version: 6.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: legluondunet(a)gmail.com Distribution: --- Created attachment 68897 --> https://bugs.winehq.org/attachment.cgi?id=68897 screenshot installshield error message Hello, with last wine version 6, Silent Hill 2 failed to install with an installshield extraction error (cf screenshot joined). This bug is new, I can not reproduce it with Wine 5.x Nothing interesting in terminal log, only that lines: 010c:fixme:file:NtLockFile I/O completion on lock not implemented yet Initial process has exited (return code: 0) 010c:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d -- 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 50043] New: Kholat from GOG does not launch anymore
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=50043 Bug ID: 50043 Summary: Kholat from GOG does not launch anymore Product: Wine Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: titan.costa(a)gmail.com Distribution: --- Created attachment 68493 --> https://bugs.winehq.org/attachment.cgi?id=68493 Message box I get the attached message box instead. This is a regression but I can't bisect as I the following errors with older wine versions: wine: could not find __wine_start_process in kernel32.dll, status c000007a 0024:err:environ:run_wineboot failed to start wineboot c000007a -- 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 23

[Bug 54014] New: advapi32:security sometimes exits prematurely in Wine
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54014 Bug ID: 54014 Summary: advapi32:security sometimes exits prematurely 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: --- advapi32:security sometimes exits prematurely in Wine: security.c:5550: Test marked todo: expected execute access 0x120000, got 0xdeadbeef advapi32:security:03a8 done (0) in 0s 6852B What's missing here is the "tests executed..." summary line which typically indicates some underlying library called "exit()". This is usually accompanied with a warning message complaining about something being wrong but there is no trace of such a message in the task log. There are some strange aspects to this: * There is no record of it ever happening in the nightly WineTest runs. * But it impacted 9 merge requests so far: 2022-11-28 MR!1575 2022-11-29 MR!1595 MR!1583 MR!1594 2022-11-25 MR!1537 2022-11-16 MR!1379 2022-11-14 MR!1363 MR!1356 2022-11-13 MR!1315 When it happens the report shows 4 instances of the 5550 todo. Comparing that to a successful run indicates the early exit happened between the end of test_kernel_objects_security() and the start of test_CreateWellKnownSid(). Maybe a piece of good news: advapi32:security crashes with WINEDEBUG=heap. However that crash happens in test_CreateDirectoryA() instead of the expected place. So it may be an unrelated issue. -- 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 53571] New: PhotoshopCS2 Installer custom action page fault
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53571 Bug ID: 53571 Summary: PhotoshopCS2 Installer custom action page fault Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: winebugs(a)copysoft.org Distribution: --- While attempting to bisect something else on the Photoshop CS2 installer I've noticed that this recent commit: commit 0d0f2067f89545539ab3ae0ccd802239a2dce98e Author: Jacek Caban <jacek(a)codeweavers.com> Date: Sun Aug 14 23:24:04 2022 +0200 user32: Pass window name as UNICODE_STRING to NtUserCreateWindowEx. Breaks the installer and makes it crash when selecting the file types to be associated with Photoshop. 02dc:err:msi:__wine_msi_call_dll_function Custom action (L"C:\\users\\username\\Temp\\msic328.tmp":"SelectFileAssoc") caused a page fault: 0xc0000005 -- 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 40250] New: Stunt GP too fast timer for stunts, waterfall/screen animation and starting screens
by wine-bugs＠winehq.org 20 Dec '22

20 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=40250 Bug ID: 40250 Summary: Stunt GP too fast timer for stunts, waterfall/screen animation and starting screens Product: Wine Version: 1.9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 10mkudela(a)gmail.com Distribution: --- In the game time frame required to press Shift key to make stunt is much smaller then in Windows. Also waterfall animation and loading screens are much faster then in Windows. Everything else is at the same speed. One additional animation is faster as well: speed of the text on screen in Germany location is faster as well, but it's speed is changing from what I have noticed. There is probably a timer somewhere that is ticking faster then it should be, and that is used by all those elements. This bug was tested on 1.9.4 version of Wine, but it is also present on older versions. -- 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 53716] New: Warlords 3: Darklords Rising: opening dialog window has messed up colors
by WineHQ Bugzilla 20 Dec '22

20 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53716 Bug ID: 53716 Summary: Warlords 3: Darklords Rising: opening dialog window has messed up colors Product: Wine Version: 7.14 Hardware: x86-64 URL: https://www.fileplanet.com/archive/p-27637/Warlords-II I-Darklords-Rising-Demo OS: Linux Status: NEW Keywords: download, regression Severity: minor Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: 47dd8a6a9b1193ec1656cdf04117b94a3cf07025 Distribution: --- Created attachment 73147 --> https://bugs.winehq.org/attachment.cgi?id=73147 Before -> after image This was tested with GOG.com version of the game but can also be reproduced with the original demo version. When you start the game the opening dialog (where you select game mode/screen resolution) has strange colors. The demo uses a 16-bit installer which is currently affected by bug #53646. Winver needs to be Win95/98. This is a regression from Wine-7.14, caused by commit 47dd8a6a9b1193ec1656cdf04117b94a3cf07025 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Sun Jul 10 16:15:10 2022 +0200 win32u: Use syscall interface for more user painting functions. Nothing obvious is visible in the terminal output. Darkdemo.zip (20M) md5sum: 30f5908552d720e8b5361e0656772da8 wine-7.17-224-g52a83ffe4ef -- 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 1

[Bug 53256] New: user32:win - test_window_from_point() and test_mouse_input() sometimes fail on Windows 10 2009+
by WineHQ Bugzilla 20 Dec '22

20 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53256 Bug ID: 53256 Summary: user32:win - test_window_from_point() and test_mouse_input() sometimes fail on Windows 10 2009+ 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:win - test_window_from_point() and test_mouse_input() sometimes fail on Windows 10 2009+: win.c:10238: Test failed: button under static window didn't get WM_LBUTTONUP 02fc:win: 10 tests executed (0 marked as todo, 1 failure), 0 skipped. ... win.c:4549: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0204 win.c:4554: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0205 win.c:4559: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0206 win.c:4564: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0205 win.c:4580: Test failed: hwnd 00000000007902D6/00000000007902D6 message 0204 win.c:4584: Test failed: hwnd 00000000007902D6/00000000007902D6 message 0205 win.c:4593: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0204 win.c:4596: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0205 win.c:4629: Test failed: hwnd 00000000005C0340/00000000005C0340 message 00a4 win.c:4635: Test failed: hwnd 00000000005C0340/00000000005C0340 message 00a5 win.c:4642: Test failed: hwnd 00000000005C0340/00000000005C0340 message 0206 win.c:4644: Test failed: wparam 2 win.c:4655: Test failed: hwnd 00000000005C0340/00000000005C0340 message 0205 https://test.winehq.org/data/patterns.html#user32:win Where: * 204 == WM_RBUTTONDOWN * 205 == WM_RBUTTONUP * 206 == WM_RBUTTONDBLCLK Although they seem unrelated, the test_window_from_point() failure and the set of 13 test_mouse_input() failures always happen together which means they probably have a common cause. Also these failures are usually rare but can be almost systematic at times, for instance from 2022-04-25 to 2022-05-30 on w1064 32-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.

1 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs November 2022