wine-bugs August 2023

wine-bugs@winehq.org

1 participants
2774 discussions

[Bug 54194] New: user32:msg - test_broadcast() sometimes fails to send WM_USER-1 on Windows 7
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54194 Bug ID: 54194 Summary: user32:msg - test_broadcast() sometimes fails to send WM_USER-1 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_broadcast() sometimes fails to send WM_USER-1 on Windows 7. 2022-12-29 w7u-2qxl (32-bit) msg.c:17379: Test failed: 0: message 03ff, got 0, error 1460 msg.c:17384: Test failed: 0,0: message 03ff, got 0, error 1460 msg.c:17384: Test failed: 0,1: message 03ff, got 0, error 1460 msg.c:17384: Test failed: 0,2: message 03ff, got 0, error 1460 msg.c:17384: Test failed: 0,3: message 03ff, got 0, error 1460 msg.c:17384: Test failed: 0,8: message 03ff, got 0, error 1460 msg.c:17384: Test failed: 0,9: message 03ff, got 0, error 1460 msg.c:17384: Test failed: 0,10: message 03ff, got 0, error 1460 msg.c:17384: Test failed: 0,11: message 03ff, got 0, error 1460 msg.c:17384: Test failed: 0,12: message 03ff, got 0, error 1460 2022-12-15 w7u (32-bit) msg.c:17379: Test failed: 0: message 03ff, got 0, error 0 msg.c:17384: Test failed: 0,0: message 03ff, got 0, error 0 msg.c:17384: Test failed: 0,1: message 03ff, got 0, error 0 msg.c:17384: Test failed: 0,2: message 03ff, got 0, error 0 msg.c:17384: Test failed: 0,3: message 03ff, got 0, error 0 msg.c:17384: Test failed: 0,8: message 03ff, got 0, error 0 msg.c:17384: Test failed: 0,9: message 03ff, got 0, error 0 msg.c:17384: Test failed: 0,10: message 03ff, got 0, error 0 msg.c:17384: Test failed: 0,11: message 03ff, got 0, error 0 msg.c:17384: Test failed: 0,12: message 03ff, got 0, error 0 2022-10-19 w7u-adm (32-bit) msg.c:17002: Test failed: 0: message 03ff, got 0, error 5 msg.c:17007: Test failed: 0,0: message 03ff, got 0, error 5 msg.c:17007: Test failed: 0,1: message 03ff, got 0, error 5 msg.c:17007: Test failed: 0,2: message 03ff, got 0, error 5 msg.c:17007: Test failed: 0,3: message 03ff, got 0, error 5 msg.c:17007: Test failed: 0,8: message 03ff, got 0, error 5 msg.c:17007: Test failed: 0,9: message 03ff, got 0, error 5 msg.c:17007: Test failed: 0,10: message 03ff, got 0, error 5 msg.c:17007: Test failed: 0,11: message 03ff, got 0, error 5 msg.c:17007: Test failed: 0,12: message 03ff, got 0, error 5 See https://test.winehq.org/data/patterns.html#user32:msg Where: 0x03ff == WM_USER-1 5 == ERROR_ACCESS_DENIED 1460 == ERROR_TIMEOUT 0, ERROR_ACCESS_DENIED and ERROR_TIMEOUT are the only three errors that were reported in the past 6 months. See also bug 54032 which deals with test_broadcast() sometimes getting ERROR_INVALID_PARAMETER. -- 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 55461] New: directmanipulation:manipulation sometimes times out on Windows 10
by WineHQ Bugzilla 14 Sep '23

14 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55461 Bug ID: 55461 Summary: directmanipulation:manipulation sometimes times out 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 directmanipulation:manipulation sometimes times out on Windows 10: directmanipulation:manipulation:2190 done (258) in 120s 0B See https://test.winehq.org/data/patterns.html#directmanipulation:manipulation The test normally runs in under 1 second which means the time out is caused by a deadlock. However this is pretty rare and has only happened twice in the past 8 months: * 2023-04-06 win21H1_newtb-w10pro64-hi-u8-64 (followed out-of-memory failures in previous tests) * 2023-08-18 win21H1_newtb-w10pro64-de-64 (followed dinput:joystick8 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 2

[Bug 55477] New: shell32:autocomplete - test_prefix_filtering() sometimes fails on Windows because the AutoComplete DropDown is visible
by WineHQ Bugzilla 14 Sep '23

14 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55477 Bug ID: 55477 Summary: shell32:autocomplete - test_prefix_filtering() sometimes fails on Windows because the AutoComplete DropDown is visible Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com shell32:autocomplete - test_prefix_filtering() sometimes fails on Windows because the AutoComplete DropDown is visible: autocomplete.c:671: Test failed: AutoComplete DropDown visible See https://test.winehq.org/data/patterns.html#shell32:autocomplete This is pretty rare and did not happen for 4 months but has started happening again: * 2023-01-16 win21H1_newtb-w10pro64-ar-64 * 2023-01-19 win22H2_newtb-w1064-tsign-64 * 2023-02-14 win1507_newtb-w1064v1507-64 * 2023-07-03 win21H1_newtb-w10pro64-he-64 * 2023-08-22 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 2

[Bug 55492] New: ntdll:threadpool - test_RtlRegisterWait() sometimes fails in Wine
by WineHQ Bugzilla 14 Sep '23

14 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55492 Bug ID: 55492 Summary: ntdll:threadpool - test_RtlRegisterWait() sometimes fails in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ntdll:threadpool - test_RtlRegisterWait() sometimes fails in Wine. There are three variants which look like they are probably related: (1) threadpool.c:354: Test failed: expected info.userdata = 1, got 0 threadpool.c:370: Test failed: expected info.userdata = 1, got 0 threadpool.c:371: Test failed: expected info.threadid != 0, got 0 threadpool.c:373: Test failed: OpenThread failed with 87 threadpool.c:376: Test failed: QueueUserAPC failed with 6 (2) threadpool.c:290: Test failed: expected info.userdata = 0, got 65536 threadpool.c:294: Test failed: expected info.userdata = 1, got 65536 threadpool.c:296: Test failed: WaitForSingleObject returned 0 (3) threadpool.c:292: Test failed: expected info.userdata = 1, got 65536 threadpool.c:294: Test failed: WaitForSingleObject returned 0 See https://test.winehq.org/data/patterns.html#ntdll:threadpool (1) This is the most common variant and it happens in both the GitLab and other non-TestBot VMs: * 2023-06-30 linux_fgtb-debian11-x86-64 * 2023-06-18 MR!3094 * 2023-06-06 linux_rbernon-vulkan-win64 * 2023-05-29 linux_fg-deb64-wow32 * 2023-05-24 MR!2628 * 2023-01-31 linux_fg-deb64-wow64 * 2023-01-11 MR!1940 (2) Only happened once and on the GitLab CI. * 2023-04-28 MR!2682 (3) Only happened on the GitLab CI. * 2023-08-25 linux_gitlab-debian-32 * 2023-06-02 MR!2954 -- 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 49868] New: Hedgewars 1.0.0 crashes when a game against the computer is started
by WineHQ Bugzilla 13 Sep '23

13 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=49868 Bug ID: 49868 Summary: Hedgewars 1.0.0 crashes when a game against the computer is started Product: Wine Version: 5.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: --- Created attachment 68209 --> https://bugs.winehq.org/attachment.cgi?id=68209 The console messages Hedgewars crashes when the following steps are taken: 1) remove .wine directory 2) run wineboot 3) run the Hedgewars installer, accept the defaults. This will start Hedgewards at the end of the installer 4) Press "Play a game on a single computer" 5) Press "Play a quick game against the computer with random settings" 6) Sometimes, the game now shows the error "The program hedgewars.exe has encountered a serious problem and needs to close" 7) if the game does not crash, press escape and Y, and repeat step 5 My versions: $ wine --version wine-5.17 (Staging) $ uname -a Linux cedric-p4 5.8.10-arch1-1 #1 SMP PREEMPT Thu, 17 Sep 2020 18:01:06 +0000 x86_64 GNU/Linux -- 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 54530] New: Unable to find an entry point named 'UiaDisconnectProvider' in DLL 'UIAutomationCore.dll'
by WineHQ Bugzilla 13 Sep '23

13 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54530 Bug ID: 54530 Summary: Unable to find an entry point named 'UiaDisconnectProvider' in DLL 'UIAutomationCore.dll' Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: uiautomationcore Assignee: wine-bugs(a)winehq.org Reporter: hunt3rgz(a)protonmail.com Distribution: --- Created attachment 74074 --> https://bugs.winehq.org/attachment.cgi?id=74074 Wine log I runned a .NET 5.0 application written with Windows Forms https://github.com/X-Hax/sa_tools When i close the 'create gradient' window, it gives me this error System.EntryPointNotFoundException: Unable to find an entry point named 'UiaDisconnectProvider' in DLL 'UIAutomationCore.dll'. at Interop.UiaCore.UiaDisconnectProvider(IRawElementProviderSimple provider) at System.Windows.Forms.Control.ReleaseUiaProvider(IntPtr handle) at System.Windows.Forms.Control.WmDestroy(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam) -- 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 53434] New: user32:msg - test_SendMessage_other_thread() sometimes fails on Windows 10 1507 - 1909
by WineHQ Bugzilla 12 Sep '23

12 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=53434 Bug ID: 53434 Summary: user32:msg - test_SendMessage_other_thread() sometimes fails on Windows 10 1507 - 1909 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_SendMessage_other_thread() sometimes fails on Windows 1507 - 1909: msg.c:18493: main: call PeekMessage msg.c:18505: Test failed: wrong status 00080000 msg.c:18507: main: call PeekMessage msg.c:18508: Test failed: PeekMessage should fail https://test.winehq.org/data/patterns.html#user32:msg Where 0x00080000 indicates that there are still QS_POSTMESSAGE messages in the queue and that none were added since the last call. This only happens on Windows 10 1507 to 1909. -- 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 12854] New: ntdll change.ok test fails in PC-BSD but not Linux
by wine-bugs＠winehq.org 12 Sep '23

12 Sep '23

http://bugs.winehq.org/show_bug.cgi?id=12854 Summary: ntdll change.ok test fails in PC-BSD but not Linux Product: Wine Version: 0.9.60 Platform: PC OS/Version: FreeBSD Status: NEW Keywords: testcase Severity: minor Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=12551) --> (http://bugs.winehq.org/attachment.cgi?id=12551) +file in git, bzip2 -9'ed Change.ok is full of failures in PC-BSD: change.c:117: Test failed: event should be ready change.c:119: Test failed: information wrong change.c:120: Test failed: information wrong change.c:124: Test failed: action wrong change.c:125: Test failed: len wrong change.c:126: Test failed: name wrong Total of 26. Attached is a +file log. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 18

[Bug 38095] New: Metatrader: doesn't respect charts sorting/sequency when restarted
by wine-bugs＠winehq.org 12 Sep '23

12 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=38095 Bug ID: 38095 Summary: Metatrader: doesn't respect charts sorting/sequency when restarted Product: WineHQ Apps Database Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: 23bene(a)gmail.com Distribution: --- Wine 1.6 on Ubuntu 14.04.1 LTS 32bit using Metatrader 4 vers. 4.00 Build 765 (12 Dec 2014) doesn't respect charts sorting/sequency when restarted. Eg.: if I sort charts alphabetically during my Metatrader session, it remain so sorted till I close it. When I open again for a new Metatrader session, I find charts completely shuffled!! I copypasted my order.wnd file (that contain my charts ordered) in my home/.wine/drive_c/Program Files/Metatrader 4/profiles/my_name/ directory without having no one mt4 session opened. When I launch mt4 session, it doesn't follow charts order as written in my file and everytime I launch it again a new, random charts sequence is done. -- 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 10

[Bug 55066] New: user32:msg - test_button_messages() sometimes gets WM_SIZE instead of WM_SETFOCUS in Wine
by WineHQ Bugzilla 11 Sep '23

11 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55066 Bug ID: 55066 Summary: user32:msg - test_button_messages() sometimes gets WM_SIZE instead of WM_SETFOCUS in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:msg - test_button_messages() sometimes gets WM_SIZE instead of WM_SETFOCUS in Wine: msg.c:6897: Test failed: SetFocus(hwnd) on a button: 4: the msg 0x0007 was expected, but got msg 0x0005 instead msg.c:6897: Test failed: SetFocus(hwnd) on a button: 5: the msg 0x0138 was expected, but got msg 0x030f instead msg.c:6897: Test failed: SetFocus(hwnd) on a button: 6: the msg 0x0111 was expected, but got msg 0x001c instead msg.c:6897: Test failed: SetFocus(hwnd) on a button: 8: the msg 0x8000 was expected, but got msg 0x0086 instead msg.c:6897: Test failed: SetFocus(hwnd) on a button: 9: the msg sequence is not complete: expected 0000 - actual 0006 See https://test.winehq.org/data/patterns.html#user32:msg This first happened on 2023-05-19 and since then it has been happening in about 4% of the runs. -- 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

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