October 2021 - Wine-bugs - list.winehq.org

[Bug 51000] New: Rufus won't run on a fresh prefix; Needs "elevated privileges"
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51000 Bug ID: 51000 Summary: Rufus won't run on a fresh prefix; Needs "elevated privileges" Product: Wine-staging Version: 6.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: oguilherme(a)protonmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: ArchLinux Created attachment 69844 --> https://bugs.winehq.org/attachment.cgi?id=69844 Wine Staging 6.6 log file Rufus 3.13 (Portable) won't run on a fresh Wine Staging prefix. The oldest staging version I could still reproduce this was on 6.3. Steps to reproduce: 1. Download rufus-3.13p.exe from here: https://github.com/pbatard/rufus/releases/tag/v3.13 (sha1: da498e3e80186ee16620f56a601e19fbdc1f8551) 2. Run: $ WINEPREFIX=~/.wine2 wine rufus-3.13p.exe 3. Rufus will display the following message and exit: "This application can only run with elevated privileges" I wasn't able to reproduce with vanilla Wine. Regards. -- 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 51143] New: Dragon NaturallySpeaking does not install with "CheckForElevationState" return 1602
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51143 Bug ID: 51143 Summary: Dragon NaturallySpeaking does not install with "CheckForElevationState" return 1602 Product: Wine Version: 6.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: susancragin(a)earthlink.net Distribution: --- Created attachment 70013 --> https://bugs.winehq.org/attachment.cgi?id=70013 Installation log I am trying to install Dragon Naturally Speaking 12.5 on a new Gentoo install. I have done this successfully in the past, on both Debian and Gentoo installs, one on this machine. But now I keep getting this error, which is a Microsoft error saying that I have terminated the installation. err:msi:ITERATE_Actions Execution halted, action L"CheckForElevationState" returned 1602 When I try to install Dragon Naturally Speaking 15 Home, it quits with the same error. (Natspeak 15 does not install successfully, but usually quits with an error much further in the installation process. However, when I install Notepad++ that works. That may be just because there are no MSIs with it. -- 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 50680] New: Detroit: Become Human crashes at launch with ntdll-NtAlertThreadByThreadId
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=50680 Bug ID: 50680 Summary: Detroit: Become Human crashes at launch with ntdll-NtAlertThreadByThreadId Product: Wine-staging Version: 6.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lvb.crd(a)protonmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 69406 --> https://bugs.winehq.org/attachment.cgi?id=69406 wine-6.2 with ntdll-NtAlertThreadByThreadId +seh,+pid,+timestamp,+tid output The game won't launch on Wine-Staging 6.1 and 6.2. I've done some tests and found that using Wine + `ntdll-NtAlertThreadByThreadId` from Staging is enough to reproduce this problem. Disabling this patchset on Staging or using "vanilla" Wine helps. And the most annoying thing is that "slowing down Wine" (or whatever) with `WINEDEBUG="+seh,+pid,+sync,+timestamp` - fixes the problem on my local system/hardware. So I can't reproduce it at collection of logs. I was able to attach a log with these debug channels (+seh,+pid,+timestamp,+tid), but it looks like the game can create several kinds of error. Perhaps it depends on which part of the code/thread is the first to be executed (it looks like something related to parallel programming, I don't know how it is called correctly). (Sorry, it looks like this time I was not able to collect any useful information to create a report, but I believe that it would be wrong not to create it at all.) -- 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 30

[Bug 51602] New: Roblox Player crash when server-default_integrity/0007-ntdll-Elevate-processes-if-requested-in-RtlCreateUse.patch is applied
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51602 Bug ID: 51602 Summary: Roblox Player crash when server-default_integrity/0007-ntdll-Elevate-processes- if-requested-in-RtlCreateUse.patch is applied Product: Wine-staging Version: 6.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: a0939712328(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 70451 --> https://bugs.winehq.org/attachment.cgi?id=70451 The Wine-Staging patch that causes the crash. A recent update to Roblox Player cause Wine-staging to crash with the error "An unexpected error occurred and Roblox needs to quit. We're sorry!". To locate the exact patchset that caused the issue, I created a bisect tool in Python that allows me to approximately rule out half of the patchsets every rebuild. After few rounds of bisection, I discovered that by skipping just the server-default_integrity patchset, Roblox Player no longer crash. I did further bisect and found that applying "0007-ntdll-Elevate-processes-if-requested-in-RtlCreateUse.patch" causes Roblox Player to crash. The patch was introduced on commit be3928a8091e36197bc9894c4a09f13cf5459138 (server-default_integrity: Elevate processes if the manifest requests.), which is supposed to fix Bug ID 51000. The patch file itself is attached below to make the discussion easier. -- 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 51085] New: Overwatch crashes when launched from Battle.net
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51085 Bug ID: 51085 Summary: Overwatch crashes when launched from Battle.net Product: Wine-staging Version: 6.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: b1779506(a)trbvn.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Always crashes. wine-6.7 (Staging) on Ubuntu 21.04. -- 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 50558] New: ntdll-Dealloc_Thread_Stack cause memory leak for C# game
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=50558 Bug ID: 50558 Summary: ntdll-Dealloc_Thread_Stack cause memory leak for C# game Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: trufanovan(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- I've traced down a memory leak in one game to the ntdll-Dealloc_Thread_Stack in wine-staging. No other wine versions or staging patches cause such problem. I've reproduced it on actual wine master branch from github with `./staging/patchinstall.py ntdll-Dealloc_Thread_Stack` The game is "Delta's Shadow" released in 2020. Demo is available at https://zxonline.net/game/deltas-shadow/ Its Windows version is written in C# with SDL. The memory leaks every time game plays SFX and only in this case. A music doesn't cause leak. I've asked the author: music is played via SDL and SFX is played with System.Media.SoundPlayer::Play(). It looks like this class is just calls PlaySound function from winmm.dll and pass a stream with WAV into it. And this somehow and ups in ntdll. So, to reproduce the problem: 1. Install wine-staging 2. Install the demo 3. Launch game in wine-staging 4. Press ALt+Enter to switch the game into a windowed mode and launch Task manager to see the RAM it consumes. 5. Start pressing W and S keys (Up and Down) in game main menu to produce a menu item change SFX. Result: Game RAM usage grows each time you press the key and don't decrease later. Expected: No significant RAM usage change. -- 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 51172] New: Blank screen with many games using wine-staging 6.9 and Arch (wine 6.9 works OK)
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51172 Bug ID: 51172 Summary: Blank screen with many games using wine-staging 6.9 and Arch (wine 6.9 works OK) Product: Wine-staging Version: 6.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vulture6(a)mail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: ArchLinux Most games now just give a blank screen when they are run with wine-staging 6.9 on my Arch distro. Can list some if necessary, but should be obvious. No clear errors from debug log. Changing to standard wine 6.9 fixes problem. System: Core i5 with Intel UHD 630. -- 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 51198] New: regression: black screen in main menu of warcraft 3 reforged with wine-staging-6.9
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51198 Bug ID: 51198 Summary: regression: black screen in main menu of warcraft 3 reforged with wine-staging-6.9 Product: Wine-staging Version: 6.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: idarktemplar(a)mail.ru CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 70072 --> https://bugs.winehq.org/attachment.cgi?id=70072 wc3.log.bz2 When running Warcraft 3 Reforged in wine-staging 6.9, main menu is a completely black screen, and instead of cursor there are some visual artefacts. With wine-staging 6.8 it works acceptably: it's really slow, but at least there's properly rendered main menu. No DXVK is used. OS: Gentoo Linux, kernel 5.10.27 Proprietary Nvidia driver 460.67: OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 750/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 460.67 OpenGL core profile shading language version string: 4.60 NVIDIA Wine output contains a lot of lines similar to: 03bc:err:d3d:state_undefined Undefined state UNKNOWN_STATE(0) (0). Log 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.

1 4

[Bug 50520] New: Any Rust-Lang application: Cannot create an async tcp connection
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=50520 Bug ID: 50520 Summary: Any Rust-Lang application: Cannot create an async tcp connection Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)greaka.de Distribution: --- Created attachment 69183 --> https://bugs.winehq.org/attachment.cgi?id=69183 minimal example Rust applications are not able to use async libraries in wine. TCP connections send Syn, receive Syn/Ack, send Reset. Test matrix: - Wine versions 5.0, 5.8, 5.22, 6.0rc0 , 6.0rc6 - Ubuntu, Arch - WSL, native on laptop - Tokio, Smol, Async-Std (Smol and async-std use the same under the hood) - Rust versions 1.48 stable, 1.49 stable, 1.50 beta - Targets windows-gnu, windows-msvc - Toolchains gnu, msvc Every combination fails to connect. Minimal example source code: https://pastebin.com/SZavTYD7 precompiled binary 1.50 beta/windows-msvc/msvc attached. The example expects a listener on localhost:41206! You can easily open one with ncat -l -k -p 41206 The error returned to rust: [src\main.rs:10] TcpStream::connect(addr.as_slice()).await = Err( Os { code: 10045, kind: Other, message: "OS Error 10045 (FormatMessageW() returned error 317)", }, ) Trace from wineserver: Short version https://cdn.discordapp.com/attachments/596410107726921728/79886280364864308… Long version https://cdn.discordapp.com/attachments/596410107726921728/79885875841138688… -- 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 22

[Bug 48726] New: Final Fantasy XIV, freezes for several seconds when the mouse is moved with ReShade / GShade installed.
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=48726 Bug ID: 48726 Summary: Final Fantasy XIV, freezes for several seconds when the mouse is moved with ReShade / GShade installed. Product: Wine-staging Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: HereInPlainSight+wine(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- First time submitting -- apologies if I'm missing anything obvious. Firstly, the regression was tested using the git repos from wine's 'wine-5.0' tag and wine-staging's 'v5.0' tag. The issue is still present even with the wine 5.3 versions, but when I tried to follow the regression tests, I was failing to compile. I might've screwed something up, I can try again if you need me to, but I am a bit of a derp and I'm punching upward. The output I got from the regression test (following instructions from https://wiki.winehq.org/Wine-Staging#Reporting_and_debugging_bugs_against_S… ) was: 014cecf3f8e5eac5f8e23ef1aaf07f8e17169188 is the first bad commit commit 014cecf3f8e5eac5f8e23ef1aaf07f8e17169188 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Mon Aug 26 14:08:20 2019 +0200 dinput8: Use raw input interface for dinput8 mouse device. dlls/dinput/mouse.c | 117 +++++++++++++++++++++++++++++++++++++++++++- dlls/dinput8/tests/device.c | 10 ++-- 2 files changed, 119 insertions(+), 8 deletions(-) Second, the game currently requires ntdll-Hide_Wine_Exports, and it works fine with just that, and people can use an older version of Proton / Wine and that works around the problem too. Finally, the actual problem: If ReShade (or GShade, a fork of ReShade) is installed with FFXIV, as soon as you get into the game itself (not the launcher), the game works perfectly fine unless you move the mouse. As soon as you move the mouse the game freezes from around five to ten seconds every time you move the mouse, making it effectively unplayable. This did not happen with Wine-Staging prior to 5.0. Reproduction: 1) Download and install FFXIV (I realize Lutris is an extraneous program and I can go through the details, but I'd just be repeating what the scripts at https://lutris.net/games/final-fantasy-xiv-a-realm-reborn/ say to do / what's required. I can add the info if it's preferable). 2) Download and install a shader program (I use GShade, so instructions are based on that arbitrarily, but I confirmed the same issue with ReShade): 2a) Easiest installation is to download https://github.com/Mortalitas/GShade-Shaders/releases/latest/download/GShad… into the prefix/drive_c/Program Files (x86)/SquareEnix/FINAL FANTASY XIV - A Realm Reborn/game/ directory and unzip it. Also download https://lutris.net/files/tools/dll/d3dcompiler_47.dll to the same location. 2b) Add overrides for d3d11 (native,builtin) and d3dcompiler_47 (native) to the prefix. 3) Run the game, sign in through the launcher. 4) When the game loads, move the mouse. There's no output of the issue such that I can see by default in the console. -- 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