https://bugs.winehq.org/show_bug.cgi?id=55424
Bug ID: 55424 Summary: user32:cursoricon - test_SetCursor() sometimes fails on w10pro64v2004 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com
user32:cursoricon - test_SetCursor() sometimes fails on w10pro64v2004:
cursoricon.c:2529: Test failed: expected global cursor 00010003
See https://test.winehq.org/data/patterns.html#user32:cursoricon
This failure first happened on 2023-06-05, always with the same cursor handle and always on w10pro64v2004: * 2023-06-05 win2004_newtb-w10pro64v2004-32 * 2023-06-07 win2004_newtb-w10pro64v2004-32 * 2023-06-16 win2004_newtb-w10pro64v2004-32 * 2023-06-19 win2004_newtb-w10pro64v2004-32 * 2023-06-28 win2004_newtb-w10pro64v2004-32 * 2023-08-08 win2004_newtb-w10pro64v2004-32 * 2023-08-08 win2004_newtb-w10pro64v2004-64
The 2023-08-08 final screenshots both show a Windows update window that should not be there. Maybe it is related.
https://bugs.winehq.org/show_bug.cgi?id=55424
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase
https://bugs.winehq.org/show_bug.cgi?id=55424
--- Comment #1 from François Gouget fgouget@codeweavers.com --- w1064pro2004's network card has a data cap which automatically sets it to metered mode. Same configuration as the 21h1 snapshots. Also in the days before there was no Windows Update window. There is still no proof any of this is related to this failure.
https://bugs.winehq.org/show_bug.cgi?id=55424
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon@codeweavers.com
--- Comment #2 from Rémi Bernon rbernon@codeweavers.com --- I don't this this happening, maybe it's fixed?