December 2021 - Wine-Bugs - list.winehq.org

[Bug 51500] New: ntdll:exception test_wow64_context() randomly fails on Windows
by WineHQ Bugzilla Dec. 17, 2021

Dec. 17, 2021

https://bugs.winehq.org/show_bug.cgi?id=51500 Bug ID: 51500 Summary: ntdll:exception test_wow64_context() randomly fails on Windows 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 test_wow64_context() regularly gets one of the following two failures on Windows: exception.c:4370: Test failed: cs32: ecx f6a10000 / 4EAECB33F6A10000 or exception.c:4450: Test failed: cs64: rsp not inside 64-bit stack 0000000002B7F388 / 00000000009E0000-0000000000A1FD20 It looks like at most one failure happens in a given run. They happen on Windows 8.1 to Windows 10 2009, only QEmu VMs so far. But the failures only happen about 6.9% of the time so the above data is not 100% certain yet. The tests were added in this commit: commit 9ae2b046ef2f645b122a2554cc8e32d3a3d79ccc Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Tue Jun 22 17:08:11 2021 +0200 ntdll/tests: Add more tests for Wow64 contexts. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 51282] New: Samurai Shodown Reboot 2019: low gpu usage around 5-10% and low fps around 9-20fps
by WineHQ Bugzilla Dec. 17, 2021

Dec. 17, 2021

https://bugs.winehq.org/show_bug.cgi?id=51282 Bug ID: 51282 Summary: Samurai Shodown Reboot 2019: low gpu usage around 5-10% and low fps around 9-20fps Product: Wine Version: 6.7 Hardware: x86-64 URL: https://store.steampowered.com/bundle/21032/SAMURAI_SH ODOWN_STEAM_EDITION/ OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: rezzafri(a)gmail.com Regression SHA1: c2c78a2fe0ac13e4fca7ab4c17977b65e358485c Distribution: Other Regression on commit c2c78a2fe0ac13e4fca7ab4c17977b65e358485c. normal gpu usage and fps with this commit reverted. -- 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 52187] New: wine-mono's WPF tests hang
by WineHQ Bugzilla Dec. 17, 2021

Dec. 17, 2021

https://bugs.winehq.org/show_bug.cgi?id=52187 Bug ID: 52187 Summary: wine-mono's WPF tests hang Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Distribution: --- The test WineMono.Tests.System.Windows.Media.TextFormatting.TextFormatterTest:IndentTest hangs on current Wine. It seems it gets in a loop where dwritetextanalyzer_AnalyzeLineBreakpoints requests data past the end of the range provided by the source, and the source returns 0-length text. This is our implementation of GetTextAtPosition: https://github.com/madewokherd/wpf/blob/main/src/Microsoft.DotNet.Wpf/src/D… Print statement debugging shows that the "else" path is being taken in that function, but on the dwrite side checking for a length of 0 works around the hang. Bisecting gave me this: 909f7aa7c21f82114586e98a0a9e940b13bc386a is the first bad commit commit 909f7aa7c21f82114586e98a0a9e940b13bc386a Author: Nikolay Sivov <nsivov(a)codeweavers.com> Date: Thu Dec 2 15:37:19 2021 +0300 dwrite: Use CRT allocation functions. Nothing in that commit should change the behavior. I double-checked the result, and it's consistent. I tried running with WINEDEBUG=warn+heap, both before and after the bad commit, and that didn't change the behavior or print any warnings while the test process was running. Leaving component unknown because it's not clear to me that dwrite is doing anything wrong. -- 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 18

[Bug 52165] New: mfplat:mfplat has failures in test_sample_allocator_d3d12() on Windows 10 1709
by WineHQ Bugzilla Dec. 17, 2021

Dec. 17, 2021

https://bugs.winehq.org/show_bug.cgi?id=52165 Bug ID: 52165 Summary: mfplat:mfplat has failures in test_sample_allocator_d3d12() on Windows 10 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mfplat:mfplat has failures in test_sample_allocator_d3d12() on Windows 10 1709: mfplat.c:7365: Test failed: Failed to set a device, hr 0x80070057. mfplat.c:7383: Test failed: Unexpected hr 0x80041000. https://test.winehq.org/data/patterns.html#mfplat:mfplat The failures happen on cw-rx460 and the TestBot's w1064v1709 VM. cw-gtx560 is also impacted but it normally gets stuck before reaching this test (see bug 52164). The failures started with the commit that introduced this set of tests: commit f03933fbb73152c7a54383fba411a611af7aaa55 Author: Nikolay Sivov <nsivov(a)codeweavers.com> Date: Sat Nov 27 00:03:59 2021 +0300 mfplat/tests: Add some tests for video sample allocator using D3D12 device. Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 52112] New: Final Fantasy XIV failing to boot
by WineHQ Bugzilla Dec. 17, 2021

Dec. 17, 2021

https://bugs.winehq.org/show_bug.cgi?id=52112 Bug ID: 52112 Summary: Final Fantasy XIV failing to boot Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: meowsuke(a)gmail.com Distribution: --- Created attachment 71139 --> https://bugs.winehq.org/attachment.cgi?id=71139 terminal output ubuntu 20.04.3 lts, wine staging 6.22. the launcher runs, but the game will not launch. the game ran previously (maybe under 6.20). i wasn't able to do a regression test because of errors i ran into while compiling wine. the game has to be run under staging because it needs the wine version to be hidden. -- 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 51910] New: Keyboard Input Partially Broken
by WineHQ Bugzilla Dec. 17, 2021

Dec. 17, 2021

https://bugs.winehq.org/show_bug.cgi?id=51910 Bug ID: 51910 Summary: Keyboard Input Partially Broken Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: escomk3(a)hotmail.com Distribution: --- Here's an interesting one. After 71ecc179aab [1], some keyboard keys no longer (completely) work as they should in FINAL FANTASY XI Online. For example, the arrow keys no longer navigate through menus, while they do still move the cursor in chat. Other keys that have become partially "mute" include: - right ctrl - insert - delete - home - end - page up - page down - / (numpad) - Enter (numpad) 1. https://source.winehq.org/git/wine.git/commit/71ecc179aab7ad103e06b52ea76ae… -- 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 9

[Bug 51745] New: Xbox Controller no longer recognised
by WineHQ Bugzilla Dec. 17, 2021

Dec. 17, 2021

https://bugs.winehq.org/show_bug.cgi?id=51745 Bug ID: 51745 Summary: Xbox Controller no longer recognised Product: Wine Version: 6.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: xinput Assignee: wine-bugs(a)winehq.org Reporter: lemonzest(a)gmail.com Distribution: --- Created attachment 70631 --> https://bugs.winehq.org/attachment.cgi?id=70631 XinputTest.exe Test Program for Xinput Controllers Hi I just updated to WineHQ-Devel 6.17 and Xinput/Xbox controllers (Not sure about others as don't own any) are no longer detected in games I have tried Dragon's Dogma, Dead Cells and a couple of others and they no longer react to Gamepad inputs and XinputTest.exe says its disconnected. rolling back to WineHQ-Devel 6.16 all is working. I am on Fedora 34 with a PDP Afterglow XBox One Controller which in many previous versions worked correctly. -- 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 51521] New: Installer of Tencent meeting crashes when using enter key in the license agreement screen.
by WineHQ Bugzilla Dec. 17, 2021

Dec. 17, 2021

https://bugs.winehq.org/show_bug.cgi?id=51521 Bug ID: 51521 Summary: Installer of Tencent meeting crashes when using enter key in the license agreement screen. Product: Wine Version: 6.13 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: richedit Assignee: wine-bugs(a)winehq.org Reporter: jactry92(a)gmail.com Distribution: --- Created attachment 70361 --> https://bugs.winehq.org/attachment.cgi?id=70361 a +richedit log. Steps to reproduce: 1. `wine TencentMeeting_0300000000_2.15.4.400.publish.exe`. 2. Pass the 'return' key for selecting a language. 3. Pass the 'return' key in the license agreement screen. Then it will crash. Wine version: wine-6.13-114-ga5f787ac445 MD5: 13359c85cb244a587e703111c80080ec TencentMeeting_0300000000_2.15.4.400.publish.exe -- 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 51479] New: Сreating a prefix gives "wine: Unhandled page fault on write access ..."
by WineHQ Bugzilla Dec. 17, 2021

Dec. 17, 2021

https://bugs.winehq.org/show_bug.cgi?id=51479 Bug ID: 51479 Summary: Сreating a prefix gives "wine: Unhandled page fault on write access ..." Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lvb.crd(a)protonmail.com CC: rbernon(a)codeweavers.com Regression SHA1: b065daa600e858823944f996144ed233065da7fd Distribution: ArchLinux When closing winecfg after creating a prefix (I mean run winecfg without prefix), now every time this message appears in the terminal: wine: Unhandled page fault on write access to 0000000000000000 at address 00007F6E5819F9BB (thread 00d0), starting debugger... Not sure if this is causing any negative consequences, and I have not found any similar descriptions among the recent issues. Bisecting tests indicate that it started after this patch series: https://github.com/wine-mirror/wine/commits/f24c8c75fe11fc4b928d3ec45e71ea7… Specific commit: b065daa600e858823944f996144ed233065da7fd bad e3b28631485a010219928a888fcc543a5bb3c61d good I am using the build environment that Archlinux provides. If possible please let me know if someone can reproduce this. Thanks. -- 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 24

[Bug 51296] New: Cogmind: Mouse cursor is a black square
by WineHQ Bugzilla Dec. 17, 2021

Dec. 17, 2021

https://bugs.winehq.org/show_bug.cgi?id=51296 Bug ID: 51296 Summary: Cogmind: Mouse cursor is a black square Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: jan.steffens(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: db2b266c57b73e1a16785213ce923b749c84400e Distribution: ArchLinux Cogmind (a 2D SDL 1.2 game) sets a custom, monochrome mouse cursor. Since Wine 6.10, this cursor is broken and displays as a black square. Cogmind Beta 10.2 Wine 6.9 (good), 6.10 (bad), 6.11 (bad) GNOME 40.2 (no difference between Xorg and Wayland) Arch Linux db2b266c57b73e1a16785213ce923b749c84400e (user32: Handle monochrome icons in CreateIcon() and CreateCursor() instead of CreateIconIndirect().) is the first bad commit. -- 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 36