March 2020 - Wine-Bugs - list.winehq.org

[Bug 44089] New: Strider crashes after loading screen
by wine-bugs＠winehq.org April 25, 2020

April 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=44089 Bug ID: 44089 Summary: Strider crashes after loading screen Product: Wine Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: strider(a)strycore.com Distribution: --- Created attachment 59805 --> https://bugs.winehq.org/attachment.cgi?id=59805 backtrace of the crash While the main menu works fine, when starting a game, the game crashes. This is a regression that started in Wine Staging 2.16, when the deferred context patch (https://dev.wine-staging.com/patches/181/) was introduced. I had a build of Wine Staging 2.15 with that patch enabled and I noticed crashes starting with that build and onward until the latest tested, Staging 2.21. -- 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 48612] New: Left mouse button doesn't work in Mass Effect Andromeda.
by WineHQ Bugzilla April 25, 2020

April 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=48612 Bug ID: 48612 Summary: Left mouse button doesn't work in Mass Effect Andromeda. Product: Wine-staging Version: 5.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mail.aermakov(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Left mouse button doesn't work(can't fire) in game Mass Effect Andromeda in wine+staging 5.1. But wine 5.1 without staging patches works with mouse fine. -- 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 48089] New: Origin update hangs with Esync enabled
by WineHQ Bugzilla April 25, 2020

April 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=48089 Bug ID: 48089 Summary: Origin update hangs with Esync enabled Product: Wine-staging Version: 4.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 65647 --> https://bugs.winehq.org/attachment.cgi?id=65647 +server When Origin has an update available to be installed and Esync is enabled by passing WINEESYNC=1 envar, the updater hangs and never finishes. Disabling Esync solves the issue and allows Origin to complete the update. Attaching +server log. How to reproduce: 1) Create a prefix (64-bit will do) 2) Install DXVK using winetricks (app doesn't work correctly without it) 3) Add an override for OriginThinSetupInternal.exe and set it to disabled so that the app doesn't update during installation and a backup could be made for testing purposes. 4) Install an older version of Origin (you can use this link https://lutris.nyc3.cdn.digitaloceanspaces.com/games/origin/OriginSetup.exe) 5) Kill all processes in the prefix and remove override for OriginThinSetupInternal.exe 6) Run Origin.exe with WINEESYNC=1 envar passed on. Behavior with Esync disabled: Update window appears, then closes after a while, reopens and finishes the update. Behavior with Esync enabled: Update window appears, then closes but never reopens. The update hangs and never finishes. During the test, regular wine-staging build was used, but I've also tried it with a custom build that ports Fsync from Proton to Wine and it has the same issue when Fsync is in use (which it indicated in the logs). -- 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 46790] New: Witcher 3 hangs shortly after launch; may show ' press space to skip'
by wine-bugs＠winehq.org April 25, 2020

April 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=46790 Bug ID: 46790 Summary: Witcher 3 hangs shortly after launch; may show 'press space to skip' Product: Wine-staging Version: 4.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: riddervancocagne(a)hotmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 63809 --> https://bugs.winehq.org/attachment.cgi?id=63809 Zip file containing api trace, partial console output and Witcher 3 crash report. If The Witcher 3 is launched using Wine 4.3 Staging, it will grind to a halt almost immediately. This is no ordinary black screen, as the game often does display the text 'Press space to skip'. Pressing space has no effect, however. I have also tried running the game on Wine 3.03 Stable, Wine 4.0 Stable and Wine 4.3 Devel. All three variants launch and run the game. Attached: partial console output, api trace and Witcher 3 crash report generated by the game itself. -- 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 12

[Bug 48757] New: Multiple Direct3D 7 games crash with Wine Staging 5.4
by WineHQ Bugzilla April 25, 2020

April 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=48757 Bug ID: 48757 Summary: Multiple Direct3D 7 games crash with Wine Staging 5.4 Product: Wine Version: 5.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winter.snowfall(a)protonmail.com Distribution: --- Created attachment 66664 --> https://bugs.winehq.org/attachment.cgi?id=66664 Crash log obtained after running Blood 2 Multiple Direct3D 7 (and possibly 6) games crash on startup with the following common/similar trace after upgrading Wine Staging from 5.3 to 5.4: =>0 0x7d579dc2 wined3d_texture_release_dc+0x61a2() in wined3d (0x0032dae8) 1 0x7d50fa83 wined3d_check_device_format+0x52() in wined3d (0x0032db48) Among the affected games I can mention (the list is not exhaustive): - Blood 2 - The Chosen - Legacy Of Kain - Soul Reaver - GTA2 - Emperor - Battle For Dune - Battle Realms - Dungeon Keeper 2 - Praetorians - Re-Volt - Sacrifice I've tested on a clean prefix and on multiple machines to confirm the behaviour, on both intel and nvidia graphics hardware. Unfortunately I'm not knowledgeable enough to do a bisect, but I'm hoping it will be easy enough to track down what has caused this issue. If you need any other details please do let me know. -- 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 48833] New: Battlefield 2: user32-rawinput-mouse causes mouse stuttering
by WineHQ Bugzilla April 25, 2020

April 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=48833 Bug ID: 48833 Summary: Battlefield 2: user32-rawinput-mouse causes mouse stuttering Product: Wine-staging Version: 5.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ealex95(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 66750 --> https://bugs.winehq.org/attachment.cgi?id=66750 wine log when running battlefield 2 with the rawinput patches Hello, When using wine-staging patches I get stutters when turning with the mouse in Battlefield 2. The problem goes away if I compile wine with the wine-staging patches excluding the following: user32-rawinput-mouse user32-rawinput-mouse-experimental user32-rawinput-nolegacy user32-rawinput-hid I made two video showing this issue. Please ignore the video titles, they were made before I discovered the cause. I did retest with the latest wine and wine-staging masters before posting this bug report. Battlefield 2 without the mouse rawinput patches (walking is smooth, turning is smooth): https://www.youtube.com/watch?v=o36Rkb5LzEY Battlefield 2 with the mouse rawinput patches (walking is smooth, turning is stuttering): https://www.youtube.com/watch?v=winvJdHEUCA 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 16

[Bug 48824] New: build error - xaudio2_7/xact_dll.c:1192:9: error: case label does not reduce to an integer constant
by WineHQ Bugzilla April 25, 2020

April 25, 2020

https://bugs.winehq.org/show_bug.cgi?id=48824 Bug ID: 48824 Summary: build error - xaudio2_7/xact_dll.c:1192:9: error: case label does not reduce to an integer constant Product: Wine-staging Version: 5.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Building on Debian Buster, I ran into the following error with 5.4-staging using my regular build scripts. ccache gcc -m64 -c -o xact_dll.o /mnt/gaming/applications/wine/git/dlls/xactengine3_6/../xaudio2_7/xact_dll.c -I. \ -I/mnt/gaming/applications/wine/git/dlls/xactengine3_6 \ -I/mnt/gaming/applications/wine/git/dlls/xactengine3_6/../xaudio2_7 -I../../include \ -I/mnt/gaming/applications/wine/git/include -D__WINESRC__ -DXACT3_VER=0x0306 -D_REENTRANT -fPIC \ -Wall -pipe -fcf-protection=none -fno-stack-protector -fno-strict-aliasing \ -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Wno-packed-not-aligned \ -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla \ -Wwrite-strings -Wpointer-arith -Wlogical-op -gdwarf-2 -gstrict-dwarf -g -O0 /mnt/gaming/applications/wine/git/dlls/xactengine3_0/../xaudio2_7/xact_dll.c: In function ‘unwrap_notificationdesc’: /mnt/gaming/applications/wine/git/dlls/xactengine3_0/../xaudio2_7/xact_dll.c:1192:9: error: case label does not reduce to an integer constant case (int)XACTNOTIFICATIONTYPE_GLOBALVARIABLECHANGED: ^~~~ /mnt/gaming/applications/wine/git/dlls/xactengine3_0/../xaudio2_7/xact_dll.c:1193:9: error: case label does not reduce to an integer constant case (int)XACTNOTIFICATIONTYPE_GUICONNECTED: ^~~~ /mnt/gaming/applications/wine/git/dlls/xactengine3_0/../xaudio2_7/xact_dll.c:1194:9: error: case label does not reduce to an integer constant case (int)XACTNOTIFICATIONTYPE_GUIDISCONNECTED: ^~~~ /mnt/gaming/applications/wine/git/dlls/xactengine3_0/../xaudio2_7/xact_dll.c:1198:9: error: case label does not reduce to an integer constant case (int)XACTNOTIFICATIONTYPE_CUEPREPARED: ^~~~ /mnt/gaming/applications/wine/git/dlls/xactengine3_0/../xaudio2_7/xact_dll.c:1199:9: error: case label does not reduce to an integer constant case (int)XACTNOTIFICATIONTYPE_CUEPLAY: ^~~~ ... Build of shared WoW64 failed. I don't have time to investigate right now, but I was able to build fine if I avoided the xactengine-initial patch set. $ ./patchinstall.sh DESTDIR=../../git --all -W xactengine-initial -- 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 16

[Bug 47365] New: jittering caused by mouse input in vkquake
by wine-bugs＠winehq.org April 24, 2020

April 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=47365 Bug ID: 47365 Summary: jittering caused by mouse input in vkquake Product: Wine Version: 4.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tempel.julian(a)gmail.com Distribution: --- Created attachment 64704 --> https://bugs.winehq.org/attachment.cgi?id=64704 wine log In vkquake, enable vsync (and set an fps limit well above refresh rate via "host_maxfps" command if your using a refreshrate of greater than 60Hz, as the game caps to 72fps by default), start a new game and pan the camera via the keyboard's arrow keys. It should be absolutely smooth. Now, pan the camera by moving the mouse instead -> there is jitter. After alt + Tab to the desktop and back into the game, this jitter usually is gone. Still, it shouldn't occur in the first place, as it doesn't happen on Windows. I made sure this isn't a driver issue by checking with both modesetting and xf86-video-amdgpu DDX and also on xwayland. In xwayland, the issue is less distinct, but still noticeable. Happens with both wine 4.9, wine-staging 4.9 and my custom 4.10 build (4.10 not yet in Arch repository). Get vkquake here: https://github.com/Novum/vkQuake/releases/download/1.01.0/vkquake-1.01.0_wi… You also need the game's free demo content, copy the "id1" folder into the main folder. Since the official servers usually are a mess, you can get it from here as well: https://bugs.freedesktop.org/attachment.cgi?id=143128 -- 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 6

[Bug 46633] New: unimplemented function: kernel32.dll.startthreadpoolio
by wine-bugs＠winehq.org April 24, 2020

April 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=46633 Bug ID: 46633 Summary: unimplemented function: kernel32.dll.startthreadpoolio Product: Wine Version: 4.0-rc2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: mushipao(a)gmail.com Distribution: --- Created attachment 63542 --> https://bugs.winehq.org/attachment.cgi?id=63542 backtrace of exception 3rd party, proprietary software errors out in Wine. 0157:fixme:thread:CreateThreadpoolIo (0x64, 0x42fca0, 0x5fc2a0, (nil)): stub wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Unimplemented function KERNEL32.dll.StartThreadpoolIo called at address 0x7bc51e39 (thread 0157), starting debugger... -- 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 18

[Bug 48817] New: Module_InitDLL fails if LDR_MODULE.Flags was modified
by WineHQ Bugzilla April 24, 2020

April 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=48817 Bug ID: 48817 Summary: Module_InitDLL fails if LDR_MODULE.Flags was modified Product: Wine Version: 5.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: qsniyg(a)mail.com Distribution: --- I've created a test case here: https://github.com/qsniyg/wine_dll_load_test. I would have made a patch to add this in wine's test suite, but it's rather complex (requiring multiple DLLs), so I'm not sure how to do this. dll1.dll depends on dll2.dll, which therefore will have its DllMain run before dll1's. dll2.dll looks for dll1's LDR_MODULE, then blanks out the Flags attribute, alongside a few others. Since MODULE_InitDLL reads the flags from dll1's now-modified LDR_MODULE, it fails to find the LDR_IMAGE_IS_DLL flag, which prevents dll1's DllMain from being run. The test case runs fine under Windows 10, but not under wine. This is used by certain code protection systems in order to confuse debuggers. -- 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 20