wine-bugs October 2023

wine-bugs@winehq.org

1 participants
2963 discussions

[Bug 55652] New: A FindResourceW() call prevents windows.applicationmodel:model from running on Windows 8
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55652 Bug ID: 55652 Summary: A FindResourceW() call prevents windows.applicationmodel:model from running on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com A FindResourceW() call prevents windows.applicationmodel:model from running on Windows 8: model.c:0: Tests skipped: missing entry point (details below) | windows.applicationmodel_test.exe - Entry Point Not Found | The procedure entry point FindResourceW could not be located in the dynamic link library C:\Users\winetest\Documents\windows.applicationmodel_test.exe. See https://test.winehq.org/data/patterns.html#windows.applicationmodel:model This is caused by this commit: commit 8609fef5c822e32998725bad58582764d289c194 Author: Rémi Bernon <rbernon(a)codeweavers.com> AuthorDate: Wed Aug 23 11:21:33 2023 +0200 windows.applicationmodel/tests: Test IPackageManager_RegisterPackageAsync. -- 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

[Bug 55236] New: scrrun:dictionary - test_hash_value() gets bad hashes on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55236 Bug ID: 55236 Summary: scrrun:dictionary - test_hash_value() gets bad hashes on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: scrrun Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com scrrun:dictionary - test_hash_value() gets bad hashes on Windows: dictionary.c:676: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:686: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:695: Test failed: got hash 0x2db, expected 0x2da dictionary.c:721: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:732: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:742: Test failed: got hash 0x2db, expected 0x2da See https://test.winehq.org/data/patterns.html#scrrun:dictionary Note that the hash values change with every run causing false positives. -- 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 54791] New: explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54791 Bug ID: 54791 Summary: explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7. This can either be a single event but it can also happen multiple times for multiple events: nstc.c:2265: Test failed: Got event 4, count 1 or nstc.c:1906: Test failed: Got event 7, count 0 nstc.c:1908: Test failed: Got event 4, count 0 nstc.c:1912: Test failed: Got event 4, count 1 nstc.c:1912: Test failed: Got event 7, count 1 nstc.c:1912: Test failed: Got event 12, count 8 See https://test.winehq.org/data/patterns.html#explorerframe:nstc This first happened on 2022-12-07 and has been happening roughly once every three week since. So it's probably caused by a commit in the fall of 2022. -- 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 54441] New: windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54441 Bug ID: 54441 Summary: windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10: speech.c:1775: Test failed: recog_state was 0. See https://test.winehq.org/data/patterns.html#windows.media.speech:speech This failure started on 2023-01-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.

1 9

[Bug 54156] New: comctl32:edit & user32:edit - test_paste() sometimes gets an empty string on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54156 Bug ID: 54156 Summary: comctl32:edit & user32:edit - test_paste() sometimes gets an empty string on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:edit - test_paste() sometimes gets an empty string on Windows edit.c:3238: Test failed: got 0 See https://test.winehq.org/data/patterns.html#comctl32:edit This happens on Windows 10 1809 to 21H2 a bit less than 3 times per month. Where 0 is the length of the string in the field we pasted to. So that field is empty instead of having received the string we pasted. We can also get this failure in user32:edit (2022-11-15 w10pro64v1809): edit.c:3211: Test failed: got 0 See https://test.winehq.org/data/patterns.html#user32:edit But the case above is for the single-line to single-line case and there is also the same issue happening in the multi-line to multi-line case (2022-10-25 w11pro64-amd): edit.c:3240: Test failed: got 0 So it's a pretty general, if rare (only 4 known instances in 6 months), problem. Note that while one could expect this to be caused by yet another OpenClipboard() failure, like in bug 53276, there is no failure message indicating this to be the case. -- 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 53276] New: user32:edit - test_paste() sometimes fails to access the clipboard on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=53276 Bug ID: 53276 Summary: user32:edit - test_paste() sometimes fails to access the clipboard on Windows 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:edit - test_paste() sometimes fails to access the clipboard on Windows: edit.c:3222: Test failed: expected 1, got 0 le=5 edit.c:3224: Test failed: expected 1, got 0 edit.c:3226: Test failed: expected 00000000008500A8, got 0000000000000000 edit.c:3228: Test failed: expected 1, got 0 edit.c:3234: Test failed: got 21 edit.c:3240: Test failed: got 21 https://test.winehq.org/data/patterns.html#user32:edit Where 5 is ERROR_ACCESS_DENIED and indicates that the clipboard has already been opened in another thread, process, etc. This happens a lot on machines with an AMD GPU due to known interference from the Radeon driver (see bug 47888). But it also happens sometimes on machines with an Nvidia GPU (cw-gtx560) and even on pure QEmu VMs such as w1064-1qxl (or fgtb-w10pro64). So there is either some other source of interference, maybe from some Windows component, or an issue (a race condition?) in the test itself. It would be nice to identify the source of interference, if any, to see if it can be neutralized. But maybe the only solution is to work around the issue as in user32:clipboard (see commit 316eec8f6658). -- 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 5

[Bug 55686] New: msvcr120:msvcr120 - test_StructuredTaskCollection() sometimes fails in Wine
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55686 Bug ID: 55686 Summary: msvcr120:msvcr120 - test_StructuredTaskCollection() sometimes fails in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- msvcr120:msvcr120 - test_StructuredTaskCollection() sometimes fails in Wine. The failures take different forms but always start on line 1596: msvcr120.c:1596: Test failed: Chore's task collection was not reset after execution Unhandled exception: C++ exception(object = 0x0063fc5c, type = 0x6355434c) in 32-bit code (0x7b012207). [...] msvcr120.c:1606: Test failed: Wrong chore #1 task_collection: expected 0063FCC0, actual 00000000 msvcr120.c:1609: Test failed: Wrong chore count: 0 != 1 msvcr120.c:1610: Test failed: Unexpected context: 00000000 != 009B1B80 msvcr120.c:1617: Test failed: Chore was not executed or msvcr120.c:1596: Test failed: Chore's task collection was not reset after execution 067c:msvcr120: 871 tests executed (1 marked as todo, 0 as flaky, 1 failure), 0 skipped. or msvcr120.c:1485: Test marked todo: _StructuredTaskCollection ctor set wrong unk2: 0x0 != 0x1fffffff Couldn't get first exception for process 010c C:\users\fgouget\Temp\wct\msvcr120_test.exe. No backtrace available msvcr120:msvcr120:010c done (-1073741819) in 0s 4591B See https://test.winehq.org/data/patterns.html#msvcr120:msvcr120 The failures started on 2023-09-19 so they are likely caused by one of the 2023-09-18 commits. * 2023-09-28 fg-deb64-t32 * 2023-09-27 fg-deb64-x86-64 * 2023-09-27 MR!3884 * 2023-09-26 MR!3963 * 2023-09-25 fg-deb64-i286 * 2023-09-25 MR!3930 * 2023-09-21 fg-deb64-i286 * 2023-09-19 rbernon-nulldrv-win32 * 2023-09-19 MR!3855 -- 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 55606] New: Finale 27 printing - incorrect linecap
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55606 Bug ID: 55606 Summary: Finale 27 printing - incorrect linecap Product: Wine Version: 8.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineps.drv Assignee: wine-bugs(a)winehq.org Reporter: davech(a)t-online.de Distribution: --- Wine 8.16 uses 'setlinecap' incorrectly in the postscript output. This is correct in wine 7.0.2 -- 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 11

[Bug 55272] New: The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55272 Bug ID: 55272 Summary: The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709 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 The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709: exception.c:3537: vect. handler c0000005 addr:000002858E4C0000 exception.c:3537: vect. handler c0000005 addr:000002858E4C0000 ntdll:exception:0dd8 done (-1073741819) in 0s 6581B See https://test.winehq.org/data/patterns.html#ntdll:exception Where -1073741819 == 0xC0000005 == STATUS_ACCESS_VIOLATION The crashes started with GitLab CI's switch to Debian 12 for the WineTest builds which are used in the WineTest nightlies. However they also happen with binaries built on Debian 11 in this case it is just a coincidence. Note that before that ntdll:exception was exiting silently on Windows 8 & 10 <= 1809, see bug 55111. These two issues may be one and the same, just producing different results due to changes in the binary layout. -- 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 55108] New: xaudio2_8:xaudio2 fails on Windows 10+
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55108 Bug ID: 55108 Summary: xaudio2_8:xaudio2 fails on Windows 10+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com xaudio2_8:xaudio2 fails on Windows 10+: xaudio2.c:1218: Test failed: Got hr 0x80004002. See https://test.winehq.org/data/patterns.html#xaudio2_8:xaudio2 Note that this is the same failure as what happened on Windows 8 in the late stages described in bug 55016. A bisect shows that this failure started with the commit below: commit e8b0e7c1fcf090ba80c543f68b0bdae185316327 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Fri Jun 16 15:13:14 2023 -0500 xaudio2/tests: Fix the IID_IXAudio28 declaration. This was accidentally copied from the 2.9 version instead in 14c44d0b0. -- 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 5

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 October 2023