wine-bugs September 2021

wine-bugs@winehq.org

1 participants
4652 discussions

[Bug 51539] New: "server: Get the process entry point from the exe image info" breaks running if exe is loaded at a non-default address
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51539 Bug ID: 51539 Summary: "server: Get the process entry point from the exe image info" breaks running if exe is loaded at a non-default address Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: martin(a)martin.st CC: jacek(a)codeweavers.com, julliard(a)winehq.org Regression SHA1: a3c92a02cc7014cfdb1f90f1d070037868067097 Distribution: --- Since "server: Get the process entry point from the exe image info", a3c92a02cc7014cfdb1f90f1d070037868067097, starting a process fails if the exe image ends up loaded at a non-default address. This can be easily triggered e.g. with this patch: ---8<--- diff --git a/dlls/ntdll/unix/virtual.c b/dlls/ntdll/unix/virtual.c index 8ceba611875..2515d73ee9e 100644 --- a/dlls/ntdll/unix/virtual.c +++ b/dlls/ntdll/unix/virtual.c @@ -2405,8 +2405,10 @@ static NTSTATUS virtual_map_image( HANDLE mapping, ACCESS_MASK access, void **ad base = wine_server_get_ptr( image_info->base ); if ((ULONG_PTR)base != image_info->base) base = NULL; +#if 0 if ((char *)base >= (char *)address_space_start) /* make sure the DOS area remains free */ status = map_view( &view, base, size, alloc_type & MEM_TOP_DOWN, vprot, zero_bits_64 ); +#endif if (status) status = map_view( &view, NULL, size, alloc_type & MEM_TOP_DOWN, vprot, zero_bits_64 ); if (status) goto done; ---8<--- This seems to happen a lot on 32 bit arm builds (on Ubuntu 20.04), when the expected low addresses used as default load address of 0x400000 conflicts with e.g. /home/martin/wine32/share/wine/nls/sortdefault.nls which is mapped at 0x00230000-0x00564000. -- 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 51409] New: Trails to Azure main menu crash after video playback after wine 6.1
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51409 Bug ID: 51409 Summary: Trails to Azure main menu crash after video playback after wine 6.1 Product: Wine Version: 6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: billfleming11(a)gmail.com Distribution: --- Created attachment 70265 --> https://bugs.winehq.org/attachment.cgi?id=70265 Good vs Bad Crash logs In Trails To Azure (and Trails from Zero) both games were working fine in Wine 5.XX and 6.1 but not in future wine releases. (using Geofront translation patch with dinput8 dll) These games play a video on startup, then have a typical "Press Start" screen to get to the main menu. After doing a bisect wine-6.1-249-g5bff63621ee is the last working release. Bisect bad commit: https://source.winehq.org/git/wine.git/commit/897800fd449ae0ea5da00206bd348… https://bugs.winehq.org/show_bug.cgi?id=50667#c1 (reference for getting logs and bug from same commit) Starting in wine-6.1-250-g897800fd449 (for several dozen versions) the game will crash immediately before the video starts playing. All future wine versions (6.2 to present) that succeed in playing the video crash at the menu screen immediately afterwords as soon as input is received at the "PRESS START" screen. However the video does appear to play correctly in these newer releases. If the video is removed or disabled (in the game settings) the game will still crash in the newer wine versions when pressing start at the main menu. You have to let the short (7 second) video play then press a button at the screen in the working wine 6.1 version. See attached 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 14

[Bug 48930] New: Vcrun2019 cannot be installed.
by WineHQ Bugzilla 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=48930 Bug ID: 48930 Summary: Vcrun2019 cannot be installed. Product: Wine Version: 5.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: depositmail(a)mail.ru Distribution: --- Hi! I can't install vcrun2019. Used the Winetricks shell. I can't figure it out myself, I need help. -- 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 43981] New: Watch_Dogs fails to start
by wine-bugs＠winehq.org 17 Dec '21

17 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=43981 Bug ID: 43981 Summary: Watch_Dogs fails to start Product: Wine-staging Version: 2.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fin4478(a)hotmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59641 --> https://bugs.winehq.org/attachment.cgi?id=59641 wine terminal output The Uplay game Watch_Dogs is free in this week. Install Uplay and then you can install the Watch_Dogs game. When you launch the game, the game opens a full screen image where is the Ubisoft logo and plays a sound. Then the game hangs. The terminal output is attached and you can see the following error many times: d3d:wined3d_device_decref Leftover resource 0x1491f420 with type WINED3D_RTYPE_BUFFER (0x1) I use the Wine configuration for watch_dog.exe. I have tried d3d library override and win7 and win8. My system: OpenGL renderer string: AMD POLARIS11 (DRM 3.19.0 / 4.14.0-rc4, LLVM 6.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.0-devel - padoka PPA -- 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 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs September 2021