wine-bugs

wine-bugs@winehq.org

1 participants
159000 discussions

[Bug 56354] New: Bioshock 1.0 demo crashes on HLSL syntax error 'unexpected T_TEXT, expecting T_NEWLINE'
by WineHQ Bugzilla 10 Aug '25

10 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=56354 Bug ID: 56354 Summary: Bioshock 1.0 demo crashes on HLSL syntax error 'unexpected T_TEXT, expecting T_NEWLINE' Product: vkd3d Version: 1.10 Hardware: x86-64 URL: http://us.download.nvidia.com/downloads/nZone/demos/nz d_BioShockPC.zip OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com Distribution: --- 01cc:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 01cc:err:d3dcompiler:D3DCompile2 Shader log: 01cc:err:d3dcompiler:D3DCompile2 StandardInputs.hlsl:6:32: E4000: syntax error, unexpected T_TEXT, expecting T_NEWLINE 01cc:err:d3dcompiler:D3DCompile2 StandardInputs.hlsl: W4305: Unterminated #if block. 01cc:err:d3dcompiler:D3DCompile2 01cc:err:d3dcompiler:preprocess_shader Failed to preprocess shader, vkd3d result -4. 01cc:err:d3dcompiler:preprocess_shader Shader log: 01cc:err:d3dcompiler:preprocess_shader StandardInputs.hlsl:6:32: E4000: syntax error, unexpected T_TEXT, expecting T_NEWLINE 01cc:err:d3dcompiler:preprocess_shader StandardInputs.hlsl: W4305: Unterminated #if block. 01cc:err:d3dcompiler:preprocess_shader wine: Unhandled page fault on read access to 00000000 at address 10D9BBDE (thread 01cc), starting debugger... -- 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

[Bug 58527] New: autocad electrical 2026 error in wxwidgets
by WineHQ Bugzilla 10 Aug '25

10 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58527 Bug ID: 58527 Summary: autocad electrical 2026 error in wxwidgets Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: grandrodri3(a)gmail.com Distribution: --- Created attachment 79001 --> http://bugs.winehq.org/attachment.cgi?id=79001 autocad architecture error in wxwidgets Hey, hello guys, how are you? Well, I'm adding a new application to the Wine database. This is an AutoCAD application developed by Autodesk, specifically for electrical plans (specifically, electrical panel installations in homes). So, I'm reporting the error the installer gives me to see if anything can be done. The error I'm getting, by the way, was loaded with the following DLLs installed: vcrun2012 vcrun2022 dotnetcore3 dotnet8 I get an error in the DLLs for the Windows implementation of wxwidgets. I've tried installing wxwidgets from their official website, but nothing. AutoCAD doesn't go beyond the terminal (that is, the installer doesn't display). official download website: https://www.autodesk.com/es/products/autocad/included-toolsets/autocad-elec… I'll pass what I get in the terminal. Could you please check it? Best 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 7

[Bug 58585] New: unnamed keymap layout leads to null pointer dereference in find_xkb_layout_variant
by WineHQ Bugzilla 10 Aug '25

10 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58585 Bug ID: 58585 Summary: unnamed keymap layout leads to null pointer dereference in find_xkb_layout_variant Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: lompikvoila(a)gmail.com Distribution: --- Created attachment 79112 --> http://bugs.winehq.org/attachment.cgi?id=79112 gdb backtrace Using the winewayland would abruptly exit at launch. Running wine64 under gdb uncovers a segv happening in find_xkb_layout_variant's strcmp (see attachement, due to name being NULL). As per the documentation(https://xkbcommon.org/doc/current/group__components.html#ga50…, xkb_keymap_layout_get_name can return null if the layout does not have any name(or if there is an error). This is problematic as find_xkb_layout_variant does not handle the case where name is NULL. Returning false in find_xkb_layout_variant if name is NULL fixes the issue. -- 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 0

[Bug 58583] New: msvcp140: Multiple modern applications using C++ Concurrency crash in CONCRT140.dll on startup
by WineHQ Bugzilla 10 Aug '25

10 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58583 Bug ID: 58583 Summary: msvcp140: Multiple modern applications using C++ Concurrency crash in CONCRT140.dll on startup Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: waser(a)waser.tech Distribution: --- Created attachment 79107 --> http://bugs.winehq.org/attachment.cgi?id=79107 The game's own crash log from its `_appdata_ixray_/logs` directory. This report details a consistent, immediate startup crash in `CONCRT140.dll` affecting modern S.T.A.L.K.E.R. engine forks. These engines are based on the open-source **Open X-Ray 1.6**, which itself works flawlessly under Wine. The crash only appears in these newer, more advanced forks which leverage the MSVC concurrency runtime for performance. This strongly indicates the issue lies within Wine's implementation of these APIs, not a bug in the engines themselves. This is effectively a regression, as the baseline engine works while the newer, concurrency-enabled versions do not. **Existing Related Bugs:** This issue appears to be a new, highly reproducible test case for known problems in Wine's concurrency support. We are filing this as a new report due to the unique test case and the specific failure point (constructor vs. destructor), but it is likely caused by the same underlying issues as: - **Bug 52899:** Notes that `CONCRT140.dll` requires `CreateEventExW` from `kernel32`. This is the most likely root cause. - **Bug 41749:** Shows a crash in the destructor for `Concurrency::details::_TaskCollection`. Our crash occurs in the *constructor* of this same object, demonstrating a different failing code path. Our report provides two clear methods to reproduce this crash, including one that is fully free and requires no commercial software. --- ### **Primary Reproduction Steps (IX-Ray on S.T.A.L.K.E.R.: Call of Pripyat)** *(Steps 1-5 as in previous draft)* 6. **Run the Game with Debug Logging:** Launch the game using its main executable with full debug channels enabled. ```bash WINEDEBUG=+all wine Stalker-COP.exe &> stalker_cop_crash_all.log WINEDEBUG=+seh,+loaddll wine Stalker-COP.exe &> stalker_cop_crash_seh.log ``` 7. **Result:** The process will crash immediately. The game's own crash log (in `_appdata_ixray_/logs`) and the attached Wine debug logs will show a fatal error in `CONCRT140.dll`. --- ### **Alternative Reproduction Steps (AOEngine on S.T.A.L.K.E.R. Anomaly)** *(As in previous draft, but with the same logging commands)* --- **Expected Behavior:** The game launcher should appear, and the game should launch to the main menu successfully, as it does on Windows and as the baseline Open X-Ray 1.6 engine does under Wine. **Logs:** Three files will be attached for the primary reproduction case: 1. `stalker_cop_crash_seh.log`: A small log with `+seh,+loaddll` for quick initial review. 2. `stalker_cop_crash_all.log.bz2`: The complete `+all` debug log, compressed with bzip2 due to its large size. 3. `ixray-2025.08.10-02.37.21-waser.log`: The game's own crash log from its `_appdata_ixray_/logs` directory. **References:** - **IX-Ray GitHub (Open Source Engine):** https://github.com/ixray-team/ixray-1.6-stcop - **GE-Proton Issue #197 (Full History):** https://github.com/GloriousEggroll/proton-ge-custom/issues/197 -- 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 2

[Bug 44966] New: [ER: The Game] A style error occurred while verifying the reading of the license agreement.
by wine-bugs＠winehq.org 10 Aug '25

10 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=44966 Bug ID: 44966 Summary: [ER: The Game] A style error occurred while verifying the reading of the license agreement. Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: ilya(a)ilin.pp.ua Distribution: --- Created attachment 61088 --> https://bugs.winehq.org/attachment.cgi?id=61088 Screenshot When installing the game, the possibility of accepting the license agreement is conceived only if it is fully read (textarea should scroll to the bottom). But in wine it does not work. wine 3.5 openSUSE Tumbleweed Game download: (registry don't need) https://firedrop.com/4bfe735821e6bfcb or http://www.theisozone.com/downloads/pc/windows-games/er---the-game (Black Download button) Patches: https://www.gamewatcher.com/games/er/downloads 0030:err:ole:TLB_ReadTypeLib Loading of typelib L"C:\\Program Files (x86)\\Common Files\\InstallShield\\Professional\\RunTime\\IsProBE.tlb" failed with error 2 0030:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet 0030:fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0x33dd3c L"M:\\data1.hdr" 0030:err:richedit:ReadStyleSheet skipping optional destination 0030:err:richedit:ReadStyleSheet skipping optional destination 0030:err:richedit:ReadStyleSheet skipping optional destination -- 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 56137] New: Overwatch 2 fails to save highlight video files
by WineHQ Bugzilla 09 Aug '25

09 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=56137 Bug ID: 56137 Summary: Overwatch 2 fails to save highlight video files Product: Wine Version: 9.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: forestix(a)nom.one Distribution: --- When attempting to save an Overwatch 2 highlight video as an mp4 file (the default format), it fails with this error message: SAVING ERROR An unknown error has occurred. (6-04) Steps to reproduce: - play a game (easiest way is via Play: Training: Practice vs. AI: Casual) - after the game is over, return to the main menu - click username button (top right corner) - click history tab (top edge) - click highlights tab (left edge) - click a highlight from "today's top 5" - click save button (bottom edge) - select movie format: mp4 - click save button Note that this is a different kind of failure than the one with .webm format (bug 56059). -- 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 58490] New: MusicBee: tab dragging still does not work
by WineHQ Bugzilla 09 Aug '25

09 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58490 Bug ID: 58490 Summary: MusicBee: tab dragging still does not work Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: v_winebugs(a)outlook.com Distribution: --- Bug 52078 was solved thanks to the drag and drop helpers being stubbed, however WINE still does not allow for tab dragging with MusicBee, so I'm adding it as a separate bug report. How to reproduce: On MusicBee, attempt to drag a tab. Expected behaviour: MusicBee should allow me to drag the tab and drop it to move it. Actual behaviour: A prohibited cursor shows up and the tab is unable to be dragged. Tested on WINE Staging 10.11 on Arch Linux -- 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 58580] New: macOS clang: -msabi=ms unrecognized option... causes x86_64-unix/*.a files to be missing. Cannot winegcc cannot link agains libadvapi32 et al
by WineHQ Bugzilla 09 Aug '25

09 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58580 Bug ID: 58580 Summary: macOS clang: -msabi=ms unrecognized option... causes x86_64-unix/*.a files to be missing. Cannot winegcc cannot link agains libadvapi32 et al Product: Wine Version: 10.0 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: winelib Assignee: wine-bugs(a)winehq.org Reporter: matteo.ceruti(a)gmail.com Created attachment 79102 --> http://bugs.winehq.org/attachment.cgi?id=79102 the patch for the configure-script that works for me I had first reported this to macports but I think you should have a look at it https://trac.macports.org/ticket/72792 Expected Behavior: I like to continue to use winegcc and wineg++ on macOS x86_64 to compile winelibs. In fact it worked with wine 9.0. Actual Behavior: winegcc says it cannot link against advapi32 and others and infact the files such as libadvapi32.a are not in lib/x86_64-unix/ anymore. I think this might be the case since this change: https://github.com/wine-mirror/wine/commit/84d8a24af71d#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810L1969 "Disable non-PE import libraries if compiler support is missing." The -mabi-ms check is now done even if $PE_ARCHS exist which in my understanding means we're crosscompiling PE code. The macport compiles with clang and uses minGW to compile the PE code. But clang does not recognize and no longer ignores the -mabi=ms option and in that case the configure-script now sets DLLEXT from its initial value ".so" to "" which seems to cause the *.a archive files to not being created/installed. I've patched the configure-script so that DLLEXT is only set to "" in case $PE_ARCHS is empty analogous to the fact that in that -mabi=ms not being recognized is not reported as an error. And I can create winelibs .exe.so and .dll.so just fine and load them from a client *.exe. I'd like to still use winegcc and wineg++ and the winelib feature on macOS. Is this no longer possible? I guess linux using clang might experience the same. This is my the patch that works for me on wine 10.12 (It's also attached): https://github.com/matatata/macports-ports/blob/ff459f21995e6b6fceeacd51cea… I'd appreaciate if you could take a look and clarify. -- 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 58581] New: Nirsoft siteshooter only produces "black" files
by WineHQ Bugzilla 09 Aug '25

09 Aug '25

http://bugs.winehq.org/show_bug.cgi?id=58581 Bug ID: 58581 Summary: Nirsoft siteshooter only produces "black" files Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Distribution: --- Install Nirsoft Siteshooter 1.42 (https://www.nirsoft.net/utils/siteshoter.zip) Use http://www.google.com as URL and "test.png" on desktop as local file and run a screenshot test.png is only a black png and no error is raised. -- 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

[Bug 38774] New: Execute MS Excel 2007 macro crashes Excel
by wine-bugs＠winehq.org 09 Aug '25

09 Aug '25

https://bugs.winehq.org/show_bug.cgi?id=38774 Bug ID: 38774 Summary: Execute MS Excel 2007 macro crashes Excel Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: florent.merlet(a)free.fr Distribution: --- Created attachment 51706 --> https://bugs.winehq.org/attachment.cgi?id=51706 Crash report of macro execution on Microsoft Excel 2007 The execution of a Excel Visual Basic Macro execution does not work when it is compiled from Wine 1.6.2. The compilation starts properly, and the window freezes after few seconds. The macro tested works properly on windows 7. There is no problem to modify, record the macro, and execute it from a MS Windows 7 environment. details : Microsoft EXCEL 2007, installed Windows 7 personal -- 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 7

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