July 2022 - Wine-bugs - list.winehq.org

[Bug 52352] New: Impossible completing the installation of YI Home
by WineHQ Bugzilla 22 Mar '24

22 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=52352 Bug ID: 52352 Summary: Impossible completing the installation of YI Home Product: Wine Version: 6.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: s.magrini(a)tiscali.it Distribution: --- Created attachment 71528 --> https://bugs.winehq.org/attachment.cgi?id=71528 Error log After launching the installation by means of the command: wine YIHomePCClientIntl_download_1.0.0.2.exe the installation starts correctly but, after asking some questions, it stops with the attached log. -- 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 7

[Bug 48085] New: Wine error trying to install Mono after a version update
by WineHQ Bugzilla 22 Mar '24

22 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=48085 Bug ID: 48085 Summary: Wine error trying to install Mono after a version update Product: Wine Version: 4.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ronen.rozner(a)gmail.com Distribution: --- Created attachment 65637 --> https://bugs.winehq.org/attachment.cgi?id=65637 Backtrace file It started after an update a few versions ago (4.xx branch, currently running 4.19). When launching an application, wineconfig will initially run, prompting to update Mono. Then it will prompt an error (see trace). The Win application runs normally, so I guess it might not be a severe bug. -- 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 15

[Bug 40613] New: WhatsApp Desktop application not working
by wine-bugs＠winehq.org 22 Mar '24

22 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=40613 Bug ID: 40613 Summary: WhatsApp Desktop application not working Product: Wine Version: 1.9.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: sh.yaron(a)gmail.com Distribution: --- Created attachment 54470 --> https://bugs.winehq.org/attachment.cgi?id=54470 Stack trace as appears on cli WhatsApp for Windows Desktop was released and I tried to install it. Apparently it requires Windows 8 and greater, I've set it correctly in Winecfg. Trying to run the WhatsApp installation (ver 0.2.684) renders the error in the attached file. -- 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 80

[Bug 29523] New: CDBurnerXP hangs on right-clicking empty space in the file browser
by wine-bugs＠winehq.org 22 Mar '24

22 Mar '24

http://bugs.winehq.org/show_bug.cgi?id=29523 Bug #: 29523 Summary: CDBurnerXP hangs on right-clicking empty space in the file browser Product: Wine Version: 1.3.36 Platform: x86-64 URL: http://cdburnerxp.se/download?more-options OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Classification: Unclassified Created attachment 38233 --> http://bugs.winehq.org/attachment.cgi?id=38233 Terminal output Right-clicking in an empty section of the file browser causes CDBurnerXP to become unresponsive. On Windows, this brings up a context menu. Steps to reproduce: 1. winetricks dotnet20 2. Install and run CDBurnerXP 3. Choose "data disc" from the main menu 4. Right-click in some empty space within the file browser (top-right section) The problem is also present in 1.2. -- 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 13

[Bug 52401] New: Improper synchronization in sock_recv/sock_send leads to arbitrary reordering of completion of I/O requests
by WineHQ Bugzilla 21 Mar '24

21 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=52401 Bug ID: 52401 Summary: Improper synchronization in sock_recv/sock_send leads to arbitrary reordering of completion of I/O requests Product: Wine Version: 7.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com Distribution: --- The sock_recv function (dlls/ntdll/unix/socket.c) issues a 'recv_socket' call to the server to complete the I/O request. Prior to calling the server, the function attempts to serve the I/O request locally first by calling try_recv(). The consequence is that there are two types of asynchronous I/O request (hereinafter "Async") sent to the server: 1. Eager: try_recv() call has succeeded before 'recv_socket'. There is no more I/O to be done. 2. Deferred: the request is still pending. When the server senses an incoming packet, async_recv_proc() (in client side) will be called to complete the I/O. The problem is that eager Asyncs are _not_ prioritized before deferred Asyncs. Therefore, deferred Asyncs may be completed before eagar Asyncs. The following scenario illustrates the problem: 1. The socket's incoming buffer is initially empty. 2. Client: The application calls WSARecv(). In sock_recv(), try_recv() fails with STATUS_DEVICE_NOT_READY; therefore, a deferred Async is queued to the server. WSARecv() returns with error ERROR_IO_PENDING. 3. The socket receives packet [A] in the meantime. The socket's incoming buffer is no longer empty. 4. Client: The application calls WSARecv() again. In sock_recv(), try_recv() succeeds with packet [A]; therefore, an eager Async is queued to the server. 5. The socket receives packet [B] in the meantime. 6. Server: the poll() loop detects this, and calls async_wake_up( &sock->read_q, status ). This causes APC_ASYNC_IO for deferred Async to be called to the client process. 6. Client: While still in the second sock_recv(), the client does wait_async() on the returned wait handle. This causes the APC_ASYNC_IO (a system APC) to be dequeued. 7. Client (select loop): The client does a server select call. This returns STATUS_KERNEL_APC with APC_ASYNC_IO. The client calls try_recv() (from async_recv_proc), which succeeds with packet [B]. The client process completes the deferred Async with this packet. 8. Client (select loop): The client re-issues the select call after the APC. 8. Server: the wait on the async wait handle is satisfied, causing async_satisified() to be called. This in turn calls async_set_result(), which completes the eager Async (with packet [A]). 9. Client: The client exits sock_recv() and in turn WSARecv(), which reports immediate success. (Ditto for sock_send and other similar asynchronous I/O requests.) If the application uses a completion port, it will observe the deferred Async first, and the eager Async second. The deferred Async carries packet [B], while the eager Async carriers packet [A]. This results in the application receiving the packets in the wrong order. -- Three possible solutions comes to mind: 1. Replace the call to try_recv()/try_send() in sock_recv()/sock_send() with STATUS_DEVICE_NOT_READY. This may slightly reduce performance, since it always defers all I/O requests and forces them to go through the poll() loop. 2. Make async_handoff() immediately call async_set_result() if the status and data are already set (i.e. the I/O has completed synchronously). Since this affects other asynchronous operations as well, I'm not sure this approach is semantically correct. 3. Prioritize immediately satiable async wait handles _before_ system APCs when waiting for objects. This approach too changes semantics, and appears much uglier than other solutions. -- 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 14

[Bug 49978] New: OpenGL Extensions Viewer 2.33 crashes on start up
by WineHQ Bugzilla 20 Mar '24

20 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=49978 Bug ID: 49978 Summary: OpenGL Extensions Viewer 2.33 crashes on start up Product: Wine Version: 5.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- 00a8:fixme:wgl:X11DRV_wglChoosePixelFormatARB unused pfAttribFList 00a8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute 00a8:fixme:wbemprox:wbem_locator_ConnectServer unsupported flags 00a8:fixme:wbemprox:client_security_SetBlanket 7BF96CA4, 001AB3F0, 10, 0, (null), 3, 3, 00000000, 0x00000000 00a8:fixme:wbemprox:client_security_Release 7BF96CA4 00a8:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 00a8:fixme:wgl:X11DRV_wglChoosePixelFormatARB unused pfAttribFList 00a8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute 00a8:fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2009 WGL Attribute 00a8:fixme:wbemprox:wbem_locator_ConnectServer unsupported flags 00a8:fixme:wbemprox:client_security_SetBlanket 7BF96CA4, 001AAC98, 10, 0, (null), 3, 3, 00000000, 0x00000000 00a8:fixme:wbemprox:client_security_Release 7BF96CA4 00a8:err:richedit:CharAttr unknown font 3 Unhandled exception: page fault on read access to 0x0000000f in 32-bit code (0x0040612f). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:0040612f ESP:0031eb40 EBP:0031eb7c EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000007 EBX:053f7f24 ECX:053f7c50 EDX:00000001 ESI:053f7c50 EDI:7e942260 Stack dump: 0x0031eb40: 053f7c50 00000143 0040687d 485308ef 0x0031eb50: 053f7e74 053f7c50 00447020 00000000 0x0031eb60: 0041bf9f 053ffea8 0273a61c 053feec0 0x0031eb70: 0031eba8 00442146 00000001 0031ebb4 0x0031eb80: 00406b2e 00000000 00000000 48530827 0x0031eb90: 00000000 00000110 0001014e 00447020 Backtrace: =>0 0x0040612f EntryPoint+0xffffffff() in glview (0x0031eb7c) 1 0x00406b2e EntryPoint+0xffffffff() in glview (0x0031ebb4) 2 0x0040f42e EntryPoint+0xffffffff() in glview (0x0031ebe8) -- 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 11

[Bug 36547] New: 3DMark 2003 installer has no taskbar/Alt Tab representation
by wine-bugs＠winehq.org 20 Mar '24

20 Mar '24

http://bugs.winehq.org/show_bug.cgi?id=36547 Bug ID: 36547 Summary: 3DMark 2003 installer has no taskbar/Alt Tab representation Product: Wine Version: 1.7.19 Hardware: x86 URL: http://www.futuremark.com/benchmarks/legacy OS: Linux Status: UNCONFIRMED Severity: major Priority: P1 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: t.artem(a)mailcity.com Created attachment 48641 --> http://bugs.winehq.org/attachment.cgi?id=48641 Installing 3DMark03_v360_1901.exe Download and try to run 3DMark03_v360_1901.exe. 3DMark03 installer won't be registered in the Alt-Tab list, or taskbar. See the attached screenshot. -- 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 24

[Bug 49299] New: PowerToys for Windows 10 crashes on unimplemented function KERNEL32.dll.GetPackageFamilyName
by WineHQ Bugzilla 19 Mar '24

19 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=49299 Bug ID: 49299 Summary: PowerToys for Windows 10 crashes on unimplemented function KERNEL32.dll.GetPackageFamilyName Product: Wine Version: 5.9 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- The program installs, but crashes when you try to run PowerToys.exe. $ sha256sum PowerToysSetup-0.18.1-x64.msi 83b2f088f6a0ef7066ba8303ad51e2a270123fe127991486b715ac55f84da19b PowerToysSetup-0.18.1-x64.msi -- 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 39669] New: D3DERR_NOTAVAILABLE in Dishonored - Steam
by wine-bugs＠winehq.org 19 Mar '24

19 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=39669 Bug ID: 39669 Summary: D3DERR_NOTAVAILABLE in Dishonored - Steam Product: Wine Version: 1.8-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: miachm3(a)gmail.com Distribution: --- Dishonored crashes at start with Steam Launcher: 1º Install Steam. 2º Install Dishonored from Steam. 3º Launch, not additional options required. Anothers D3X9 games works as well. -- 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 16

[Bug 52832] New: Regression: Crysis 3 crashes at startup
by WineHQ Bugzilla 17 Mar '24

17 Mar '24

https://bugs.winehq.org/show_bug.cgi?id=52832 Bug ID: 52832 Summary: Regression: Crysis 3 crashes at startup Product: Wine Version: 7.4 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: svyatpro(a)gmail.com Crysis 3 and other heavy D3D applications crashes at startup on Windows 32bit after this commit: https://github.com/wine-mirror/wine/commit/24432a24d5e922cbd824b0af8f7b0c66… Works before this commit without issues. -- 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 10