January 2023 - Wine-Bugs - list.winehq.org

[Bug 44414] New: GetNamedPipeHandleState not properly implemented
by wine-bugs＠winehq.org March 18, 2023

March 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=44414 Bug ID: 44414 Summary: GetNamedPipeHandleState not properly implemented Product: Wine Version: 3.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: ossman(a)cendio.se Distribution: --- I'm getting these running the Windows version of the ThinLinc client: 002f:fixme:sync:GetNamedPipeHandleStateW 0x4c 0x84e300 (nil) (nil) (nil) (nil) 0: semi-stub 002f:fixme:sync:GetNamedPipeHandleStateW 0x4c 0x84e300 (nil) (nil) (nil) (nil) 0: semi-stub 002f:fixme:sync:GetNamedPipeHandleStateW 0x50 0x84e300 (nil) (nil) (nil) (nil) 0: semi-stub 002f:fixme:sync:GetNamedPipeHandleStateW 0x50 0x84e300 (nil) (nil) (nil) (nil) 0: semi-stub 002f:fixme:sync:GetNamedPipeHandleStateW 0x54 0x84e300 (nil) (nil) (nil) (nil) 0: semi-stub 002f:fixme:sync:GetNamedPipeHandleStateW 0x54 0x84e300 (nil) (nil) (nil) (nil) 0: semi-stub It uses that call to set and remove PIPE_NOWAIT. The client also locks up, but I'm not sure it is because of this stub or something else. -- 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 3

[Bug 29902] New: Windows Live Messenger 8.5 does login, error 81000378
by wine-bugs＠winehq.org March 18, 2023

March 18, 2023

http://bugs.winehq.org/show_bug.cgi?id=29902 Bug #: 29902 Summary: Windows Live Messenger 8.5 does login, error 81000378 Product: Wine Version: 1.4-rc3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fael_mc(a)msn.com Classification: Unclassified Created attachment 38893 --> http://bugs.winehq.org/attachment.cgi?id=38893 Log, try entering the messenger salutations (google translation) I installed messenger through .msi package without problems in wine, I went to winecfg, changed windows version to 2000, when I opened the messenger if you could not type anything in the field username and password, then Riched20 installed through winetricks, so I could enter my username and password when I try to get in, get into normal, but not time to appear the contacts of the error 81000378 "You cannot use Windows Live Messenger at this time because your contact list is not available.Please try again later" I made some test with Wine 1.1.30, and usually logged, but the messenger is buggy I want to run it under wine 1.4 thank you -- 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 32

[Bug 29942] New: Windows Live Messenger 8.5, lock in chat windows
by wine-bugs＠winehq.org March 18, 2023

March 18, 2023

http://bugs.winehq.org/show_bug.cgi?id=29942 Bug #: 29942 Summary: Windows Live Messenger 8.5, lock in chat windows Product: Wine Version: 1.4-rc4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fael_mc(a)msn.com Classification: Unclassified Created attachment 38969 --> http://bugs.winehq.org/attachment.cgi?id=38969 Terminal log Greetings I managed to run and log into Windows Live Messenger 8.5 on wine, the bug does not login, (bug 29902) was solved with a patch disponiblizado by Juan Lang. Now I have another problem, after logging all normal, see the contacts, can I change nickname, phrase, image. I open the chat window to talk, I type normal, but when I send the message, the program crashes, and gets caught, taking 30% cpu. to have Windows Live Messenger 8.5 on wine, follow these steps: Download messenger: http://www.mediafire.com/?tlywu43id00 Normal installation in wine, and install riched20 msxml3 by winetricks, then set the Wine version for Windows 2000, done that is possible to login. But to login you must have wine with the patch: http://www.winehq.org/pipermail/wine-patches/2012-February/111655.html http://www.winehq.org/pipermail/wine-patches/2012-February/111656.html applied, but the Windows Live Messenger error 81000378 will Post here the log of the terminal, since the messenger open, until it freezes in the chat window -- 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 10

[Bug 54008] New: d3d9:device sometimes fails to create a D3D object in Wine, crashes
by WineHQ Bugzilla March 17, 2023

March 17, 2023

https://bugs.winehq.org/show_bug.cgi?id=54008 Bug ID: 54008 Summary: d3d9:device sometimes fails to create a D3D object in Wine, crashes Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d9:device sometimes fails to create a D3D object on the TestBot VMs, crashes. The failure and ensuing crash can happen in many locations: test_get_rt(): device.c:4821: Test failed: Received unexpected WM_SIZE message. device.c:3016: Test failed: Failed to create a D3D object. Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x000000004154d5). test_multi_adapter(): device.c:14264: Test failed: Failed to create a D3D object. Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00459a93). test_cursor_pos(): device.c:5241: Test failed: Failed to create a D3D object. Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x0041816a). See https://test.winehq.org/data/patterns.html#d3d9:device This failure can probably happen anywhere in the test. -- 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 54298] New: d3d12:d3d12 - test_desktop_window() fails on Windows 10 1709
by WineHQ Bugzilla March 17, 2023

March 17, 2023

https://bugs.winehq.org/show_bug.cgi?id=54298 Bug ID: 54298 Summary: d3d12:d3d12 - test_desktop_window() fails on Windows 10 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d12:d3d12 - test_desktop_window() fails on Windows 10 1709: d3d12.c:1412: Test failed: Got unexpected hr 0x8007000e. See https://test.winehq.org/data/patterns.html#d3d12:d3d12 Where 0x8007000e == E_OUTOFMEMORY. * On w1064v1507 and w1064v1607 this test is skipped because init_test_context() fails to create a device. * On w1064v1809 and greater this specific test just succeeds (and another fails instead). * So w1064v1709 supports just enough of d3d12 to run the test, but not enough to succeed. Maybe just add a broken()? https://gitlab.winehq.org/wine/wine/-/merge_requests/1961 -- 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 54052] New: winhttp:notification times out randomly in Wine
by WineHQ Bugzilla March 17, 2023

March 17, 2023

https://bugs.winehq.org/show_bug.cgi?id=54052 Bug ID: 54052 Summary: winhttp:notification times out randomly in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winhttp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- winhttp:notification times out randomly in Wine. First, on 2022-11-24 Paul Gofman got a series of patches in that probably fixed a bunch of these random timeouts (the situation on fg-deb64 and fgtb-debian11 seems better for one). However the following merge requests got timeouts after the patches went in: * MR!1553 on 2022-11-26 ... notification.c:117: Test failed: 892: expected status 0x20000 got 0x200000 winhttp:notification:0b98 done (258) in 120s 1148B * MR!1557 on 2022-11-27 ... notification.c:117: Test failed: 988: expected status 0x80000 got 0x200000 winhttp:notification:06d0 done (258) in 120s 1148B * MR!1560 on 2022-11-27 ... notification.c:1184: Test marked todo: got 3 winhttp:notification:052c done (258) in 120s 1118B Where: 0x20000 == WINHTTP_CALLBACK_STATUS_HEADERS_AVAILABLE 0x80000 == WINHTTP_CALLBACK_STATUS_READ_COMPLETE 0x200000 == WINHTTP_CALLBACK_STATUS_REQUEST_ERROR So there may still be some issue left. -- 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 53975] New: d3drm:d3drm sometimes fails to create an immediate mode device in Wine
by WineHQ Bugzilla March 17, 2023

March 17, 2023

https://bugs.winehq.org/show_bug.cgi?id=53975 Bug ID: 53975 Summary: d3drm:d3drm sometimes fails to create an immediate mode device in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3drm:d3drm sometimes fails to create an immediate mode device in Wine: d3drm.c:5843: Test failed: Cannot create IM device, skipping tests. This can happen in either test_create_device_from_d3d2() or test_create_device_from_d3d3() and always comes with the following winediag message repeated 3 times in the Wine log: 063c:err:winediag:d3d_device_create The application wants to create a Direct3D device, but the current DirectDrawRenderer does not support this. See https://test.winehq.org/data/patterns.html#d3drm:d3drm So far this has only been seen on debian11 and debiant so it may be related to their dual-screen configuration. Also this failure first happened on 2022-11-07 and there are 4 known instances so far (2 in the nightly runs and 2 TestBot job false positives). So it is probably caused by some recent Wine change. -- 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 53270] New: test_WSARecv() fails when using wow64 thunks [Wow64ApcRoutine() overwrites return value set by NtContinue()]
by WineHQ Bugzilla March 17, 2023

March 17, 2023

https://bugs.winehq.org/show_bug.cgi?id=53270 Bug ID: 53270 Summary: test_WSARecv() fails when using wow64 thunks [Wow64ApcRoutine() overwrites return value set by NtContinue()] Product: Wine Version: 7.11 Hardware: x86-64 OS: Linux Status: NEW Keywords: source, testcase Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Created attachment 72642 --> https://bugs.winehq.org/attachment.cgi?id=72642 test diff This might be a bit early since the wow64 path isn't exactly supported, but (with a couple patches to ntdll to enable it in the first place) it works well enough to expose a bug in its own implementation, which is more than a little tricky to solve. I'm attaching a diff to the tests, which I will submit upstream, which demonstrates the root of the problem. KiUserApcDispatcher can be called from three-ish places: wait functions, NtTestAlert, and NtContinue. In the case of the former two KiUserApcDispatcher will be passed a wow64 context which, among other things, has its %rax/%eax set to STATUS_USER_APC or STATUS_SUCCESS respectively. In the latter case %rax/%eax comes from the passed-in context. Wow64ApcRoutine tries to translate the %rax from the 64-bit context into the %eax that the 32-bit context will restore to. In the former two cases this is STATUS_USER_APC or STATUS_SUCCESS and things work fine. In the latter case, however, this overwrites %eax from the passed-in 32-bit context. Note that we don't get the right %eax from ntdll either, because (a) ntdll gives us a 64-bit context anyway, and (b) we don't use NtContinue but rather NtTestAlert. That does mean we could fix it by using NtContinue and putting the %eax value into %rax, which is a bit weird but I don't know if there's a better option. This is wrong inherently, as the attached tests show, but it more saliently ends up breaking LdrInitializeThunk, because on i386 RtlUserThreadStart is called with %eax pointing to the thread procedure, and we then overwrite that with zero. -- 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 49266] New: Amazon Games installs but won't start
by WineHQ Bugzilla March 17, 2023

March 17, 2023

https://bugs.winehq.org/show_bug.cgi?id=49266 Bug ID: 49266 Summary: Amazon Games installs but won't start Product: Wine Version: 5.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Created attachment 67270 --> https://bugs.winehq.org/attachment.cgi?id=67270 Console Output (wine 5.8) Hello everyone, I download the Amazon games installer from: https://download.amazongames.com/AmazonGamesSetup.exe and got it installed with wine 5.8 - Unfortunately the application doesn't launch. Console output is attached. -- 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 21

[Bug 54168] New: kernel32:console - test_wait() sometimes fails on Windows 8+
by WineHQ Bugzilla March 17, 2023

March 17, 2023

https://bugs.winehq.org/show_bug.cgi?id=54168 Bug ID: 54168 Summary: kernel32:console - test_wait() sometimes fails on Windows 8+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:console - test_wait() sometimes fails on Windows 8+: console.c:1198: Test failed: WaitForSingleObject returned 0 console.c:1200: Test failed: WaitForSingleObject returned 0 console.c:1202: Test failed: WaitForSingleObject returned 0 console.c:1204: Test failed: WaitForSingleObject returned 0 console.c:1206: Test failed: WaitForSingleObject returned 0 console.c:1208: Test failed: NtWaitForSingleObject returned 0 console.c:1211: Test failed: NtWaitForSingleObject returned 0 See https://test.winehq.org/data/patterns.html#kernel32:console This happens a bit less that twice per month. -- 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