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

[Bug 50638] New: Builtin Dbghelp.dll doesn't succesfully load symbols from a FakePDB PDB file
by WineHQ Bugzilla Dec. 19, 2021

Dec. 19, 2021

https://bugs.winehq.org/show_bug.cgi?id=50638 Bug ID: 50638 Summary: Builtin Dbghelp.dll doesn't succesfully load symbols from a FakePDB PDB file Product: Wine Version: 6.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it Distribution: ArchLinux Hi. FakePDB is a plugin for IDA PRO 7.x that from the current program and database loaded into IDA , generate a PDB file compatible with debuggers. I created a PDB for Oblivion.exe (the executable of the game The Elder Scroll Oblivion) as I weanted to try the system (and Oblivion has many internal definition decoded from various projects, from OBSE to OblivionReloaded) So I tried triggering a CTD (knowing a way to make the game crash immediatly) but the winedbg wasn't loading the symbols, sometimes causing a crash of the winedbg itself. In the terminals there were a lot of: 04f4:fixme:dbghelp:symt_get_address Unsupported sym-tag --- for get-address Going down the rabbit hole, I tried to see if I could get the value of the sym-tag, adding a print, but the value was nonsensical (1114872 in decimal) too big to be valid. I continued to debug: 0584:trace:dbghelp_msc:pdb_init PDB(C:\Games\Oblivion\Oblivion.pdb): "Microsoft C/C++ MSF 7.00\r\n\x1aDS\x00\ 0584:trace:dbghelp_msc:pdb_init found DS for C:\Games\Oblivion\Oblivion.pdb: age=1 guid={7bbd0a3a-8959-474f-aba3-082cd018c220} 0584:trace:dbghelp_msc:pdb_init PDB(e:\NetworkProjectsPC\OblivionSE\Oblivion\Game\Oblivion.pdb): "Microsoft C/C++ MSF 7.00\r\n\x1aDS\x00\ 0584:trace:dbghelp_msc:pdb_init found DS for e:\NetworkProjectsPC\OblivionSE\Oblivion\Game\Oblivion.pdb: age=1 guid={7bbd0a3a-8959-474f-aba3-082cd018c220} 0584:trace:dbghelp_symt:symt_new_public Adding public symbol L"oblivion":$LN21 @98124f 0584:trace:dbghelp_symt:symt_new_public Added public symbol L"oblivion":$LN21 @98124f a The PDB is found and loaded properly, and the first symbol is succesfully added. However after the first symbol is added all the others start to fail: 0584:trace:dbghelp_symt:symt_new_public Adding public symbol L"oblivion":??0?$LockFreeMap(a)PBDPAVKFModel@@@@QAE(a)XZ @438f10 0584:fixme:dbghelp:symt_get_address Unsupported sym-tag 1114872 for get-address 0584:trace:dbghelp_symt:symt_new_public Failing 10014 10000 10000 1465e64 (I added some traces to understand a bit better what's was going on, but the issue should be clear) Here seems to be that dbghelp_options is SYMOPT_AUTO_PUBLICS and symt_find_nearest(module, address) return a non-null address, so the function symt_new_public return null. For every symbols except the first and the :EntryPoint symbol. For now the only workaround I found is to comment this part of the code: if ((dbghelp_options & SYMOPT_AUTO_PUBLICS) == SYMOPT_AUTO_PUBLICS && (sym = symt_find_nearest(module, address) != NULL)){ return NULL; } And everything seems to work again, but I don't know if by doing this I broke something else. FakePDB code: https://github.com/Mixaill/FakePDB (It use LLVM to generate the PDB 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.

1 3

[Bug 47882] New: Noita - Crash on launch
by WineHQ Bugzilla Dec. 18, 2021

Dec. 18, 2021

https://bugs.winehq.org/show_bug.cgi?id=47882 Bug ID: 47882 Summary: Noita - Crash on launch Product: Wine Version: 4.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: digisteve5(a)gmail.com Distribution: --- Created attachment 65377 --> https://bugs.winehq.org/attachment.cgi?id=65377 backtrace Tried with various desktop settings, set to Windows 7 and 10. -- 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 29934] New: Weird Worlds: Launcher no longer launches the game
by wine-bugs＠winehq.org Dec. 17, 2021

Dec. 17, 2021

http://bugs.winehq.org/show_bug.cgi?id=29934 Bug #: 29934 Summary: Weird Worlds: Launcher no longer launches the game Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: samurai_no_densetsu(a)yahoo.es Classification: Unclassified Weird Worlds's launcher no longer works as expected. Since this is a regression, I did a regression test but it was unsuccessful. The launcher works fine from wine-1.0 to wine-1.3.25, including the stable version wine-1.2.3. So I tried to bisect 1.3.25 against 1.4-rc4. When I was doing the bisection learned that between wine-1.3.27 and wine-1.3.33 (both included) the launcher didn't even appear, and manually had to skip all that range, and within wine-1.3.34 to wine-1.4-rc4 the menu launcher is there but no longer launches the game. Can't provide a regression id as the issue clearly raised between wine-1.3.27 and wine-1.3.33, versions in which the launcher does not start so is virtually impossible to test. Didn't noticed earlier as the game can be launched from scripts or commandline this way: wine weird.exe -skiplauncher -game default Luckyly there's a demo showing the same behaviour here: http://www.shrapnelgames.com/Demos/DD_WW_win.html I wish I could add more info, but that's all I have right now. -- 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 45

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

Dec. 17, 2021

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 Dec. 16, 2021

Dec. 16, 2021

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 50680] New: Detroit: Become Human crashes at launch with ntdll-NtAlertThreadByThreadId
by WineHQ Bugzilla Dec. 16, 2021

Dec. 16, 2021

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 50558] New: ntdll-Dealloc_Thread_Stack cause memory leak for C# game
by WineHQ Bugzilla Dec. 16, 2021

Dec. 16, 2021

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 50520] New: Any Rust-Lang application: Cannot create an async tcp connection
by WineHQ Bugzilla Dec. 16, 2021

Dec. 16, 2021

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 Dec. 16, 2021

Dec. 16, 2021

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

[Bug 48945] New: "Show Advanced Fields" link should be made more visible and changed to a button
by WineHQ Bugzilla Dec. 15, 2021

Dec. 15, 2021

https://bugs.winehq.org/show_bug.cgi?id=48945 Bug ID: 48945 Summary: "Show Advanced Fields" link should be made more visible and changed to a button Product: WineHQ Bugzilla Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: stefan.riesenberger(a)gmail.com CC: austinenglish(a)gmail.com Distribution: --- Created attachment 66919 --> https://bugs.winehq.org/attachment.cgi?id=66919 Example modification of the "Show Advanced Fields" button This is a enhancement bug about the bug report page itself. The "Show Advanced Fields" link isn't really eye catching and blends in with labels or links that will move you to other pages. I would suggest changing it to a real button instead, which would make it's function more obvious. The placement could also be improved, but that's not as important. Currently it gets overshadowed by the components list, so you pretty much overlook it. I would suggest moving it between the version and summary field. I attached a screenshot on how I think it should look like, but as said above the button position is probably more subjective. I hope I explained everything in an understandable way. Kind regards, Riesi -- 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 1