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

[Bug 53663] New: Subnautica Below Zero permanently loses focus if the active window changes
by WineHQ Bugzilla 02 Dec '22

02 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53663 Bug ID: 53663 Summary: Subnautica Below Zero permanently loses focus if the active window changes Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: achurch+wine(a)achurch.org Distribution: --- In the game Subnautica: Below Zero (version 45391), when playing in windowed mode, if the game window loses focus, the game will no longer accept mouse/keyboard input even after the window regains focus again. If the game is set to pause when in the background, it remains paused even after the window regains focus. This bug also occurs with stable Wine (7.0), but it does not occur with Proton 7.0.4 (the game properly accepts input again and unpauses when the window regains focus). -- 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 54006] New: d3d8:device - test_reset() sometimes crashes on Windows 8+
by WineHQ Bugzilla 02 Dec '22

02 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54006 Bug ID: 54006 Summary: d3d8:device - test_reset() sometimes crashes on Windows 8+ 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 d3d8:device - test_reset() sometimes crashes. There are a few failure modes that look like they are related: device.c:1967: Test failed: Failed to reset device, hr 0x88760873. device.c:1967: this is the last test seen before the exception 163c:device: unhandled exception c0000005 at 74D3CC42 and device.c:2022: Test failed: Reset failed, hr 0x88760873. device.c:2024: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:2029: Test failed: GetBackBuffer failed, hr 0x8876086c. device.c:2031: Test failed: Got hr 0. device.c:2033: Test failed: Got hr 0. device.c:2033: this is the last test seen before the exception 0b00:device: unhandled exception c0000005 at 0043032C and device.c:1747: Test failed: Reset failed, hr 0x88760873. device.c:1749: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1761: Test failed: D3DVIEWPORT->Width = 400. device.c:1762: Test failed: D3DVIEWPORT->Height = 300. device.c:1764: this is the last test seen before the exception 03c0:device: unhandled exception c0000005 at 743FA86E and device.c:1807: Test failed: Reset failed, hr 0x80070057. device.c:1809: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1835: Test failed: D3DVIEWPORT->Width = 500, expected 200. device.c:1837: Test failed: D3DVIEWPORT->Height = 400, expected 150. device.c:1840: this is the last test seen before the exception 09d8:device: unhandled exception c0000005 at 7448946E See https://test.winehq.org/data/patterns.html#d3d8:device Where: 0x88760873 == ??? 0x88760869 == D3DERR_DEVICENOTRESET 0x80070057 == E_INVALIDARG -- 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 53685] New: ntdll:rtl is broken on Windows 10 1809+ in the GitLab WineTest builds
by WineHQ Bugzilla 02 Dec '22

02 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53685 Bug ID: 53685 Summary: ntdll:rtl is broken on Windows 10 1809+ in the GitLab WineTest builds Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:rtl is broken on Windows 10 1809+ in the GitLab WineTest builds: rtl.c:2790: Running test 1 (compressed_size=10, uncompressed_size=8, status=0x00000000) rtl.c:2790: this is the last test seen before the exception 1538:rtl: unhandled exception c0000005 at 005532C0 https://test.winehq.org/data/patterns.html#ntdll:rtl The failures started on 2022-07-26 which is when the WineTest builds switched from the old build system to GitLab. A test with winetest-889fe64d9f2e.exe (built on 2022-07-25) confirms that this test still succeeds when using binaries from the old build system. -- 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 43812] New: Divinity Original Sin 2 some parts display white ingame
by wine-bugs＠winehq.org 02 Dec '22

02 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=43812 Bug ID: 43812 Summary: Divinity Original Sin 2 some parts display white ingame Product: Wine-staging Version: 2.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: holzminister(a)t-online.de CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59354 --> https://bugs.winehq.org/attachment.cgi?id=59354 log from terminal I play Divinity Original Sin 2 with the workaround described in bug https://bugs.winehq.org/show_bug.cgi?id=43660 ("winetricks xact"). With this the game works quiet well. But there is one small but annoying bug for that kinda game. When you try to read books or other papers you find ingame they only show up white and empty. Also the buff icons of the unitframes are plain white. (See screenshots). -- 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 9

[Bug 54053] New: user32:input - test_GetRawInputBuffer() gets spurious WM_INPUT on Windows and Wine
by WineHQ Bugzilla 02 Dec '22

02 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54053 Bug ID: 54053 Summary: user32:input - test_GetRawInputBuffer() gets spurious WM_INPUT on Windows and Wine 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:input - test_GetRawInputBuffer() gets spurious WM_INPUT messages on Windows and Wine: * 2022-12-01 on w7u_el (32-bit) for MR!1619 input.c:2406: Test failed: Spurious WM_INPUT messages * 2022-11-11 on w1064 (64-bit) input.c:2404: Test failed: Spurious WM_INPUT messages * 2022-08-29 on debiant (wow64) input.c:2404: Test failed: Spurious WM_INPUT messages See https://test.winehq.org/data/patterns.html#user32:input All in all there has been 12 instances on Windows (7 to 10) and 6 on Wine in the past 6 months. -- 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 54051] New: winhttp:notification gets unexpected 'reconnections' on Windows 10 1507
by WineHQ Bugzilla 02 Dec '22

02 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54051 Bug ID: 54051 Summary: winhttp:notification gets unexpected 'reconnections' on Windows 10 1507 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winhttp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com winhttp:notification gets unexpected 'reconnections' on Windows 10 1507: notification.c:117: Test failed: 1555: expected status 0x10 got 0x1 notification.c:1701: Test failed: data too short notification.c:117: Test failed: 1555: expected status 0x10 got 0x2 notification.c:117: Test failed: 1555: expected status 0x10 got 0x4 notification.c:117: Test failed: 1555: expected status 0x10 got 0x4 notification.c:117: Test failed: 1555: expected status 0x10 got 0x8 notification.c:117: Test failed: 1584: expected status 0x20000 got 0x200000 winhttp:notification:0e58 done (258) in 120s 527B See https://test.winehq.org/data/patterns.html#winhttp:notification Where: 0x1 == WINHTTP_CALLBACK_STATUS_RESOLVING_NAME 0x2 == WINHTTP_CALLBACK_STATUS_NAME_RESOLVED 0x4 == WINHTTP_CALLBACK_STATUS_CONNECTING_TO_SERVER 0x8 == WINHTTP_CALLBACK_STATUS_CONNECTED_TO_SERVER 0x10 == WINHTTP_CALLBACK_STATUS_SENDING_REQUEST 0x20000 == WINHTTP_CALLBACK_STATUS_HEADERS_AVAILABLE 0x200000 == WINHTTP_CALLBACK_STATUS_REQUEST_ERROR While the reconnection messages are specific to Windows 10 1507, the request error (0x200000) is not. The timeout is probably related to the latter and may be a separate issue. Note also that winhttp:notification gets timeouts in many other cases. -- 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 54048] New: Opera Neon just displays a black screen and hangs on connecting
by WineHQ Bugzilla 02 Dec '22

02 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54048 Bug ID: 54048 Summary: Opera Neon just displays a black screen and hangs on connecting Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Created attachment 73604 --> https://bugs.winehq.org/attachment.cgi?id=73604 Console output (wine-7.22 on Slackware64/Multilib) Hello everyone, When I was revisting 42997 I downloaded the installer from https://get.geo.opera.com/.private/OperaNeonSetup.exe?utm_tryagain=yes&dl_t… sha256sum OperaNeonSetup.exe 76d998a47c34e89447eb6ca177ea3d563abbf3c1153184f7c47923d0249abd00 OperaNeonSetup.exe The application in a fresh prefix seems to be fine but no feedback is given and neon.exe resides in /home/mwagner/WineApps/OperaNeon/drive_c/users/mwagner/AppData/Local/Opera Software/Opera Neon/Application for me. As suggested in 42997 I ran it as follows. wine neon.exe 2&>/home/mwagner/Desktop/OperaNeonConsole.txt --no-sandbox The screen turns dark and a message "Connecting" is in the lower left corner so there seems to be something happening. -- 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 53902] New: wine install Genshin fails in Ubuntu20.04 Docker
by WineHQ Bugzilla 01 Dec '22

01 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53902 Bug ID: 53902 Summary: wine install Genshin fails in Ubuntu20.04 Docker Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: guangli.li(a)intel.com Distribution: --- Created attachment 73445 --> https://bugs.winehq.org/attachment.cgi?id=73445 the needed memory is 304MB, the avaiable memory is 1. start a ubuntu 20.04 docker with --priviledged, following instruction to install wine 7.0 stable 2. download genshin launcher: 3. install dxvk 1.10.3 from: https://github.com/doitsujin/dxvk/releases/download/v1.10.3/dxvk-1.10.3.tar… 4. wine launcher.exe, it will show memory insufficient. logs as below: guangli(a)247ca492a6aa:/data$ wine yuanshen_setup_20220811050610.exe need space: 307347065 archive size: 97504766 compressDatapos: 26339848 read Config I18nNameMap=QMap(("de-de", "")("en-us", "")("es-es", "")("fr-fr", "")("id-id", "")("it-it", "")("ja-jp", "")("ko-kr", "")("pt-pt", "")( "ru-ru", "")("th-th", "")("tr-tr", "")("vi-vn", "")("zh-cn", "??")("zh-tw", "")) ProductName="??" InstallerSingleId="miHoYo.com_installer_yuanshen" I nstallAppendPath="Genshin Impact" LauncherExeName="launcher.exe" AppSingleId="miHoYo.com_launcher_yuanshen" Publisher="miHoYo Co.,Ltd" WebSiteUrl="ht tps://ys.mihoyo.com/main/" ProtocolUrl="https://ys.mihoyo.com/launcher/18/{lang}/agreement?api_url=https%3A%2F%2Fap…" Versio n="2.19.0.0" EnvValue="prod" Preview=false RequestKey="eYd89JmJ" AppId="18" CPS="mihoyo" Channel="1" SubChannel="1" ClusterLabel="" BuildSha="1b0cc5b 8jK3rv6zy" my docker memory info: is larger than needed. Filesystem Size Used Avail Use% Mounted on overlay 1.8T 1.3T 459G 74% / -- 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 54046] New: wiaservc:wia sometimes times out on Windows 10 21H1 & 22H2
by WineHQ Bugzilla 01 Dec '22

01 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54046 Bug ID: 54046 Summary: wiaservc:wia sometimes times out on Windows 10 21H1 & 22H2 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wia Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wiaservc:wia sometimes times out on Windows 10 21H1 & 22H2: wiaservc:wia:1204 done (258) in 120s See https://test.winehq.org/data/patterns.html#wiaservc:wia This failure is pretty rare and since there is no trace whatsoever it's unclear where the timeout occurs. Normally the test runs in "0 seconds" so it's not a speed issue. Note: On Windows 11 it crashes instead of timing out. These two issues may well be related (memory corruption?). -- 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 47874] New: kernel32:debugger sometimes fails getting EXCEPTION_DEBUG_EVENT
by WineHQ Bugzilla 01 Dec '22

01 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=47874 Bug ID: 47874 Summary: kernel32:debugger sometimes fails getting EXCEPTION_DEBUG_EVENT Product: Wine Version: 4.17 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:debugger sometimes gets the following failure: debugger.c:1424: Test failed: dwDebugEventCode = 1 https://test.winehq.org/data/tests/kernel32:debugger.html This value seems to correspond to EXCEPTION_DEBUG_EVENT. This failure has been seen on the wxppro and w2003std TestBot VMs and on the fg-win7u64 family of VMware VMs. It also happened on the cw1-hd6800-t64 Windows 8.1 real hardware machine (which also means it happens in both 32 and 64 bit tests). However it never happened on the Windows 10 VMs so it may be a bug in older Windows versions. -- 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