July 2023 - Wine-Bugs - list.winehq.org

[Bug 48172] New: 32 bit wine is unable to allocate a continuous 1.5GB block of memory
by WineHQ Bugzilla Jan. 8, 2024

Jan. 8, 2024

https://bugs.winehq.org/show_bug.cgi?id=48172 Bug ID: 48172 Summary: 32 bit wine is unable to allocate a continuous 1.5GB block of memory Product: Wine Version: 4.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Steps to reproduce: 1) Create a 7zip archive with 1.5GB dictionary (a PC with at least 20GB of RAM is required) using a 64 bit version of the application In console this could be done this way using native p7zip: 7za a -md=1536m arc.7z [files or folders] 2) Try to unpack this file in 32bit Wine/32bit WinRAR - you'll get a message: Not enough memory -- 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 23

[Bug 54402] New: Borland Turbo CPP 4.5 installer deadlocks on start
by WineHQ Bugzilla Jan. 7, 2024

Jan. 7, 2024

https://bugs.winehq.org/show_bug.cgi?id=54402 Bug ID: 54402 Summary: Borland Turbo CPP 4.5 installer deadlocks on start Product: Wine Version: 8.0 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Note that the installer is INSTALL.EXE, not SETUP.EXE. On start, only the splash screen appears, and the following errors are printed to the console: 0110:err:local:LOCAL_GetBlock not enough space in local heap 043f for 16388 bytes 010c:err:sync:RtlpWaitForCriticalSection section 6C8449E0 "../wine/dlls/krnl386.exe16/syslevel.c: Win16Mutex" wait timed out in thread 010c, blocked by 0110, retrying (60 sec) 0110:err:sync:RtlpWaitForCriticalSection section 7BC6A440 "../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0110, blocked by 010c, retrying (60 sec) This is in fact a regression. `git bisect` says: 3a2e7d1a3dbf42a0385e5c0f64d79e9ea054252e is the first bad commit commit 3a2e7d1a3dbf42a0385e5c0f64d79e9ea054252e Author: Alexandre Julliard <julliard(a)winehq.org> Date: Fri May 29 15:02:45 2015 +0900 krnl386.exe: Release the Win16 lock when loading a 32-bit dll. $ sha256sum 'Borland Turbo CPP 4.5 for Windows.7z' 8a6f5797f0af880728421426beacf5e5760701e424d89e14cd714a13e625f2ff -- 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 54220] New: d3d11_swapchain_Present1 Ignored present parameters
by WineHQ Bugzilla Jan. 7, 2024

Jan. 7, 2024

https://bugs.winehq.org/show_bug.cgi?id=54220 Bug ID: 54220 Summary: d3d11_swapchain_Present1 Ignored present parameters Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: st.kost(a)gmail.com Distribution: --- the free vst plugins from here https://ronanfed.rf.gd/plugins.html are not very useable (lots of ui flicker) due to: dxgi:d3d11_swapchain_Present1 Ignored present parameters 000000000011E860 According to the code https://github.com/wine-mirror/wine/blob/master/dlls/dxgi/swapchain.c#L697 and the original docs https://learn.microsoft.com/en-us/windows/win32/api/dxgi1_2/nf-dxgi1_2-idxg… it sound like the "present parameters" are used to parametrize the are to update. -- 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 51738] New: [Bioshock Infinite]Crash after Intro video with "mmap() failed: Cannot allocate memory"
by WineHQ Bugzilla Jan. 5, 2024

Jan. 5, 2024

https://bugs.winehq.org/show_bug.cgi?id=51738 Bug ID: 51738 Summary: [Bioshock Infinite]Crash after Intro video with "mmap() failed: Cannot allocate memory" Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Distribution: --- Created attachment 70619 --> https://bugs.winehq.org/attachment.cgi?id=70619 Bioshock crash output Hi, I try to launch the game bought on GoG - I use Wine 6.16 without extern patch - The game crashes after the Intro video with these error message : mmap() failed: Cannot allocate memory Failed to create permanent mapping for memfd region with ID = 97865773 Failed to regester memfd mempool. Reason: could not attach memfd SHM ID to pipe mmap() failed: Cannot allocate memory Failed to create permanent mapping for memfd region with ID = 3681069605 mmap() failed: Cannot allocate memory Failed to create permanent mapping for memfd region with ID = 1659172633 Ignoring received block reference with non-registered memfd ID = 1659172633 It's a 32bits game, Wine is not patched with LARGE ADRESS AWARE override support findable on TKG github. Instead, i used 4GB_patch from https://ntcore.com/?page_id=371. Without success, the game still crashed. I tried to use wined3d vulkan renderer than opengl and same problem. The full output console 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 5

[Bug 26142] New: Civilization 4: Screen turns black on turn end with built-in msxml
by wine-bugs＠winehq.org Jan. 5, 2024

Jan. 5, 2024

http://bugs.winehq.org/show_bug.cgi?id=26142 Summary: Civilization 4: Screen turns black on turn end with built-in msxml Product: Wine Version: 1.3.13 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msxml3 AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Created an attachment (id=33298) --> (http://bugs.winehq.org/attachment.cgi?id=33298) Image showing the problem Steps to reproduce: 1) remove ~/.wine 2) install Civilization 4 complete 3) wine Civilization4.exe 4) load my save 5) end the turn Behaviour: Black screen and HUD is OK. The game doesn't hang. See attachment (left image) Expected behaviour: There should be no black screen. See attachment (right image) Workaround: winetricks msxml3 Additional comment: This bug occurs randomly and mostly after short films inside the game. If I try to load the same saved game once more time I get black screen too. unless I exit to desktop and load the game again. -- 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 37

[Bug 38039] New: linux console leaves in stty echo off mode after executing bash.exe from Wine
by wine-bugs＠winehq.org Jan. 5, 2024

Jan. 5, 2024

https://bugs.winehq.org/show_bug.cgi?id=38039 Bug ID: 38039 Summary: linux console leaves in stty echo off mode after executing bash.exe from Wine Product: Wine Version: 1.7.35 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fracting(a)gmail.com Distribution: --- Created attachment 50674 --> https://bugs.winehq.org/attachment.cgi?id=50674 Patch: Hack console to restore "echo mode" Steps to reproduce: 1. Install msysGit for Windows: https://github.com/msysgit/msysgit/releases/download/Git-1.9.5-preview20141… 2. cd to the directory of bash.exe 3. executing bash.exe: bin$ wine bash.exe -c "./ls -l" 4. Wine will execute bash.exe and then exectue ls.exe, the output is expected at this stage 5. try to type anything in the same Linux console after ls.exe quit Expect result: Typed characters should be echoed back Actual result: Typed characters are not echoed back, but typed commands run as expected. Workaround: A. execute `stty echo` to enable echo mode again B. apply the attached hack patch -- 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 4

[Bug 40011] New: Git Bash Program error
by wine-bugs＠winehq.org Jan. 5, 2024

Jan. 5, 2024

https://bugs.winehq.org/show_bug.cgi?id=40011 Bug ID: 40011 Summary: Git Bash Program error Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vk.kulk(a)gmail.com Distribution: --- Created attachment 53457 --> https://bugs.winehq.org/attachment.cgi?id=53457 error report I am trying to open Git-Gui from wine. Its not working. Also attached error log. Please look into 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.

2 13

[Bug 45242] New: winedbg Internal crash when debugging win32
by wine-bugs＠winehq.org Jan. 5, 2024

Jan. 5, 2024

https://bugs.winehq.org/show_bug.cgi?id=45242 Bug ID: 45242 Summary: winedbg Internal crash when debugging win32 Product: Wine Version: 3.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: luizluca(a)gmail.com Distribution: --- Hello, I cannot launch winedbg to any win32 exe: $ winedbg Downloads/andale32.exe WineDbg starting on pid 002d 0009:fixme:dbghelp_dwarf:dwarf2_swallow_attribute Unhandled attribute form 1f20 0009:fixme:dbghelp_dwarf:dwarf2_swallow_attribute Unhandled attribute form 1f21 winedbg: Internal crash at 0x7e1cb182 $ winedbg Downloads/PsExec.exe WineDbg starting on pid 002d 0009:fixme:dbghelp_dwarf:dwarf2_swallow_attribute Unhandled attribute form 1f20 0009:fixme:dbghelp_dwarf:dwarf2_swallow_attribute Unhandled attribute form 1f21 winedbg: Internal crash at 0x7e1db182 For win64, it simply works. $ winedbg Downloads/PsExec64.exe WineDbg starting on pid 0031 Process of pid=0031 has terminated I was originally using wine-64bit but even installing wine.i586 and using a clean prefix, I get the same result. $ file /usr/bin/wine /usr/bin/wine: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=37bf33eb8ca1b2a498fc9998fac1753ac70399a8, stripped $ WINEPREFIX=~/win32 WINEARCH=win32 winedbg Downloads/PsExec.exe WineDbg starting on pid 002d 0009:fixme:dbghelp_dwarf:dwarf2_swallow_attribute Unhandled attribute form 1f20 0009:fixme:dbghelp_dwarf:dwarf2_swallow_attribute Unhandled attribute form 1f21 winedbg: Internal crash at 0x7e1c6182 When I try to attach from winedbg, it does not crash, but it returns the 'Unhandled attribute' and raises an exception: $ WINEPREFIX=~/win32 WINEARCH=win32 winedbg Wine-dbg>info process pid threads executable (all id:s are in hex) 0000000e 8 'services.exe' 00000020 6 \_ 'winedevice.exe' 0000001b 3 \_ 'plugplay.exe' 00000011 6 \_ 'winedevice.exe' Wine-dbg>attach 0x11 0009:fixme:dbghelp_dwarf:dwarf2_swallow_attribute Unhandled attribute form 1f20 0009:fixme:dbghelp_dwarf:dwarf2_swallow_attribute Unhandled attribute form 1f21 Exception c0000005 Wine-dbg> -- 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 15

[Bug 54940] New: Import library generation is much slower without dlltool
by WineHQ Bugzilla Jan. 5, 2024

Jan. 5, 2024

https://bugs.winehq.org/show_bug.cgi?id=54940 Bug ID: 54940 Summary: Import library generation is much slower without dlltool Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: 103eb831564decc9812239f454ed1cc40714c0a1 Distribution: --- E.g.: elizabeth(a)ledyba:~/git/wine64$ time tools/winebuild/winebuild -w --implib -o dlls/msi/x86_64-windows/libmsi.a --without-dlltool -b x86_64-w64-mingw32 --export ../wine/dlls/msi/msi.spec real 0m1.509s user 0m0.575s sys 0m0.481s elizabeth(a)ledyba:~/git/wine64$ time tools/winebuild/winebuild -w --implib -o dlls/msi/x86_64-windows/libmsi.a -b x86_64-w64-mingw32 --export ../wine/dlls/msi/msi.spec real 0m0.042s user 0m0.017s sys 0m0.025s -- 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 53108] New: Skyrim SE NPC voices echo inside houses
by WineHQ Bugzilla Jan. 5, 2024

Jan. 5, 2024

https://bugs.winehq.org/show_bug.cgi?id=53108 Bug ID: 53108 Summary: Skyrim SE NPC voices echo inside houses Product: Wine Version: 7.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: marik.jiri(a)protonmail.com Distribution: --- When inside houses all sounds seem to have a strange echo, most noticeable when talking to NPCs. Everything works fine throughout the tutorial, even the part that's happening inside the fort, until the player reaches Riverwood. When talking to NPCs inside houses there's a huge echo. These reddit posts seem to be describing the same issue. https://www.reddit.com/r/linux_gaming/comments/hp0w6k/skyrim_voice_dialogue… https://www.reddit.com/r/linux_gaming/comments/uyh5hq/skyrim_se_voices_echo… As recommended in those posts I tried to use native xaudio2_7 library. I also tried installing faudio through winetricks but there was no change. Installing xact made no difference either. All changes were tried on a fresh prefix. --- OS: Fedora 35 Audio: Pulseaudio 15 (not using pipewire currently but others reported same issue with pipewire as well) Wine version: 7.9 (Staging) --- I also tried downgrading wine to version 6.16-1 and I lost all voice audio on a fresh prefix. I got voice audio back when I installed faudio but the same echo issue was back. Since installing faudio resolved this issue for other people in the past I also tried installing earliest version of faudio in the repos (faudio1901) but the echo is still there. Last thing to mention, this issue is only affecting Skyrim Special Edition at the moment. Vanilla Skyrim voices work 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 5