March 2025 - Wine-bugs - list.winehq.org

[Bug 57393] New: MS Office 2013: Slide out File menu panel is behind the editing page
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=57393 Bug ID: 57393 Summary: MS Office 2013: Slide out File menu panel is behind the editing page Product: Wine Version: 9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: bigfoothart(a)gmail.com Distribution: --- Created attachment 77375 --> https://bugs.winehq.org/attachment.cgi?id=77375 wayland debug * GNOME 47 * Arch Linux * winetricks -q vcrun2017 msxml6 dxvk * wayland 1.23.1-1 MS Office 2013: Slide out File menu panel is behind the editing page. Watch the video and wayland debug log. -- 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 57570] New: Syntax Error in CMD Batch Parsing
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=57570 Bug ID: 57570 Summary: Syntax Error in CMD Batch Parsing Product: Wine-staging Version: 10.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: juan3(a)yandex.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 77673 --> https://bugs.winehq.org/attachment.cgi?id=77673 running wine cmd When attempting to run the `msys2_shell.cmd` script from MSYS2, Wine fails with a syntax error: `Syntax error: unexpected IN`. This issue occurs during the batch file parsing phase. 1. Download the MSYS2 base archive from the following link: ``` https://github.com/msys2/msys2-installer/releases/download/2024-12-08/msys2… ``` 2. Extract the archive to a directory, e.g., `Z:\msys2\msys64`. 3. Navigate to the extracted directory: ``` Z:\msys2\msys64> ``` 4. Run the `msys2_shell.cmd` script with the following arguments: ``` msys2_shell.cmd -here -defterm -no-start ``` 5. Observe the error: ``` Syntaxfehler Syntax error: unexpected IN ``` The `msys2_shell.cmd` script should execute without errors and launch the MSYS2 shell environment. Wine fails with a syntax error: `Syntax error: unexpected 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.

2 6

[Bug 39627] New: BreezeBrowser Pro 1.x crashes on start
by wine-bugs＠winehq.org 08 Dec '25

08 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=39627 Bug ID: 39627 Summary: BreezeBrowser Pro 1.x crashes on start Product: Wine Version: 1.7.34 Hardware: x86 URL: http://www.breezesys.com/downloads/bbpro1987.exe OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: erich.e.hoover(a)wine-staging.com Regression SHA1: ca51e113e4820f8b11016c13732b1a971d2b0054 Distribution: --- The application crashes immediately after starting (no backtrace is generated for me): fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:server_ioctl_file Unsupported ioctl 900a8 (device=9 access=0 func=2a method=0) fixme:ntdll:server_ioctl_file Unsupported ioctl 900a8 (device=9 access=0 func=2a method=0) wine: Unhandled exception 0x40000015 in thread 9 at address 0x80d930 (thread 0009), starting debugger... If you manually create an empty 'dbglogs' directory under ~/Documents, then the application starts properly.It seems the application fails to create that directory for some reason. Regression introduced by commit ca51e113e4820f8b11016c13732b1a971d2b0054 Author: Erich E. Hoover <erich.e.hoover(a)gmail.com> Date: Tue Aug 19 20:31:00 2014 -0600 ntdll: Unify retrieving the attributes of a file. The commit can't be reverted on git (Wine build failure), however the application starts properly with the previous commit (and dbglogs directory is created). Still present in wine-1.7.55-73-g39f2ed3. bbpro1987.exe sha1: ead99cf82bc8eeac4413ed4939891bbe57251058 -- 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.

3 21

[Bug 53442] New: Total War Shogun 2 needs D3DX_FILTER_BOX for memory management.
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=53442 Bug ID: 53442 Summary: Total War Shogun 2 needs D3DX_FILTER_BOX for memory management. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- Total War Shogun 2 uses the D3DX_FILTER_BOX filter to downscale it's textures. Both during normal usage, but more critically, when it's VRAM budget is low or over-committed. This can be seen on Intel GPUs in the game's stderr output with a line similar to: ---snip--- ** Downsizing Textures, Over Budget by : 115 Mb ---snip--- Followed by (in wine-7.12 or older) or prior (in wine-7.13 or later) multiple fixmes: ---snip--- 0024:fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x5. ---snip--- See also the attached log from wine-7.13. As this filter is used for memory management in a 32bit game, it's implementation would help alleviate some OOM errors. -- 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 55176] New: Regression: Wing Commander Secret Ops/Prophecy unable to launch.
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=55176 Bug ID: 55176 Summary: Regression: Wing Commander Secret Ops/Prophecy unable to launch. Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jcarthew(a)gmail.com Distribution: --- Game fails to load with a fatal error: "file 'game\\cdlayout.iff' not found and not optional" 0024:err:vxd:MONODEBG_DeviceIoControl "Fatal: " 0024:err:vxd:MONODEBG_DeviceIoControl "Iff::Iff open file 'game\\cdlayout.iff' not found and not optional" 0024:fixme:event:wait_for_withdrawn_state window 0x10070/a00001 wait timed out 0024:fixme:event:wait_for_withdrawn_state window 0x20070/a00004 wait timed out Bug was introduced between WINE 7.8 and 7.9. Generating regression testing to locate exact 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.

1 14

[Bug 53737] New: Incoming (game): crashes after the intro video
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=53737 Bug ID: 53737 Summary: Incoming (game): crashes after the intro video Product: Wine Version: 7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: putr4.s(a)gmail.com Distribution: --- Created attachment 73174 --> https://bugs.winehq.org/attachment.cgi?id=73174 Terminal output of GOG version Recently with an update in the Wine 7.x series (don't know which one unfortunately, but it worked with 7.x at some point) the game Incoming no longer runs, it shows the intro video and music, but then the music stops and it crashes on either a black screen or the loading screen while the Wine crash reporter appears in the background. I was using the GOG version of Incoming, but the demo (the same one mentioned in bug 44864, MD5: 5b1fff6863768eeff95167e510d09a2e, SHA256: dcc55a269c33ea5363cd937284752d7ffe57f4774c55a38dfdd4a9172376563c, 3.8MB file called incoming.exe, available via cnet.com at least) also exhibits the same issue. I have attached the terminal output from the GOG version as log.txt, and I will also attach the terminal output of the GOG version as well as the demo versions of those two. The wine version I am using is from the Arch Linux repositories, and I am using a clean 64 bit wineprefix with no settings changed at all (this setup worked fine before), although I also tried a 32 bit wineprefix, same results. OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) HD Graphics 530 (SKL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.1.7 OpenGL core profile shading language version string: 4.60 OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.1.7 OpenGL shading language version string: 4.60 -- 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 15

[Bug 25535] New: .NET Framework 4.0 Fails to install with HRESULT 0x80070643
by wine-bugs＠winehq.org 07 Dec '25

07 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=25535 Summary: .NET Framework 4.0 Fails to install with HRESULT 0x80070643 Product: Wine Version: 1.3.9 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: pjdowson(a)gmail.com Wine version is 1.3.9, compiled with no parameters on Fedora 13. Installing dotNetFx40_Full_x86_x64.exe downloaded from the MS website, the installer will open and verify the integrity of files. The next stage will attempt to install the .NET Framework 4.0 Client Profile. Towards the end of this install the installer will fail with HRESULT 0x80070643, leaving little or no information in the %TEMP% folder as to the cause. The installer will only run if wine is set to WinXP. Process used to reproduce: WINEPREFIX=~/.wine-net40 sh winetricks gecko WINEPREFIX=~/.wine-net40 sh winetricks windowscodecs ie7 msxml3 WINEPREFIX=~/.wine-net40 wineboot WINEDEBUG=+relay WINEPREFIX=~/.wine-net40 wine Downloads/net40/dotNetFx40_Full_x86_x64.exe &> net-out I also attempted to install the .NET Framework 4.0 Client Profile prior to installing the Full package. This provides the same error, the only difference to the above process used was the filename of the Client Profile installer dotNetFx40_Client_x86_x64.exe. Each time I attempted to install I used a clean WINEPREFIX, deleting the prior one before attempting again. Screenshot of error: http://www.stimpy.org/wine/net-error.png Logs referenced in above screenshot, in %TEMP% dir: http://www.stimpy.org/wine/net-install-logs.tar.gz Output of installer debug: http://www.stimpy.org/wine/net-out.tar.gz This is my first bug report, I apologize if I have missed anything out. -- 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 48

[Bug 12401] New: Support junction points, i.e. DeviceIoCtl( FSCTL_SET_REPARSE_POINT/FSCTL_GET_REPARSE_POINT)
by wine-bugs＠winehq.org 07 Dec '25

07 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=12401 Summary: Support junction points, i.e. DeviceIoCtl(FSCTL_SET_REPARSE_POINT/FSCTL_GET_REPARSE_PO INT) Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Junction points are one of Microsoft's answers to symlinks. Unix symlinks could be mapped into junction points. This would allow applications (e.g. Picasa) avoid following symlinks if they wanted to. Also, the .net 2 installer would be happier in winxp mode if wine supported junction points (see bug 10601): "The .NET 2.0 Framework installer checks if the target volume is NTFS filesystem type and then uses the FSCTL_SET_REPARSE_POINT ioctl (used for mount points and junctions) to create junction points for each registered assembly in Windows SxS directory to GAC assembly directory (link target). Basically the junction point is used to redirect access from one directory to another." Tommy Kho posted a patch to add a conformance test for getting and setting junction points, http://www.winehq.org/pipermail/wine-patches/2006-March/024956.html but it was not accepted. -- 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 90

[Bug 56647] New: ntdll-Junction_Points prevent rustup from correctly installing a toolchain
by WineHQ Bugzilla 07 Dec '25

07 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=56647 Bug ID: 56647 Summary: ntdll-Junction_Points prevent rustup from correctly installing a toolchain Product: Wine-staging Version: 9.8 Hardware: x86-64 URL: https://rustup.rs/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: ArchLinux Created attachment 76423 --> https://bugs.winehq.org/attachment.cgi?id=76423 return STATUS_NOT_A_REPARSE_POINT instead of STATUS_INVALID_PARAMETER Hi. With the recent rustup 1.27.0 using wine-staging with the ntdll-Junction_Points patches, the toolchain installation doesn't complete properly, failing to write to the settings.toml under the prefix home .rustup directory info. A bug with the same root cause is also present on rustup 1.26.0 where while the installation was completing properly, it was failing to remove the .rustup/tmp/* directories, causing issues with subsequent installations. Both bugs express the same behavioral pattern with few differences. I investigated the directory bug firstly, so I will detail this, and confirmed that the problem and the expected solution are the same. Rustup (or one of it's dependency managing files) get the handle of the temporary directory using CreateFileW and then checking if it's a reparse point using DeviceIoControl with FSCTL_GET_REPARSE_POINT. The directories (and the file) aren't reparse points at all, so the readlink fails returining EINVAL. This EINVAL is then mapped to an NT_STATUS using errno_to_status that map EINVAL to STATUS_INVALID_PARAMETER. However this mapping is incorrect for FSCTL_GET_REPARSE_POINT as in this case applications that handle this case like rustup try to handle this case by epxecting STATUS_NOT_A_REPARSE_POINT. Returning STATUS_NOT_A_REPARSE_POINT in this case allow rustup to work (both versions ) Attaching a patch to show the change in the file.c code (and restored also the out_buffer check) -- 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 33997] New: win86emu needs Unimplemented function KERNEL32.dll.CreateSymbolicLinkA
by wine-bugs＠winehq.org 07 Dec '25

07 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=33997 Bug #: 33997 Summary: win86emu needs Unimplemented function KERNEL32.dll.CreateSymbolicLinkA Product: Wine Version: 1.6-rc4 Platform: arm URL: http://forum.xda-developers.com/showthread.php?t=20959 34 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: nerv(a)dawncrow.de CC: focht(a)gmx.net Classification: Unclassified PostInstall.exe from win86emu says: wine: Call from 0xb6b71868 to unimplemented function KERNEL32.dll.CreateSymbolicLinkA, aborting I already checked that it doesn't try to import something from kernel32 per ordinal. -- 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 11