wine-bugs November 2022

wine-bugs@winehq.org

1 participants
3243 discussions

[Bug 50136] New: allow to disable wine's vulkan loader/driver
by WineHQ Bugzilla 18 Mar '23

18 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=50136 Bug ID: 50136 Summary: allow to disable wine's vulkan loader/driver Product: Wine Version: 5.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: xantares09(a)hotmail.com Distribution: --- I'm trying to run mesa's software vulkan renderer driver with wine. This means I want to use vulkan's icd loader and mesa's renderer libs I built (outside of wine): libvulkan-1.dll libvulkan_lvp.dll Unfortunately, building wine with --disable-vulkan does not seem to disable its loader, it only disables the driver: $ VK_ICD_FILENAMES=lvp_icd.x86_64.json wine vkcubepp.exe 0064:err:vulkan:get_vulkan_driver Wine was built without Vulkan support. Is there a way to disable the loader too ? -- 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 48112] New: The tests trigger heap and loader critical section lockups
by WineHQ Bugzilla 18 Mar '23

18 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=48112 Bug ID: 48112 Summary: The tests trigger heap and loader critical section lockups Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The log of *some* WineTest runs contains critical section errors like the following: Running: httpapi:httpapi (222 of 670) [...] 01d8:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "../../../wine/dlls/ntdll/heap. c: main process heap section" wait timed out in thread 01d8, blocked by 01d4, retrying (60 sec) 01f8:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "../../../wine/dlls/ntdll/heap. c: main process heap section" wait timed out in thread 01f8, blocked by 01d4, retrying (60 sec) 0201:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 0201, blocked by 01d4, retrying (60 sec) 01d9:err:ntdll:RtlpWaitForCriticalSection section 0x7be970a0 "../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 01d9, blocked by 0201, retrying (60 sec) 01d7:err:ntdll:RtlpWaitForCriticalSection section 0x7be970a0 "../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 01d7, blocked by 0201, retrying (60 sec) 01f7:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 01f7, blocked by 01d4, retrying (60 sec) 01d8:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 01d8, blocked by 01d4, retrying (60 sec) 01f8:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 01f8, blocked by 01d4, retrying (60 sec) 0201:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 0201, blocked by 01d4, retrying (60 sec) 01d9:err:ntdll:RtlpWaitForCriticalSection section 0x7be970a0 "../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 01d9, blocked by 0201, retrying (60 sec) 01d7:err:ntdll:RtlpWaitForCriticalSection section 0x7be970a0 "../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 01d7, blocked by 0201, retrying (60 sec) Running: ieframe:ie (223 of 670) Running: ieframe:intshcut (224 of 670) 01dc:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 01dc, blocked by 01d4, retrying (60 sec) 01da:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 01da, blocked by 01d4, retrying (60 sec) [... and more later on, all the way to...] Running: wtsapi32:wtsapi (665 of 670) 01dc:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 01dc, blocked by 01d4, retrying (60 sec) [...] It's always either the heap critical section or the loader one. Unfortunately the ERR() message does not show the process id so it's impossible to know which process got stuck. We can rule out httpapi:httpapi and the tests that ran before because the WineTest report indicates that they ran for less than 1 second: gdiplus:region:01ae done (0) in 0s gdiplus:stringformat:01b4 done (0) in 0s hid:device:01b7 done (0) in 1s hlink:browse_ctx:01b9 done (0) in 0s hlink:hlink:0118 done (0) in 0s hnetcfg:policy:0112 done (0) in 0s httpapi:httpapi:014f done (0) in 1s * The lockups seem to continue until the end of the log. So they could be happening in either WineTest.exe, or one of Wine's internal processes: explorer.exe, plugplay.exe, services.exe or winedevice.exe. * httpapi:httpapi is always where the lockups appear first. * Since the initial timeout is 5 seconds, it could in fact be caused by a test that ran up to 5 seconds before httpapi:httpapi. Unfortunately the WineTest report has a 1 second granularity so it's hard to know how many tests ran in 5 seconds. * When the lockups occur WineTest takes 2 to 5 minutes longer to run. So they slow the tests down somehow. -- 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 10570] New: Thief 2: The Metal Age - fog not working
by wine-bugs＠winehq.org 18 Mar '23

18 Mar '23

http://bugs.winehq.org/show_bug.cgi?id=10570 Summary: Thief 2: The Metal Age - fog not working Product: Wine Version: 0.9.49. Platform: Other URL: http://www.thief-thecircle.com/media/demos/ OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: a.hurst(a)shef.ac.uk In a notoriously foggy level (Life of The Party), the fog doesn't work. Card is an nvidia GeForce 6200, with latest nvidia-driver. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 41

[Bug 46169] New: Zabaware Reade doesn't work properly
by wine-bugs＠winehq.org 18 Mar '23

18 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=46169 Bug ID: 46169 Summary: Zabaware Reade doesn't work properly Product: Wine Version: 3.20 Hardware: x86 URL: https://www.zabaware.com/download OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: luca.finizio.mgbx(a)hotmail.it Distribution: Mint Hi! I downloaded Zabaware reader from here https://www.zabaware.com/download and it works,but not as in Windows. In fact the voices are very different and very annoying to listen to. To reproduce the bug you need to download the free version of the program, then install ZabawareReaderSetup.exe. Now write a sentence and hear it both in WIndows and in Linux. You will note a big difference. -- 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 7

[Bug 44414] New: GetNamedPipeHandleState not properly implemented
by wine-bugs＠winehq.org 18 Mar '23

18 Mar '23

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 18 Mar '23

18 Mar '23

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 18 Mar '23

18 Mar '23

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 17 Mar '23

17 Mar '23

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 53975] New: d3drm:d3drm sometimes fails to create an immediate mode device in Wine
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

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 17 Mar '23

17 Mar '23

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

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