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

[Bug 58271] New: Window decoration issues in Wine with Wayland driver
by WineHQ Bugzilla 17 Feb '26

17 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=58271 Bug ID: 58271 Summary: Window decoration issues in Wine with Wayland driver Product: Wine Version: 10.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: mexano222(a)gmail.com Distribution: --- Created attachment 78617 --> http://bugs.winehq.org/attachment.cgi?id=78617 default decorations When running applications through Wine using the native Wayland driver, windowed applications are not receiving proper window decorations (e.g., titlebars, borders) from the system window manager. Instead, Wine's default, minimal, and visually unappealing decorations are displayed. I have enabled option "Allow the window manager to decorate the windows" in winecfg and it's working fine on Xwayland. But this option does not appear to have any effect under native Wayland. -- 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 57182] New: Clipboard integration is broken with winewayland
by WineHQ Bugzilla 17 Feb '26

17 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=57182 Bug ID: 57182 Summary: Clipboard integration is broken with winewayland Product: Wine Version: 9.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com Distribution: --- I noticed that clipboard isn't working in Wine Wayland mode. A simple test - run notepad in a prefix with Wine Wayland enabled. Copying anything from it doesn't propagate to system clipboard. Pasting when system clipboard has something doesn't paste it either. DE: KDE Plasma 6.1.4, Wayland session. -- 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 3

[Bug 54381] New: tightvnc viewer crashes on incoming connection
by WineHQ Bugzilla 17 Feb '26

17 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=54381 Bug ID: 54381 Summary: tightvnc viewer crashes on incoming connection Product: Wine Version: 8.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine(a)axeitado.com Distribution: --- Created attachment 73948 --> https://bugs.winehq.org/attachment.cgi?id=73948 Backtrace, 64bits version. $ wine --version wine-8.0-rc3 (Debian 8.0~rc3~repack-1) The crash happens when the connection is established and the remote screen is about to appear on the viewer. For instance, when the remote server connects to the viewer with a reverse connection: $ wine tvnviewer.exe -listen c:\> tvnserver.exe -run c:\> tvnserver.exe -controlapp -connect <viewer-host-address> wine: Unhandled page fault on write access to 0000000000000000 at address 000000014007D22D (thread 0110), starting debugger... 0108:err:sync:RtlpWaitForCriticalSection section 0000000001D77BF8 (null) wait timed out in thread 0108, blocked by 010c, retrying (60 sec) The above example uses the reverse connection method, which is straightforward to setup. When the viewer connects to a listening remote server the same crash occurs: c:\> rem the server must be properly configured: c:\> tvnserver.exe -run $ wine tvnviewer.exe <remote-server-address> wine: Unhandled page fault on write access to 0000000000000000 at address 000000014007D22D (thread 010c), starting debugger... 0108:err:sync:RtlpWaitForCriticalSection section 0000000001D77BF8 (null) wait timed out in thread 0108, blocked by 010c, retrying (60 sec) This worked until very recently, 7.0.1~repack-1 was fine (this is Debian Testing). The software is licensed under the GPL and binaries can be downloaded on the author's homepage (currently at version 2.8.63): https://www.tightvnc.com/download.php The 32 bit version also crashes. Backtrace attached. It looks like the problem is related to starting a thread. -- 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 18

[Bug 56825] New: Unable to see screen for Harmony Assistant version 9.9.8d (64 bit)
by WineHQ Bugzilla 17 Feb '26

17 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=56825 Bug ID: 56825 Summary: Unable to see screen for Harmony Assistant version 9.9.8d (64 bit) Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dheorchestra(a)gmail.com Distribution: --- Created attachment 76632 --> https://bugs.winehq.org/attachment.cgi?id=76632 screen shot of installed Harmony Assistant 9.9.8d (64 bit). Cannot see installed program screen. I am using Linux Lite 7.0 Download Link for Harmony Assistant version 9.9.8d (64 bit) https://www.myriad-online.com/en/products/harmony.htm When running a new installation of the Windows version of Harmony Assistant v9.9.8d (64-bit) all I receive is a black screen with little white dots on it when the program is installed. -- 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 16

[Bug 34427] New: Star Citizen launcher has several graphics issues
by wine-bugs＠winehq.org 17 Feb '26

17 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=34427 Bug #: 34427 Summary: Star Citizen launcher has several graphics issues Product: Wine Version: 1.7.1 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: adys.wh(a)gmail.com Classification: Unclassified Created attachment 45828 --> http://bugs.winehq.org/attachment.cgi?id=45828 Screenshot on wine-1.7.1 Lots of hsls/d3dcompiler spam: err:d3dcompiler:compile_shader HLSL shader parsing failed. fixme:hlsl_parser:hlsl_parse Check for valued return on void function. fixme:hlsl_parser:hlsl_parse Implicit conversion to the return type if needed, error out if conversion not possible. fixme:hlsl_parser:hlsl_parse Check for valued return on void function. fixme:hlsl_parser:hlsl_parse Implicit conversion to the return type if needed, error out if conversion not possible. fixme:hlsl_parser:declare_vars Complex initializers are not supported yet. fixme:d3dcompiler:make_assignment Check for casts in the lhs. err:d3dcompiler:compile_shader HLSL shader parsing failed. fixme:hlsl_parser:hlsl_parse Array. fixme:d3dcompiler:make_assignment Check for casts in the lhs. fixme:d3dcompiler:make_assignment Check for casts in the lhs. fixme:hlsl_parser:hlsl_parse Array. err:d3dcompiler:compile_shader HLSL shader parsing failed. Screenshots and log attached -- 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 8

[Bug 56648] New: Autodesk DWG TrueView fails at installation
by WineHQ Bugzilla 17 Feb '26

17 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=56648 Bug ID: 56648 Summary: Autodesk DWG TrueView fails at installation Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: szatkus(a)gmail.com Distribution: --- Installation fails with the fixme: "Could not find dependent assembly odis.bs.win (1.0.0)" Turns out the installer creates a new folder (%TEMP%/7z0F0512E4) with another installer that apparently is invoked next. The program removes it automatically after crashing, but it could be retrieved by placing `while(1);` next to the fixme or by using a Windows machine. There's the Setup.exe file that has the following manifest in its resources: <?xml version='1.0' encoding='UTF-8' standalone='yes'?> <assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedPrivileges> <requestedExecutionLevel level='asInvoker' uiAccess='false' /> </requestedPrivileges> </security> </trustInfo> <dependency> <dependentAssembly> <assemblyIdentity type='win32' name='odis.bs.win' version='1.0.0.0' processorArchitecture='*' language='*' /> </dependentAssembly> </dependency> <dependency> <dependentAssembly> <assemblyIdentity type='win32' name='odis.bs.wx' version='1.0.0.0' processorArchitecture='*' language='*' /> </dependentAssembly> </dependency> <dependency> <dependentAssembly> <assemblyIdentity type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='*' publicKeyToken='6595b64144ccf1df' language='*' /> </dependentAssembly> </dependency> <dependency> <dependentAssembly> <assemblyIdentity type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='*' publicKeyToken='6595b64144ccf1df' language='*' /> </dependentAssembly> </dependency> </assembly> >From what I gathered this manifest is used to resolve some required dlls files, but it ultimately fails. The odis.bs.win is resolved by the following algorithm (a comment from the wine code): /* Lookup in <dir>\name.dll * <dir>\name.manifest * <dir>\name\name.dll * <dir>\name\name.manifest * * First 'appdir' is used as <dir>, if that failed * it tries application manifest file path. */ The file it's looking for is in ODIS/odis.bs.win/odis.bs.win.manifest, not in odis.bs.win/odis.bs.win.manifest (name="odis.bs.win"). Where from does Windows get the ODIS part? Well, there's also a file called "Setup.exe.config" with the following content: <configuration> <windows> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <probing privatePath="ODIS"/> </assemblyBinding> </windows> </configuration> It looks that the program should resolve through <dir>/<privatePath>. I added a few prints here and there, and it seems that Setup.exe.config is not loaded by wine at any point. Moving odis.bs.win and odis.bs.wx to the upper folder fixes the problem, although the installation still fails after a while. -- 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 41267] New: Black ops 2 crashes with "Unhandled exception caught"
by wine-bugs＠winehq.org 17 Feb '26

17 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=41267 Bug ID: 41267 Summary: Black ops 2 crashes with "Unhandled exception caught" Product: Wine Version: 1.9.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spleefer90(a)gmail.com Distribution: --- Created attachment 55567 --> https://bugs.winehq.org/attachment.cgi?id=55567 crash log when trying to launch the game(BO2:MP) from Steam Game crashes on startup with the message: "Error during initialization: Unhandled exception caught" -- 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 55

[Bug 58084] New: Commit d813ffc3 (ntdll: Align virtual memory allocations to the host page size) breaks Wine in a Rosetta emulated Docker environment
by WineHQ Bugzilla 16 Feb '26

16 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=58084 Bug ID: 58084 Summary: Commit d813ffc3 (ntdll: Align virtual memory allocations to the host page size) breaks Wine in a Rosetta emulated Docker environment Product: Wine Version: 10.5 Hardware: arm OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: alex(a)willner.ws **Version:** 10.5 and 10.4 **Steps that will reproduce the problem:** On an arm64 M2 run macOS 15.4 (24E248) and execute with Docker version 28.0.4 (b8034c0): docker run --platform linux/amd64 --rm scottyhardy/docker-wine:devel-10.4 sh -c 'wine --version && winecfg' **What is the expected result:** > % docker run --platform linux/amd64 --rm scottyhardy/docker-wine:devel-10.5 sh -c 'wine --version && winecfg' > wine-10.5 > wine: created the configuration directory > ... **What happens instead:** > wine-10.5 > wine: dlls/ntdll/unix/virtual.c:253: anon_mmap_fixed: Assertion `!((UINT_PTR)start & host_page_mask)' failed. > qemu: uncaught target signal 6 (Aborted) - core dumped > Aborted **Possible workaround:** Downgrade to Wine 10.4: > % docker run --platform linux/amd64 --rm scottyhardy/docker-wine:devel-10.4 sh -c 'wine --version && winecfg' > wine-10.4 > wine: created the configuration directory > ... *Any additional information:** See Commit d813ffc3: ntdll: Align virtual memory allocations to the host page size. https://gitlab.winehq.org/wine/wine/-/commit/d813ffc3557083fd135a28d59f490b… -- 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 12

[Bug 57212] New: Spider-Man: Shattered Dimensions - Unable to get display aspect ratio
by WineHQ Bugzilla 15 Feb '26

15 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=57212 Bug ID: 57212 Summary: Spider-Man: Shattered Dimensions - Unable to get display aspect ratio Product: Wine Version: 9.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: tinozzo123(a)gmail.com Distribution: --- ### About the game Spider-Man: Shattered Dimensions is a weird D3D9 game: in its settings, not only there is the resolution option, but there is also the "AspectRatio" option. This setting is saved in the registry: `HKEY_CURRENT_USER\SOFTWARE\Activision\Spider-Man (TM) SD\Settings\Display\AspectRatio` 1 for 4:3, 2 for 16:10, 3 for 16:9. ### What the game is supposed to do (first launch) On Windows and on Wine Wayland, when launching the game for the first time (that is, when the registry key doesn't exist), that key is `NtSetValueKey`ed to 4 (a value that seems intentionally invalid), then it is `NtSetValueKey`ed to the appropriate value. ### What happens instead on Wine X11 (first launch) On Wine X11 (or XWayland), `NtSetValueKey` for "AspectRatio" is only called once to set it to 4, and it stays as such. (Which makes the game 4:3.) That probably means that whatever the game needs to do before the second `NtSetValueKey` fails. #### Symptoms of the issue You may wonder: "Since the Aspect Ratio option is exposed in the in-game settings, can't you adjust them there?". However, due to the game being poorly coded, this issue may make the game stuck in an unsupported resolution, causing a chain reaction of issues that makes the game unable to change all graphics settings, and sometimes it even makes the game unable to render the title screen, crashing when starting a level. Manually editing the "AspectRatio" key after the first launch doesn't solve all issues: it may still be impossible to change all graphics settings. This probably means that the game depends on "getting" the display's aspect ratio even if the registry key is set. ### Logs I don't know what channels should the logs contain. Tell me, and I'll send them. -- 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 1

[Bug 57161] New: when starting captvty, it stops saying it has encontered a problem
by WineHQ Bugzilla 15 Feb '26

15 Feb '26

https://bugs.winehq.org/show_bug.cgi?id=57161 Bug ID: 57161 Summary: when starting captvty, it stops saying it has encontered a problem Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: patrick.pochard(a)free.fr Distribution: --- Created attachment 77064 --> https://bugs.winehq.org/attachment.cgi?id=77064 backtrace available when the pb occurs captvty stops saying the is a problem captvty 2.10.8.2 wine 9.0 os linux mint 22 I tried to install 9.15 & 9.16 but the is a dependency issue libx11-dev:i386 and could not find a solution -- 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