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

[Bug 45732] New: Far Cry 5 Cannot Steer Land Vehicles
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=45732 Bug ID: 45732 Summary: Far Cry 5 Cannot Steer Land Vehicles Product: Wine Version: 3.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: airetamstrm(a)gmail.com Distribution: --- Created attachment 62170 --> https://bugs.winehq.org/attachment.cgi?id=62170 Screenshots of reports of this issue Environment: Arch Linux. 64-bit Wine Prefix, Wine-Staging 3.14, DXVK 0.70. winetricks: xact, xaudio, xinput, dxvk Hardware: Acer Predator Helios 500 (new laptop), i7-8750H, GTX-1070. Installation: I purchased the Steam version, that has yet to even start. DRM seems to be the culprit but I am still unsure. I got as far as UPlay displaying properly but the game will not start yet. Still working on that in a different wine prefix, I've worked around with a crack. Description: Graphics are perfect, everything seems to work. Get into land vehicles (haven't tested flying vehicles, water vehicles) and steering left or right doesn't work. Steering left/right in vehciles is by default bound to A (left) and D (right) respectively. Strafe (on foot) is the same, but it works. A strafes left, D strafes right. In the vehicle, nothing. Hop out, works. Attaching screenshots of several places this issue has been reported / "resolved". None of the listed resolutions seem to have any effect, and those reporting the issue on Wine/Linux do not list a resolution. Sites in that screencap in order: overclock.net gamingonlinux.com reddit.com/linux-gaming ubisoft forums Two of the screenshots are of the problem in Far Cry 4. Same engine FWIW, just another data point. Solutions presented: -Some people report this problem when they leave their game controllers plugged in before starting the game. I'm not sure what Far Cry 5 sees in terms of attached controllers under WINE. One of my thoughts was that WINE may be emulating something that reproduces this behavior. I tried attaching a gamepad, configured it under wine control. Nonresponsive. Lots of people complaining on the Ubi forums about that. -One individual said driving forward first allowed them to steer, not the case here. -Another said adjusting the "steering sensitivity" fixed the issue. Have messed with this extensively, no resolution. -I've also tried remapping keys, holding alt/ctrl/shift to see if something is amiss with the modifiers... nothing. WINEDEBUG="+dinput" was my first go at trying to track this down... I haven't seen useful console output yet. First bug I've filed, if I need to provide additional information I'm willing to learn. -- 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 87

[Bug 48314] New: Building wine on CentOS7 fails due to lack of libkrb5
by WineHQ Bugzilla April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=48314 Bug ID: 48314 Summary: Building wine on CentOS7 fails due to lack of libkrb5 Product: Wine Version: 5.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: oleg.kuznetsov(a)metamint.ru Distribution: --- Created attachment 66024 --> https://bugs.winehq.org/attachment.cgi?id=66024 Error during executing "time make" I'm trying to build 32 bit wine from git on CentOS7, and even though I have installed package krb5-devel, configure doesn't see it and even further: during compilation it fails on building "dlls/kerberos", while it should skip it. [user1(a)localhost wine]$ uname -r 3.10.0-1062.9.1.el7.x86_64 [user1(a)localhost ~]$ yum info krb5-devel --- snip --- Installed Packages Name : krb5-devel Arch : i686 Version : 1.15.1 Release : 37.el7_7.2 Size : 766 k Repo : installed >From repo : updates --- snip --- [user1(a)localhost wine]$ ./configure --- snip --- config.status: executing Makefile commands configure: OpenCL 32-bit development files not found, OpenCL won't be supported. configure: libhal 32-bit development files not found, no legacy dynamic device support. configure: OSS sound system found but too old (OSSv4 needed), OSS won't be supported. configure: libSDL2 32-bit development files not found, SDL2 won't be supported. configure: libFAudio 32-bit development files not found, XAudio2 won't be supported. configure: libcups 32-bit development files not found, CUPS won't be supported. configure: libkrb5 32-bit development files not found (or too old), Kerberos won't be supported. configure: libopenal 32-bit development files not found (or too old), OpenAL won't be supported. configure: vkd3d 32-bit development files not found (or too old), Direct3D 12 won't be supported. configure: Finished. Do 'make' to compile Wine. -- 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 34041] New: Skyrim (Steam) hangup on quit
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

http://bugs.winehq.org/show_bug.cgi?id=34041 Bug #: 34041 Summary: Skyrim (Steam) hangup on quit Product: Wine Version: 1.6-rc4 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: zoroaster(a)inode.at Classification: Unclassified Created attachment 45238 --> http://bugs.winehq.org/attachment.cgi?id=45238 The end of the log is where the wine process hangs Environment: MacPorts wine-devel, OSX 10.8 Everytime quitting Skyrim the Wine process does not end itself and hangs indefinitely. Only force quit does stop this Wine process. You can quit Skyrim directly after starting it without even loading or starting a game. -- 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 72

[Bug 47075] New: Cannot install LAVFilters, fails at registering DLLs
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=47075 Bug ID: 47075 Summary: Cannot install LAVFilters, fails at registering DLLs Product: Wine Version: 4.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yaomtcmail(a)gmail.com Distribution: --- Created attachment 64262 --> https://bugs.winehq.org/attachment.cgi?id=64262 Terminal output from Wine running the installer. It fails at the point of registering files: > C:\Program Files (x86)\LAV Filters\x64/LAVAudio.ax > > Unable to register the DLL/OCX: RegSvr32 failed with exit code 0x3. > > Click Retry to try again, Ignore to proceed anyway (not recommended), or Abort to cancel installation. Terminal output is attached. -- 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 47935] New: Nextiva: Logging in fails with "Client is unable to connect to the server."
by WineHQ Bugzilla April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=47935 Bug ID: 47935 Summary: Nextiva: Logging in fails with "Client is unable to connect to the server." Product: Wine Version: 4.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: iphlpapi Assignee: wine-bugs(a)winehq.org Reporter: joseph.kogut(a)gmail.com Distribution: --- Created attachment 65437 --> https://bugs.winehq.org/attachment.cgi?id=65437 Debug log When attempting to log in to the Nextiva app with a correct username and password, the app reports that it's unable to connect to the server. Wine debug log attached. Messages starting at line 63 occur after clicking "Sign In". Download link: https://www.nextiva.com/support/articles/nextiva-app-windows-setup.html Note that a paid account is required to sign in. -- 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 47049] New: boolean type defined as 'unsigned char' rather than 'char '
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=47049 Bug ID: 47049 Summary: boolean type defined as 'unsigned char' rather than 'char' Product: Wine Version: 4.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: richard(a)torproject.org Distribution: --- Probably not the end of the world, but still a difference between latest widl and midl. min-repro here: https://github.com/pospeselr/mingw-widl-bug/tree/boolean_bug Includes tlb generated by widl 4.5 and midl 8.01.0622 -- 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 46983] New: type command in cmd.exe with two files and stdout redirect, behavior is different
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=46983 Bug ID: 46983 Summary: type command in cmd.exe with two files and stdout redirect, behavior is different Product: Wine Version: 4.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: davidglanzman(a)yahoo.com Distribution: --- The type command in cmd.exe, when used with two file arguments as inputs and stdout is redirected to a file, write the filenames to the file in wine, but print the filenames to the terminal in windows. To reproduce: 1. Create a file "test.txt" with some content 2. Launch cmd.exe 3. Run the command "type test.txt test.txt > out.txt" 4. Observe that in wine, the filename "test.txt" is printed in the output file, while on Windows it appears in the terminal instead of the 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 9

[Bug 46421] New: μTorrent has square s in it's update-dialog - most likely taskdialog
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=46421 Bug ID: 46421 Summary: μTorrent has squares in it's update-dialog - most likely taskdialog Product: Wine Version: 4.0-rc3 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- See title. -- 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 14

[Bug 48077] New: UPlay fails to start : "Error at hooking API NtProtectVirtualMemory" (UPlay's hooking engine can't handle ENDBR32 instruction inserted at non-hotpatch API entries due to distro build environments '-fcf-protection')
by WineHQ Bugzilla April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=48077 Bug ID: 48077 Summary: UPlay fails to start : "Error at hooking API NtProtectVirtualMemory" (UPlay's hooking engine can't handle ENDBR32 instruction inserted at non-hotpatch API entries due to distro build environments '-fcf-protection') Product: Wine Version: 4.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: dario(a)mailo.com Distribution: --- This is related to bug 46626 and possibly bug 45199. When Wine is built with -fcf-protection flag, on my AMD CPU the latest version of Uplay throws the error message in the title. To fix the issue I modified one line in dlls/ntdll/virtual.c from: NTSTATUS WINAPI NtProtectVirtualMemory( HANDLE process, PVOID *addr_ptr, SIZE_T *size_ptr, ULONG new_prot, ULONG *old_prot ) to: NTSTATUS WINAPI DECLSPEC_HOTPATCH NtProtectVirtualMemory( HANDLE process, PVOID *addr_ptr, SIZE_T *size_ptr, ULONG new_prot, ULONG *old_prot ) -- 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 47709] New: Zoom Edit&Share 5.0.0.0: installer crashes on versions 3 and 4 of wine
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=47709 Bug ID: 47709 Summary: Zoom Edit&Share 5.0.0.0: installer crashes on versions 3 and 4 of wine Product: Wine Version: 4.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sven.a.jonsson(a)bahnhof.se Distribution: --- Created attachment 65181 --> https://bugs.winehq.org/attachment.cgi?id=65181 Terminal capture of fail Every time I attempt to install Zoom Edit&Share on wine, with any wine version 3 or 4. I'm currently running Gentoo, but I have seen the same error running Void linux. I have installed and executed it fine on wine 2. The crash appears when I press the "Install" button in the "Ready to Install the Program" window. The program can be downloaded from here "https://www.zoom.co.jp/sites/default/files/products/downloads/software/E_Ed…" The sha1sum of the unpacked exe is ❯ sha1sum Edit\&Share\ 5.0.0.0\ Setup.exe d917cdb747f00ef7c8def46db3ebad826565c380 Edit&Share 5.0.0.0 Setup.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.

2 10