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

[Bug 54720] Spider-Man: Shattered Dimensions - dialogue audio doesn't play

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54720 tinozzo123(a)tutanota.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from tinozzo123(a)tutanota.com --- Retested Wine 8.13 unstable and staging on a fresh prefix, it's solved! (For some reason, though, it isn't solved in Wine-GE...) -- 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.

Aug. 7, 2023

[Bug 55413] ddraw:ddraw1 sometimes fails and crashes on w1064v1507 and w1046v2004

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55413 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |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.

Aug. 7, 2023

[Bug 55413] New: ddraw:ddraw1 sometimes fails and crashes on w1064v1507 and w1046v2004

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55413 Bug ID: 55413 Summary: ddraw:ddraw1 sometimes fails and crashes on w1064v1507 and w1046v2004 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw1 sometimes fails on w1064v1507 and w1046v2004: ddraw1.c:2495: Test failed: Expected message 0x46, but didn't receive it. ddraw1.c:2618: Test failed: Failed to set foreground window. ddraw1.c:2626: Test failed: Failed to set foreground window. ddraw1.c:2652: Test failed: Expected window style 0x14cf0000, got 0x4cf0000. ddraw1.c:2655: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2662: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2671: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2680: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2683: Test failed: Failed to set foreground window. ddraw1.c:2690: Test failed: Expected window style 0x14cf0000, got 0x4cf0000. ddraw1.c:2693: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2706: Test failed: Failed to set foreground window. ddraw1.c:2731: Test failed: Failed to set foreground window. ddraw1.c:2746: Test failed: Failed to set foreground window. ddraw1.c:2755: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2775: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:2778: Test failed: Failed to set foreground window. ddraw1.c:2781: Test failed: Expected window style 0x34cf0000, got 0x14cf0000. ddraw1.c:2784: Test failed: Expected window extended style 0x108, got 0x100. ddraw1.c:3129: Test failed: Failed to set foreground window. ddraw1.c:3130: Test failed: Expected message 0x6, but didn't receive it. ddraw1.c:3135: Test failed: Got unexpected screen size 800x600. ddraw1.c:867: Test failed: Got unexpected wparam 0 for message 0x1c, expected 0x1. ddraw1.c:3141: Test failed: Expected message 0x5, but didn't receive it. ddraw1.c:3144: Test failed: Expected (0,0)-(640,480), got (-32000,-32000)-(-31840,-31972). ddraw1.c:3148: Test failed: Got unexpected screen size 1024x768. ddraw1.c:3161: Test failed: Expected message 0x46, but didn't receive it. [...] ddraw1.c:3609: Test failed: Expected (0,0)-(640,480), got (-8,-8)-(648,448). ddraw1.c:4338: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:4350: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:4362: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:4384: Test failed: Expected WM_ACTIVATEAPP, but did not receive it. ddraw1.c:8051: Test failed: Failed to set foreground window. ddraw1.c:8053: Test failed: Got unexpected hr 0. ddraw1.c:8055: Test failed: Got unexpected hr 0. ddraw1.c:8057: Test failed: Got unexpected hr 0. ddraw1.c:8059: Test failed: Got unexpected hr 0. ddraw1.c:8069: Test failed: Got unexpected hr 0. ddraw1.c:8071: Test failed: Got unexpected hr 0. ddraw1.c:8073: Test failed: Got unexpected hr 0. ddraw1.c:8077: Test failed: Failed to set foreground window. ddraw1.c:8079: Test failed: Got unexpected hr 0. ddraw1.c:8081: Test failed: Got unexpected hr 0. ddraw1.c:8087: Test failed: Got unexpected hr 0. ddraw1.c:8135: Test failed: Failed to set foreground window. ddraw1.c:8147: Test failed: Failed to set foreground window. ddraw1.c:13670: Test failed: WM_KILLFOCUS was not received. ddraw1.c:13706: Test failed: Got unexpected hr 0x887600e1. ddraw1.c:13709: Test failed: Got unexpected hr 0x887600ff. 0a60:ddraw1: unhandled exception c0000005 at 00007FF6FFAE2567 See https://test.winehq.org/data/patterns.html#ddraw:ddraw1 Where 0x46 == WM_WINDOWPOSCHANGING and the test window does not seem to be visible: expected: 0x14cf0000 == WS_VISIBLE | 0x04cf0000 This failure happens irregularly and only on w1064v1507 and w1046v2004 so far: * 2022-12-14 win1507_newtb-w1064v1507-64 * 2022-12-15 win1507_newtb-w1064v1507-64 * 2023-01-31 win1507_newtb-w1064v1507-64 * 2023-02-16 win1507_newtb-w1064v1507-64 * 2023-06-07 win1507_newtb-w1064v1507-64 * 2023-06-09 win1507_newtb-w1064v1507-32 * 2023-07-13 win1507_newtb-w1064v1507-64 * 2023-07-27 win2004_newtb-w10pro64v2004-64 -- 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.

Aug. 7, 2023

[Bug 55029] Wishlist: do reflink on CopyFileW for WINEPREFIX size reduction

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55029 Mingye Wang <arthur200126(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alex_y_xu(a)yahoo.ca --- Comment #4 from Mingye Wang <arthur200126(a)gmail.com> --- Sherml, I don't think so. Ah what the heck, let's just CC Alex Xu and see what he thinks about maybe giving the patch a new life. * * * Typo in comment 2: "detailed" should be "derailed" -- 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.

Aug. 7, 2023

[Bug 55411] Stack overflow when running Battle For Middle Earth 2.22 Launcher

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55411 danielginovker(a)gmail.com <danielginovker(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.

Aug. 7, 2023

[Bug 55411] Stack overflow when running Battle For Middle Earth 2.22 Launcher

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55411 danielginovker(a)gmail.com <danielginovker(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |danielginovker(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.

Aug. 7, 2023

[Bug 55396] advapi32:registry breaks crypt32:oid, crypt32:sip, crypt32:store, msi:msi, msi:source and sti:sti on w8adm

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55396 --- Comment #7 from François Gouget <fgouget(a)codeweavers.com> --- Note: The memory change seems to also have broken msi:package independently from advapi32:registry (see bug 55410). So it is still possible something changed on the MSI side. -- 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.

Aug. 7, 2023

[Bug 55396] advapi32:registry breaks crypt32:oid, crypt32:sip, crypt32:store, msi:msi, msi:source and sti:sti on w8adm

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55396 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|crypt32 |advapi32 Assignee|fgouget(a)codeweavers.com |wine-bugs(a)winehq.org -- 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.

Aug. 7, 2023

[Bug 55396] advapi32:registry breaks crypt32:oid, crypt32:sip, crypt32:store, msi:msi, msi:source and sti:sti on w8adm

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55396 --- Comment #6 from François Gouget <fgouget(a)codeweavers.com> --- Created attachment 74973 --> https://bugs.winehq.org/attachment.cgi?id=74973 Minimal advapi32:registry to break the other tests * Looking at the w8adm test configuration I don't see anything wrong: Windows update is disabled, there is no process that should not be running, etc. * I also restored the VM from backup but the tests fail in the same way even with the old amount of memory (but note the live snapshot is always rebuilt by the TestBot). * I also verified that before the update the tests were running without elevated privileges. The old logs on test.winehq.org have the right set of skips indicating that this was the case. The current logs have the same set of skips too (particularly in advapi32:registry). * So now I'm thinking these tests should have failed all along and we somehow got lucky. Then I hacked advapi32:registry to find which part causes the other tests to fail. This shows that the line below in test_reg_open_key() is sufficient to cause the other tests to crash (see the attached patch). ret = RegCreateKeyExA(HKEY_LOCAL_MACHINE, "Software\\Wine", 0, NULL, 0, KEY_WOW64_32KEY | KEY_ALL_ACCESS, NULL, &hkRoot32, NULL); Also this call is preceded by a check for the presence of IsWow64Process which does not skip: w8adm is 32-bit only but the WoW APIs are present regardless. Maybe the fix is to tweak that check to skip in the non-elevated privileges case? Or maybe testing WoW-stuff on a non-WoW configuration is just wrong even though it does not seem to break things in the w8 (elevated privileges) configuration. -- 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.

Aug. 7, 2023

[Bug 55291] gdi32:dc - print_something() gets a bad signature on fg-deb64-*

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=55291 Piotr Caban <piotr.caban(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |piotr.caban(a)gmail.com Status|NEW |RESOLVED Fixed by SHA1| |3345404cbe5f5945e0fbc4d495d | |b40365a9eda58 Resolution|--- |FIXED --- Comment #1 from Piotr Caban <piotr.caban(a)gmail.com> --- Marking as fixed by 3345404cbe5f5945e0fbc4d495db40365a9eda58. -- 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.

Aug. 7, 2023