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

[Bug 55317] New: user32:msg - test_hotkey() finds no free WinKey+letter on Windows 11
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55317 Bug ID: 55317 Summary: user32:msg - test_hotkey() finds no free WinKey+letter on Windows 11 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_hotkey() finds no free WinKey+letter on Windows 11: msg.c:18487: Test failed: Couldn't find any free Windows Key + letter combination See https://test.winehq.org/data/patterns.html#user32:msg -- 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 52196] New: Program desinger.exe stop after starting with error
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=52196 Bug ID: 52196 Summary: Program desinger.exe stop after starting with error Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: werbung(a)itssh.de Distribution: --- Created attachment 71249 --> https://bugs.winehq.org/attachment.cgi?id=71249 Bugreport The install of this program was completed with no errors. It was installed along with another program. The main program works wonderfully, but the sub-program (desinger.exe) does not. The OS is up to date. Wine is up to date. In OS windows7 the program works. -- 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 19

[Bug 54368] New: ::DrawGeometry doesn't respect stroke style
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54368 Bug ID: 54368 Summary: ::DrawGeometry doesn't respect stroke style Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: dmitry(a)baikal.ru Distribution: --- Created attachment 73938 --> https://bugs.winehq.org/attachment.cgi?id=73938 thick lines There's an application that uses d2d1 to draw its UI, and when the app scales its workspace the lines get very thick shapes. This seems to be related to 00d8:fixme:d2d:d2d_stroke_style_init transformType 1 is not supported 00d8:fixme:d2d:d2d_device_context_DrawGeometry Ignoring stroke style 000000001F3D8C80. According to MSDN transformType 1 refers to D2D1_STROKE_TRANSFORM_TYPE_FIXED: The stroke does not respect the world transform but it does respect the dpi and stroke width. -- 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 54202] New: user32:msg - subtest_hvredraw() fails on most Windows 7 test configurations
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54202 Bug ID: 54202 Summary: user32:msg - subtest_hvredraw() fails on most Windows 7 test configurations 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 - subtest_hvredraw() fails on most Windows 7 test configurations msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos redraw #0 (0, 0, 0, 50): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos redraw #1 (0, 0, 50, 0): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos redraw #2 (0, 0, 50, 50): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos redraw #3 (0, 0, -50, -50): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos redraw #4 (-50, -50, 0, 50): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos redraw #0 (0, 0, 0, 50): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos redraw #1 (0, 0, 50, 0): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos redraw #2 (0, 0, 50, 50): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos redraw #3 (0, 0, -50, -50): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 00cf0000 SetWindowPos redraw #5 (-50, -50, 50, 0): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithHVRedraw 00cf0000 SetWindowPos redraw #0 (0, 0, 0, 50): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithHVRedraw 00cf0000 SetWindowPos redraw #1 (0, 0, 50, 0): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithHVRedraw 00cf0000 SetWindowPos redraw #2 (0, 0, 50, 50): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithHVRedraw 00cf0000 SetWindowPos redraw #3 (0, 0, -50, -50): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 40800000 SetWindowPos redraw #0 (0, 0, 0, 50): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithHRedraw 40800000 SetWindowPos redraw #4 (-50, -50, 0, 50): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 40800000 SetWindowPos redraw #1 (0, 0, 50, 0): Update region shall match expected region msg.c:9478: Test failed: SimpleWindowClassWithVRedraw 40800000 SetWindowPos redraw #5 (-50, -50, 50, 0): Update region shall match expected region msg.c:9764: Test failed: destroy child on thread exit: 1: the msg sequence is not complete: expected 000f - actual 0000 msg.c:9764: Failed sequence destroy child on thread exit: msg.c:9764: 0: expected: msg 0082 - actual: MsgCheckProc: 00BC00A0 0082 wp 00000000 lp 00000000 (flags 19) msg.c:9764: 1: expected: msg 000f - actual: nothing See https://test.winehq.org/data/patterns.html#user32:msg These failures appeared as soon as the corresponding tests were introduced but somehow the TestBot did not detect them when MR!1874 was submitted. So maybe they are caused by interference from a previous Wine test. commit b2a9445e155487f1b47a646b70edbe181a905454 Author: Jinoh Kang <jinoh.kang.kr(a)gmail.com> Date: Thu Dec 22 01:20:59 2022 +0900 user32/tests: Add tests for CS_HREDRAW and CS_VREDRAW. -- 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 54998] New: DnsQuery(DNS_TYPE_SRV) fails to parse some of the server answers
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54998 Bug ID: 54998 Summary: DnsQuery(DNS_TYPE_SRV) fails to parse some of the server answers Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: NEW Keywords: patch, source Severity: normal Priority: P2 Component: dnsapi Assignee: wine-bugs(a)winehq.org Reporter: dmitry(a)baikal.ru Distribution: --- Created attachment 74551 --> https://bugs.winehq.org/attachment.cgi?id=74551 patch An application that uses ActiveDs sometimes fails to get domain DC using DsGetDcNameW(). That's caused by a failing call to DnsQuery("_ldap._tcp.dc._msdcs.domain.com", DNS_TYPE_SRV) which in turn fails because DnsExtractRecordsFromMessage_UTF8() fails to parse some of the server answers. It looks like this happens because in the DNS_TYPE_SRV record name is the last element, and in that case get_name() uses wrong boundary check and returns NULL. Just in case it will be useful I'm attaching my version of the fix with some tests. It seems that skip_name() also uses wrong boundary check, however usually some other data follows the skipped name, so it currently doesn't cause failures. -- 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 54655] New: user32:msg - test_InSendMessage() sometimes gets unexpected flags on Windows
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54655 Bug ID: 54655 Summary: user32:msg - test_InSendMessage() sometimes gets unexpected flags 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:msg - test_InSendMessage() sometimes gets unexpected flags on Windows: msg.c:11738: Tests skipped: cannot set global hook msg.c:19232: Failed sequence SendMessage from other thread 1: msg.c:19232: 0: expected: msg 0402 - actual: MsgCheckProc: 00000000008B03E8 0402 wp 00000000 lp 00000000 (flags 19) msg.c:19232: 1: expected: msg 0400 - actual: MsgCheckProc: 00000000008B03E8 0400 wp 00000000 lp 00000000 (flags 19) msg.c:19252: Failed sequence SendMessage from other thread 3: msg.c:19252: 0: expected: msg 0403 - actual: MsgCheckProc: 00000000008B03E8 0403 wp 00000000 lp 00000000 (flags 19) msg.c:19252: 1: expected: msg 0401 - actual: MsgCheckProc: 00000000008B03E8 0401 wp 00000000 lp 00000000 (flags 19) msg.c:19264: Failed sequence SendMessage from other thread 5: msg.c:19292: Test failed: wrong flags a msg.c:18660: Failed sequence SetFocus on a desktop window: See https://test.winehq.org/data/patterns.html#user32:msg Where 0xa == ISMEX_NOTIFY | ISMEX_REPLIED and the test expected 0x9 == ISMEX_SEND | ISMEX_REPLIED This happens about once per month and impacts at least Windows 7 & 10, regardless of locale: * 2022-08-31 on w7u-pt-PT 32-bit * 2022-08-31 on w7u 32-bit * 2022-09-06 on w7u 32-bit * 2022-09-15 on w7u-pt-PT 32-bit * 2022-12-12 on w1064 32-bit * 2023-02-20 on w10pro64-ar 64-bit * 2023-03-02 on w7u-de 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 5

[Bug 51995] New: Roblox's bad performance on Wine
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=51995 Bug ID: 51995 Summary: Roblox's bad performance on Wine Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: penguinbotonline(a)protonmail.com Distribution: --- Created attachment 70986 --> https://bugs.winehq.org/attachment.cgi?id=70986 Stderr log from Wine There is a common problem that occurs to the majority of RoL players, which is bad performance. There 2 things that people usually have, frame drops and performance degradation. When a frame drop happens, with +seh these things appear in the logs -- 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 55354] New: user32:msg - test_dialog_messages() sometimes gets a bad sequence on Windows 7
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55354 Bug ID: 55354 Summary: user32:msg - test_dialog_messages() sometimes gets a bad sequence 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_dialog_messages() sometimes gets a bad message sequence on Windows 7: msg.c:15393: Test failed: CreateDialogParam_1: 17: the msg 0x001c was expected, but got msg 0x000d instead msg.c:15393: Test failed: CreateDialogParam_1: 18: the msg 0x0086 was expected, but got msg 0x0083 instead msg.c:15393: Test failed: CreateDialogParam_1: 19: the msg 0x0006 was expected, but got msg 0x800b instead msg.c:15393: Test failed: CreateDialogParam_1: 20: the msg 0x8005 was expected, but got msg 0x001c instead msg.c:15393: Test failed: CreateDialogParam_1: 21: the msg 0x0007 was expected, but got msg 0x0086 instead msg.c:15393: Test failed: CreateDialogParam_1: 23: the msg sequence is not complete: expected 0000 - actual 0006 See https://test.winehq.org/data/patterns.html#user32:msg Where: 0x0006 == WM_ACTIVATE 0x000d == WM_GETTEXT 0x001c == WM_ACTIVATEAPP 0x0083 == WM_NCCALCSIZE 0x0086 == WM_NCACTIVATE 0x8005 == EVENT_OBJECT_FOCUS 0x800b == EVENT_OBJECT_LOCATIONCHANGE This first happened on 2023-06-22 and there has been about one instance per week since, always receiving the same unexpected message sequence: * 2023-06-22 win7_newtb-w7u-2qxl * 2023-06-28 win7_newtb-w7u-es * 2023-07-05 win7_newtb-w7u-2qxl * 2023-07-27 win7_newtb-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 7

[Bug 55238] New: ntdll:exception - The 64-bit test_nested_exception() fails on Windows 11
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55238 Bug ID: 55238 Summary: ntdll:exception - The 64-bit test_nested_exception() 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 - The 64-bit test_nested_exception() fails on Windows 11: exception.c:4842: nested_exception_handler Rip 000001E4AD6D0007, Rsp 00000012F5BFFAB0, code 0x80000003, flags 0, ExceptionAddress 000001E4AD6D0007. exception.c:4842: nested_exception_handler Rip 00007FFA236D428C, Rsp 00000012F5BFEAC0, code 0xdeadbeef, flags 0x90, ExceptionAddress 00007FFA236D428C. exception.c:4867: Test failed: Got unexpected exception code 0xdeadbeef, flags 0x90. exception.c:4870: Test failed: Got unexpected frame 00000012F5BFFAB0. exception.c:4891: Test failed: Did not get nested exception. See https://test.winehq.org/data/patterns.html#ntdll:exception This failure is specific to the 64-bit tests and only happen on the Windows 11 VM, with out without the AMD/NVidia GPUs (but the nightlies only run the 32-bit tests on the base 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.

1 5

[Bug 54944] New: ntdll:exception - test_extended_context() crashes on Window 11
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54944 Bug ID: 54944 Summary: ntdll:exception - test_extended_context() crashes on Window 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_extended_context() crashes on Window 11: exception.c:9542: Test failed: Got unexpected result ret 0, length 0x4ff. exception.c:9556: Test failed: Got unexpected result ret 0, length 0x4ff, flags 0x00100001. exception.c:9590: Test failed: Got unexpected bret 0, GetLastError() 122, flags 0x100001. exception.c:9592: Test failed: Got unexpexted length 0x4ff. exception.c:9593: Test failed: Got unexpected context 00000000DEADBEEF, flags 0x100001. exception.c:9596: Test failed: Got unexpected ContextFlags 0xcccccccc, flags 0x100001. exception.c:9599: Test failed: Got unexpected Offset -858993460, flags 0x100001. exception.c:9601: Test failed: Got unexpected Length 0xcccccccc, flags 0x100001. exception.c:9604: Test failed: Got unexpected Offset -858993460, flags 0x100001. exception.c:9608: Test failed: Got unexpected Length 0xcccccccc, flags 0x100001. exception.c:9611: Test failed: Got unexpected Offset -858993460, flags 0x100001. exception.c:9613: Test failed: Got unexpected Length 0xcccccccc, flags 0x100001. exception.c:9622: Test failed: Got unexpected p FFFFFFFFCD43BDDC, flags 0x100001. exception.c:9625: Test failed: Got unexpected p FFFFFFFFCD43BDDC, length 0xcccccccc, flags 0x100001. ntdll:exception:0974 done (-1073741819) in 0s 9642B See https://test.winehq.org/data/patterns.html#ntdll:exception The crash is systematic and happens in both the 32- and 64-bit tests. More specifically the crash happens in the first call to GetXStateFeaturesMask() but the real issue is the failure on line 9593 which indicates that the context parameter is wrong. -- 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