wine-bugs December 2022

wine-bugs@winehq.org

1 participants
3222 discussions

[Bug 45531] New: Tencent Gaming buddy crashes during pubg installation
by wine-bugs＠winehq.org 05 Dec '22

05 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=45531 Bug ID: 45531 Summary: Tencent Gaming buddy crashes during pubg installation Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: basith374(a)gmail.com Distribution: --- It says AppMarket.exe has encountered a serious problem. -- 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 14

[Bug 54077] New: rpcrt4:server - basic_tests() sometimes crashes on Windows 10 2004+
by WineHQ Bugzilla 04 Dec '22

04 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54077 Bug ID: 54077 Summary: rpcrt4:server - basic_tests() sometimes crashes on Windows 10 2004+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com rpcrt4:server - basic_tests() sometimes crashes on Windows 10 2004+: server.c:1397: this is the last test seen before the exception 2398:server: unhandled exception 000006be at 00007FFA1E1BCD29 See https://test.winehq.org/data/patterns.html#rpcrt4:server Where 0x000006be is probably RPC_S_CALL_FAILED. This crash does not seem to be happening on Windows 11. -- 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 53134] New: ddraw:ddraw7 - test_coop_level_mode_set() has a rare set of 18 failures on Windows 8
by WineHQ Bugzilla 04 Dec '22

04 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53134 Bug ID: 53134 Summary: ddraw:ddraw7 - test_coop_level_mode_set() has a rare set of 18 failures on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw7 - test_coop_level_mode_set() has a rare set of 18 failures on Windows 8: ddraw7.c:3177: Test failed: Expected message 0x46, but didn't receive it. ddraw7.c:3179: Test failed: Expected screen size 1024x768, got 0x0. ddraw7.c:3185: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3215: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3222: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3248: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3271: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3293: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3319: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3339: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3375: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3385: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3411: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3434: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3456: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3482: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3502: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). ddraw7.c:3539: Test failed: Expected (0,0)-(1024,768), got (-8,-8)-(1032,736). https://test.winehq.org/data/patterns.html#ddraw:ddraw7 Because they are rare (~4.9%) these failures cause false positives. They also did not happen on the Windows 8 configuration of cw-gtx560 and cw-rx460, so they may be related to QEmu. -- 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 54066] New: SysLink control shouldn't delete the HFONT it didn't create
by WineHQ Bugzilla 03 Dec '22

03 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54066 Bug ID: 54066 Summary: SysLink control shouldn't delete the HFONT it didn't create Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: vz-wine(a)zeitlins.org Distribution: --- I believe there is a bug in `dlls/comctl32/syslink.c` where `WM_DESTROY` handler calls `DeleteObject(infoPtr->Font)`, although this font is not owned by the control -- it is (or can be) given to it via `WM_SETFONT` and doing this means that a system font can be destroyed prematurely, resulting in plenty of other problems later on in the program. Amazingly, it looks like this code was there since a1f3756daab (Free allocated font handles when control is destroyed., 2004-12-08) and I don't really understand how could it not be noticed until now, but apparently somehow it wasn't. The following trivial patch: ``` diff --git a/dlls/comctl32/syslink.c b/dlls/comctl32/syslink.c index 8130bf19641..efc3467838b 100644 --- a/dlls/comctl32/syslink.c +++ b/dlls/comctl32/syslink.c @@ -1709,7 +1709,6 @@ static LRESULT WINAPI SysLinkWindowProc(HWND hwnd, UINT message, case WM_DESTROY: TRACE("SysLink Ctrl destruction, hwnd=%p\n", hwnd); SYSLINK_ClearDoc(infoPtr); - if(infoPtr->Font != 0) DeleteObject(infoPtr->Font); if(infoPtr->LinkFont != 0) DeleteObject(infoPtr->LinkFont); SetWindowLongPtrW(hwnd, 0, 0); Free (infoPtr); ``` is enough to fix the problem for me. -- 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 0

[Bug 54063] New: msctf:inputprocessor sometimes gets an unexpected OnSetFocus event in Windows & Wine
by WineHQ Bugzilla 03 Dec '22

03 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54063 Bug ID: 54063 Summary: msctf:inputprocessor sometimes gets an unexpected OnSetFocus event in Windows & Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: msctf Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com msctf:inputprocessor sometimes gets an unexpected OnSetFocus event in Windows & Wine: inputprocessor.c:2288: found {575F3783-70C8-47C8-AE5D-91A01A1F7592} inputprocessor.c:549: Test failed: Unexpected ThreadMgrEventSink_OnSetFocus sink inputprocessor.c:1020: TextService_Deactivate inputprocessor.c:1249: Disabling See https://test.winehq.org/data/patterns.html#msctf:inputprocessor This pretty rare. There are only 3 instances in about 6 months: * 2022-06-17 on fgtb-debian11 (64-bit), in two runs * 2022-11-30 on w7u-2qxl (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 1

[Bug 54062] New: msctf:inputprocessor - test_AssociateFocus() sometimes crashes in Wine
by WineHQ Bugzilla 03 Dec '22

03 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54062 Bug ID: 54062 Summary: msctf:inputprocessor - test_AssociateFocus() sometimes crashes in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msctf Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- msctf:inputprocessor - test_AssociateFocus() sometimes crashes in Wine: inputprocessor.c:2437: Test failed: Expected DocumentMgr not focused Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x0040ae26). [...useless backtrace...] See https://test.winehq.org/data/patterns.html#msctf:inputprocessor The earliest known instance occurred on 2022-07-04 on debian11-wow64. This impacts both the 32- and 64-bit builds. -- 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 53252] New: d3d10core:d3d10core - test_occlusion_query() sometimes fails on Windows 10 1909+
by WineHQ Bugzilla 03 Dec '22

03 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53252 Bug ID: 53252 Summary: d3d10core:d3d10core - test_occlusion_query() sometimes fails on Windows 10 1909+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d10core:d3d10core - test_occlusion_query() sometimes fails on Windows 10 1909+: d3d10core.c:4665: Test failed: Got unexpected query result 0x0000000000000000. https://test.winehq.org/data/patterns.html#d3d10core:d3d10core These failures only seem to happen on with Windows' basic 'VGA' driver (whether it's on top of QEmu's VGA or QXL GPU). They are also rare enough to cause 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 2

[Bug 53465] New: conhost.exe:tty - test_tty_output() sometimes fails on Windows 10
by WineHQ Bugzilla 03 Dec '22

03 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53465 Bug ID: 53465 Summary: conhost.exe:tty - test_tty_output() sometimes fails on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com conhost.exe:tty - test_tty_output() sometimes fails on Windows 10. There are only three known failures spread across two similar failure modes: * 2022-07-27 w10pro64-pt-BR * 2022-07-27 w10pro64-mx-MX (mixed locale) tty.c:1051: Test failed: avail = 3 tty.c:1051: Test failed: expected empty buffer, got "\x1b[m" tty.c:1058: Test failed: 0: expected "\x1b[9;4H" got "\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1059: Test failed: 0: expected "5" got "\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1060: Test failed: 0: expected "\x1b[4;3H" got "\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1061: Test failed: 0: expected "\x1b[?25h" got "\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1062: Test failed: expected empty buffer, got "\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" * 2022-07-29 w10pro64-pt-BR tty.c:1055: Test failed: expected hide cursor escape tty.c:1057: Test failed: 0: expected "\x1b[30m" got "\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1058: Test failed: 0: expected "\x1b[9;4H" got "\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1059: Test failed: 0: expected "5" got "\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1060: Test failed: 0: expected "\x1b[4;3H" got "\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1061: Test failed: 0: expected "\x1b[?25h" got "\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1062: Test failed: expected empty buffer, got "\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" -- 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 54059] New: user32:input - test_GetMouseMovePointsEx() sometimes fails on Windows 10+
by WineHQ Bugzilla 03 Dec '22

03 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54059 Bug ID: 54059 Summary: user32:input - test_GetMouseMovePointsEx() sometimes fails on Windows 10+ 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:input - test_GetMouseMovePointsEx() sometimes fails on Windows 10+: input.c:1647: Test failed: expected to get 62 mouse move points but got 64 input.c:1649: Test failed: expected cursor position to be 30x30 but got 150 150 See https://test.winehq.org/data/patterns.html#user32:input This impacts Windows 10 from 1809 to Windows 11 but it seems it can also happen on Windows 7 (though in practice not on the TestBot VMs?). -- 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 53474] New: Change in memory handling gives crash in Framemaker 8
by WineHQ Bugzilla 03 Dec '22

03 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53474 Bug ID: 53474 Summary: Change in memory handling gives crash in Framemaker 8 Product: Wine Version: 7.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- The following commit commit a4966b6690b31c4884d07a8a745017adb6363834 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Thu Jun 9 14:13:53 2022 +0200 kernelbase: Cleanup and simplify (Global|Local)ReAlloc. Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> dlls/kernel32/heap.c | 22 ++++++++- dlls/kernel32/tests/heap.c | 15 ------- dlls/kernelbase/memory.c | 108 +++++++++++++++------------------------------ 3 files changed, 56 insertions(+), 89 deletions(-) leads to a crash in Framemaker 8. Reverting the patch on top of wine-7.14 solves the problem. To reproduce (simplest way): - Start Framemaker and create a new document - Open the print dialog (Ctrl-P) - Select another printer (lower part of the dialog) - Framemaker crashes with an internal error Framemaker generates a log file (which is IMHO useless but attached anyway) I can provide a demo version of framemaker if this would help. -- 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

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 December 2022